You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a new ontology submission is uploaded and re-processed, the cache is re-populated with all the existing and new terms contained within the submission. However, if a term had been removed between the submissions, its entries still remain in the Annotator cache. Currently, the only way to remove these orphan terms is to regenerate the entire Annotator cache.
We've observed an increased number of cases, where this behavior causes wrong Annotations to be returned.
This functionality can be developed as a CRON job that runs weekly to remove orphan entries.
The text was updated successfully, but these errors were encountered:
When a new ontology submission is uploaded and re-processed, the cache is re-populated with all the existing and new terms contained within the submission. However, if a term had been removed between the submissions, its entries still remain in the Annotator cache. Currently, the only way to remove these orphan terms is to regenerate the entire Annotator cache.
We've observed an increased number of cases, where this behavior causes wrong Annotations to be returned.
This functionality can be developed as a CRON job that runs weekly to remove orphan entries.
The text was updated successfully, but these errors were encountered: