The ability to browse development models, especially in the user page, is a general demand. It would help curators to access the models they are currently working on.
Several solutions exist:
The easiest & quickest is to include the development models in the blazegraph journal behind the sparql endpoint rdf.geneontology.org.
Another solution is to further use the bbop manager NodeJS modules
Notes:
this question is somewhat related to the current choice of having an independent readonly SPARQL endpoint and a Minerva/Barista stack for writing models (triples)
to avoid displaying development models on the GO-CAM landing page, they should be hidden by default, or a cleaner solution would be to have a general login/session, where only curators & admin would have access to development models.
The ability to browse development models, especially in the user page, is a general demand. It would help curators to access the models they are currently working on.
Several solutions exist:
Notes: