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

Finalize new SPARQL end user page for GO #1606

Closed
1 of 4 tasks
kltm opened this issue Jan 5, 2021 · 10 comments
Closed
1 of 4 tasks

Finalize new SPARQL end user page for GO #1606

kltm opened this issue Jan 5, 2021 · 10 comments

Comments

@kltm
Copy link
Member

kltm commented Jan 5, 2021

To support the link in the published paper and end users, we want to accomplish the following steps for a new end user SPARQL page for the GO:

  • ensure that it is understood that rdf.geneontology.org will be the public endpoint to run SPARQL (and retain its blazegraph interface), while sparql.geneontology.org will be the general-purpose end user "gui" interface
  • (attempt to) shorten or make available http://rdf.geneontology.org/blazegraph/sparql to http://rdf.geneontology.org/sparql
  • add index.html single page app to geneontology.github.io repo
  • undo sparql.geneontology.org proxy server and have above single page app available at sparql.geneontology.org

From conversation with @cmungall and @lpalbou
Also letting @balhoff know, in case he has queries pointed at sparql.geneontology.org, or knows of anybody who does

@lpalbou
Copy link
Contributor

lpalbou commented Jan 5, 2021

Linking to geneontology/geneontology.github.io#267

@pgaudet
Copy link
Contributor

pgaudet commented May 12, 2021

Where do we stand with this?

@lpalbou
Copy link
Contributor

lpalbou commented May 12, 2021

For end-users, the public sparql page (http://sparql.geneontology.org) has been up and running for several months. This ticket is only about back end optimizations that do not affect end users.

  1. IMO done, but doesn't really matter as it's just 2 different UIs to query the same endpoint. Jim may be the only one caring about the blazegraph UI as it provides some non-RDF features that are blazegraph specific

  2. is to simplify the URL of the rdf endpoint, it's a nice to have, but nothing critical or that would affect anyone work

  3. done and powering the public UI

  4. nice to have, doesn't really affect end users except they get redirected to http://geneontology.org/sparql

@pgaudet
Copy link
Contributor

pgaudet commented May 13, 2021

ok thanks!

Would it be hard to have the same footer as on other http://geneontology.org/ pages?

Anyway I think this can close?

@cmungall
Copy link
Member

I'm ok to close

@lpalbou
Copy link
Contributor

lpalbou commented May 15, 2021

Footer added and updated.

@lpalbou lpalbou closed this as completed May 15, 2021
@pgaudet
Copy link
Contributor

pgaudet commented May 17, 2021

Thanks !!

@pgaudet
Copy link
Contributor

pgaudet commented May 17, 2021

One more question: Is this tool available from the main GO website? I cannot find it. I would expect it to be here:
http://geneontology.org/docs/tools-overview/

Thanks, Pascale

@lpalbou
Copy link
Contributor

lpalbou commented May 17, 2021

The SPARQL page is accessible from the GO APIs Guide: https://geneontology.github.io/docs/tools-guide/#query-go-causal-activity-models-sparql-endpoint but not from the GO Tools Overview. Ideally we want to keep a clear separation between APIs: REST API, SPARQL API, GOLr; and (higher level) Tools: amigo, gocam browser, ribbon, matrix, Noctua.

But yes, the access to both the Tools & APIs is not super intuitive right now. Creating a simple top-level menu for listing & quick access would help. I have been delaying the refactoring of that section of the website as we were / are planning to work on the new GO API, Jupyter notebooks and recommendations of community tools.

For reference: geneontology/geneontology.github.io#285

@pgaudet
Copy link
Contributor

pgaudet commented May 17, 2021

Thanks for the explanation!

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

4 participants