Page History

Versions Compared

changes.mady.by.user Unknown User (endlecm)

Saved on Oct 09, 2018

compared with

changes.mady.by.user Unknown User (stanclcr2)

Saved on Oct 09, 2018

...

Topic	Discussion
topic 1	Discussion Points: Remote users currently need to use the client jars. This is a concern for the end users. This could be done by updating CTS2 services and provide REST services to these users. CTS2 supports all the vocabularies (including meta). EVS REST API is limited to Triple Store content using elastic search. Governance of the services is critical in order to provide one central query mechanism. LexEVS will no longer have the stand alone code systems. The Meta will continue to live in LexEVS. There is the possibility for Meta in EVS REST API. The NLM does host UTS API. This could be something to look at. Sorting and Ranking is important for results, but this isn't available in the EVS REST API yet. End users do not have resources to upgrade or the funding. This might be done be the EVS team (rewriting code, etc). Decision Points:

Topic

Discussion

topic 1

Discussion Points:

Remote users currently need to use the client jars. This is a concern for the end users. This could be done by updating CTS2 services and provide REST services to these users.
- CTS2 supports all the vocabularies (including meta). EVS REST API is limited to Triple Store content using elastic search.
Governance of the services is critical in order to provide one central query mechanism.
LexEVS will no longer have the stand alone code systems. The Meta will continue to live in LexEVS. There is the possibility for Meta in EVS REST API.
The NLM does host UTS API. This could be something to look at.
Sorting and Ranking is important for results, but this isn't available in the EVS REST API yet.
End users do not have resources to upgrade or the funding. This might be done be the EVS team (rewriting code, etc).

Decision Points:

Attachments

...