Evaluate technical feasability of TIB terminology service integration for ontology terms

[sven1103]

What are you missing?

Our terminology terms, e.g. for mass spec devices (see #734) need to be updated regularly to support recently added terms. However, the maintenance effort is moderate, and in case of #734 also frustrating, when file formats of ontologies suddenly break.

At the same time, the availability of recent terms is a requirement of our service portfolio. If we cannot hold the promise, why are we enforcing ontology terms in the first place.

Why do you need a solution?

I would like to evaluate the TIB terminology service API and the technical feasibility of integration, especially with Vaadin's lazy loading data provider feature.

Ideas

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[sven1103]

Ok, given that the both the Query class in Vaadin and the TIB terminology service API support page size (or rows), limit and offset (page).
The response times are fast (<50ms), and with the filtering for provided ontologies, i think we should give it a try.

[sven1103]

• Define a terminology service
• Define a terminology repository interface, masking the implementation details of the HTTP REST API interaction and result object conversion
• Implement terminology repository
• Exchange ontology service for specimen, analyte and measurement device

[Shraddha0903]

UI Suggestion for the pre-selection of categories before the search: