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
Exposing a SPARQL endpoint for Slinky would be fun but it's not all that useful to anyone but ourselves. And even then.
It'd be better if we had a concise showcase of what Slinky is and what it can do and this could similar to what we did for GeoLink: http://data.geolink.org/.
Today we put together a quick list of interesting example queries that could go on this page:
Show me all datasets that have measurements of sea-surface temperature
Show me all datasets that have measurements of carbon-dioxide flux from Alaska
Show me all datasets created by Ted Schuur
Show me all datasets that have the term “ecosystem” in their Abstract or Title
Show me all datasets about Salmon that have both weight and length measurements (ideally in a tuple)
Who’s doing research in the arctic? Which organizations?
[I don't think we have an issue for this specifically but let me know if that's wrong]
The text was updated successfully, but these errors were encountered:
One option is to use the yasgui module for the query page, which is used on the gnis-ld queries page. It's really easy to set up and should work on any framework that supports npm or yarn. I think the bigger questions are which technology we'd want to go with. I feel pretty biased towards hugo because it's well supported, uses pretty sane templating & css languages, and is used in other DataONE projects.
Relating this to #11 because depending on the web framework we choose we can do a reverse proxy to Virtuso.
I'm imaging this would be deployed at api.dataone.org/slinky and the sparql endpoint at api.dataone.org/slinky/sparql.
An alternative would be to give the sparql endpoint priority at api.dataone.org/slinky/sparql (since api.dataone.org/slinky is Virtuoso Conductor), which might feel more APIish and put the query examples at api.dataone.org/slinky/examples or api.dataone.org/slinky/queries.
We now have a minimal landing page with a few example SPARQL queries. The current queries aren't too interesting, so we should leave this open and add a few of the ones Bryce mentioned above.
Exposing a SPARQL endpoint for Slinky would be fun but it's not all that useful to anyone but ourselves. And even then.
It'd be better if we had a concise showcase of what Slinky is and what it can do and this could similar to what we did for GeoLink: http://data.geolink.org/.
Today we put together a quick list of interesting example queries that could go on this page:
[I don't think we have an issue for this specifically but let me know if that's wrong]
The text was updated successfully, but these errors were encountered: