At TIB, we are working on several projects for Terminology services for NFDIs and one of them is NFDI4Chem Terminology service based on EBI-OLS. This service provides the chemistry related ontologies to our users in NFDI4Chem consortium. Chemists in this group use these ontologies extensively and at the same time they contribute to these ontologies especially RXNO, MOP, CHEBI, CHIRO etc.
Recent additions to RXNO and MOP were not listed in our NFDI4Chem TS, although they are present in the downloadable .owl file. Solr index container updated the ontology, according to the time-stamp, also these new terms are also visible in the search bar, but upon clicking it, it gave a 404 error. This was solved only after doing a re-deployment to production.
As we will have more users who will be using our Terminology service and also curate/suggest ontology terms from our platform. This can have major complications for updating the new terms. It looks like these new terms which are indexed by Solr are not present in the Neo4j straightaway. The actual terms in tree-view and mappings that are visible for a particular ontology are by Neo4j. So, it could be possible that the phenomenon we observed was a caching issue with Neo4j.
I was hoping EBISPOT team can share some insight to automate this process without having to re-deploy to production whenever new terms are added.
At TIB, we are working on several projects for Terminology services for NFDIs and one of them is NFDI4Chem Terminology service based on EBI-OLS. This service provides the chemistry related ontologies to our users in NFDI4Chem consortium. Chemists in this group use these ontologies extensively and at the same time they contribute to these ontologies especially RXNO, MOP, CHEBI, CHIRO etc.
Recent additions to RXNO and MOP were not listed in our NFDI4Chem TS, although they are present in the downloadable .owl file. Solr index container updated the ontology, according to the time-stamp, also these new terms are also visible in the search bar, but upon clicking it, it gave a 404 error. This was solved only after doing a re-deployment to production.
As we will have more users who will be using our Terminology service and also curate/suggest ontology terms from our platform. This can have major complications for updating the new terms. It looks like these new terms which are indexed by Solr are not present in the Neo4j straightaway. The actual terms in tree-view and mappings that are visible for a particular ontology are by Neo4j. So, it could be possible that the phenomenon we observed was a caching issue with Neo4j.
I was hoping EBISPOT team can share some insight to automate this process without having to re-deploy to production whenever new terms are added.