SPARQL endpoint page http://sparql.geneontology.org

[lpalbou]

The documentation page http://geneontology.org/docs/sparql/ has been completed but is not yet referenced (#269).

The SPARQL entry point described in the GO article is http://sparql.geneontology.org. Currently, this redirects to a generic blazegraph workbench page with no mention of GO or example.

This ticket is to deploy in production the new UI page for the GO SPARQL endpoint:

Steps:

• @lpalbou to push the standalone page in this repo: sparql.html
• @kltm creating a proxy from sparql.geneontology.org to http://geneontology.org/sparql
• @kltm to store that page on a GO S3 bucket "sparql.geneontology.org" and activate the "Static website hosting"
• @kltm to change the routing of http://sparql.geneontology.org from http://rdf.geneontology.org/blazegraph/ to that newly S3 bucket:

---

The following is just for reference as @cmungall would prefer a proxy to a GH page. If it was to be done with CF/S3/Route53, it could be done that way:

Result on my test architecture (http://sparql.geneontology.xyz/):

It's important to use the correct bucket name, or you won't see that option for the routing. If you have additional difficulties, you could otherwise just create a CF distribution to that bucket and route the subdomain to that CF distribution.

[lpalbou]

@kltm I pushed the sparql.html standalone page to this repo: 66d6675

If you have difficulties deploying it on sparql.geneontology.org, please refer to the steps I took for S3/Route53 here: #267 (comment) and which give us this page & route: http://sparql.geneontology.xyz

Thanks

[cmungall]

regarding the specific content to go on the static documentation page, let's set up another ticket for this page, as @lpalbou says:

This ticket is to deploy in production the new UI page for the GO SPARQL endpoint:

[lpalbou]

There is a little mix indeed, so let's be clear, there are two pages:

• UI page where users can actually test queries (this ticket as well as Finalize new SPARQL end user page for GO go-site#1606)
• doc page where we explain how to do those queries (I just created a dedicated ticket and transfer the comments there: SPARQL doc page geneontology.org/docs/sparql #269)

[cmungall]

I suggest a modification to the 2nd item in the checklist

As a general principle, I vastly prefer minimizing the number of moving pieces. I would rather not add an extra bucket just for deploying a static html file. While it is trivial, it adds to the overall complexity of configuration of the system, add introduces additional things that need synchronized.

My preference would be that all static html served to the public is done from a single source, which is this repo. We would simply check the html into this repo, and it would be deployed automatically. There is no need to set up an additional job to sync content from github to a new bucket. We would still need to have http://sparql.geneontology.org point at this page (3rd item in checklist).

[lpalbou]

Right. As it is, the page is already on GH and also accessible through: http://geneontology.org/sparql. So if you prefer without S3 bucket, I will replace step 2 by @kltm creating a proxy from sparql.geneontology.org to http://geneontology.org/sparql.

[kltm]

Okay, playing around a little with this, it seems like I have found settings for both forwarding and full proxying. Given what I think the uses are right now, I'm a little more comfortable with having the forward in place (less mechanism, less likely to get weird later). The forward is currently applied. @cmungall Do you have an opinion which way to go here?

[lpalbou]

Proxy seems to be working.

Other issues / recommendations can be added as separate tickets, deployment done.