Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Classes inaccessible for ontologies with a new submission with Error Rdf status #379

Open
jvendetti opened this issue Dec 20, 2024 · 3 comments

Comments

@jvendetti
Copy link
Member

After adoption of some code from AgroPortal, there's a new behavior where all the tabs on ontology landing pages are hidden except for the Summary tab if the latest submission failed to parse. In my opinion this causes a serious regression where users can no longer access the ontology data from the last successful processing run.

Prior to adopting AgroPortal's code, all the tabs on ontology landing pages were visible at all times. In the event a new submission was uploaded that failed to parse, BioPortal users could still navigate to the Classes tab and browse the last good version of the ontology data.

For a specific example, see the FOODON ontology. Submission with ID 103 successfully processed in BioPortal. The next submission (with ID 104) failed to parse and is listed in the Submissions table with an "Error Rdf" status. Since the Classes tab is hidden, there's no way for a user to browse the classes from the last good submission. Even worse, if you click on the link in the Submissions table for the last successfully processed version, you end up on a page that looks like this:

Screenshot 2024-12-19 at 6 09 30 PM

This behavior is inconsistent with how our REST API operates. In other words, even though the latest submission of FOODON failed to parse, you can still issue a REST call to successfully retrieve the ontology classes from the last valid submission: https://data.bioontology.org/ontologies/FOODON/classes.

If possible, I think implementing a solution for this should be prioritized. Users shouldn't be prevented from browsing ontology data if the most recent submission failed to parse, particularly since the ontology data from the previous good submission is still accessible via the REST API.

@jvendetti
Copy link
Member Author

You can also end up on pages like the screenshot above by clicking on valid search results on the Search page. Steps to reproduce:

  1. Navigate to the top-level Search page
  2. Enter "apple" in the Class Search text area
  3. Use advanced options to narrow the search to the FOODON ontology
  4. Perform the search and click on the matched result

Notice that you're navigated to the same blank ontology landing page.

Screenshot 2024-12-19 at 6 32 26 PM Screenshot 2024-12-19 at 6 38 27 PM

@syphax-bouazzouni
Copy link
Contributor

syphax-bouazzouni commented Dec 20, 2024

hello, this is the line doing that filter https://github.com/ncbo/bioportal_web_ui/blob/master/app/helpers/ontologies_helper.rb#L174.

You can remove or adapt that condition to have the desired behavior.

If you want the previous behavior, you can remove that condition.

If you want the AgroPortal behavior, which is to show the other data sections(classes, properties,...) only if the current or previous submission is ready you need to fix it because the issue I think is that in the AgroPortal alignment work, the variable @old_submission_ready was not assigned. it needs to be added like this https://github.com/ontoportal-lirmm/bioportal_web_ui/blob/master/app/controllers/ontologies_controller.rb#L288-L295 in bioportal ontologies_controller show action.

@alexskr
Copy link
Member

alexskr commented Dec 20, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants