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
We've had several reports from the developers of the EDAM ontology where they upload a new ontology submission and the user interface only shows the submission status as uploaded. After waiting (sometimes as long as 24 hours), they're never able to see the status as anything other than uploaded, i.e., the data for the new submission never becomes visible.
I've reproduced this behavior in our production environment on two separate occasions, and observed the following:
It doesn't matter if you are logged in our out. The new submission shows as "uploaded" for both cases.
Clearing the browser cache has no effect.
Manually clearing BioPortal's goo and HTTP caches from the administrative page has no effect.
The only way I was able to get the new data to become visible in the UI was to click the "Flush UI Cache" button on the administrative page, which clears the front end in-memory cache (memcached).
I've also verified (by looking at the production parsing logs), that the EDAM ontology is relatively small and the system has no difficulty during the parsing process. From start to finish, we process the ontology in roughly 12 minutes.
The text was updated successfully, but these errors were encountered:
We've had several reports from the developers of the EDAM ontology where they upload a new ontology submission and the user interface only shows the submission status as uploaded. After waiting (sometimes as long as 24 hours), they're never able to see the status as anything other than uploaded, i.e., the data for the new submission never becomes visible.
I've reproduced this behavior in our production environment on two separate occasions, and observed the following:
The only way I was able to get the new data to become visible in the UI was to click the "Flush UI Cache" button on the administrative page, which clears the front end in-memory cache (memcached).
I've also verified (by looking at the production parsing logs), that the EDAM ontology is relatively small and the system has no difficulty during the parsing process. From start to finish, we process the ontology in roughly 12 minutes.
The text was updated successfully, but these errors were encountered: