EBISPOT / ols4

Version 4 of the EMBL-EBI Ontology Lookup Service (OLS)
http://www.ebi.ac.uk/ols4/
Apache License 2.0
47 stars 22 forks source link

Frontend should cater for properties that has hundereds (some has more than a 100000) of values #754

Open henrietteharmse opened 1 month ago

henrietteharmse commented 1 month ago

New feature description. There are a number of examples where properties can contain a large amount of values. A full list of examples with details about the property, term and ontology can found here. In these cases OLS can take some time to render the full results (i.e. https://www.ebi.ac.uk/ols4/ontologies/dron/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FOBI_0000576).

Use cases In OLS there is at least 1500 terms that have properties with more than 100 values. Here are some examples:

  1. relatedFrom - here is an example with fewer values than the example above: https://www.ebi.ac.uk/ols4/ontologies/go/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_16526.
  2. relatedTo - See https://www.ebi.ac.uk/ols4/ontologies/go/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FCHEBI_57945.
  3. http__//purl.obolibrary.org/obo/NCIT_A31 - See for example https://www.ebi.ac.uk/ols4/ontologies/ncit/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FNCIT_C70729.
  4. http__//semanticscience.org/resource/SIO_000139

User communities If possible and without violating GDPR, can you refer us to user communities who are in need of this feature? In OLS there is at least 1500 terms that have properties with more than 100 values spanning ontologies such as DRON, NCIT, GO, FBBT etc.

Describe the solution you'd like It will be ideal if this can be address by frontend changes alone, except if further investigation finds backend or databases bottlenecks. From a user perspective, when a property has more than, say 100 values, the first 100 should be rendered and a combination of paging and search capabilities should allow a user to find and navigate to those values.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.