ODISCat ID as primary key, for graph (SPARQL, parquet, etc) & front-end queries

[jmckenna]

Background

• in the original odis-arch configuration, we used the short name property in the config, to query a partner's records through parquet or SPARQL queries (for the Caribbean Marine Atlas, see the name here)
• moving forward, we will be using the ODISCat ID as the primary key, for all queries
  • for the Caribbean Marine Atlas, this is ODISCat ID 616

Question

(below was submitted to the ODIS team by the ICAN summer scholar, and @tchaddad )

"Is it possible to find records in OIH that are associated with a specific ODIS Cat ID?"

So, for example the Caribbean Marine Atlas has an ODIS Cat ID of "616" --> is this ID something that can be used to query OIH and return a list of records from the OIH graph that originated from the Caribbean Marine Atlas?

I should clarify that we can see that the ODIS id is in the provenance portion of the json-ld record:

"prov:wasAttributedTo":{
          "@id":"https://catalogue.odis.org/view/616",
          "@type":"prov:Organization",
           "rdf:name":"Caribbean Marine Atlas catalogue",
           "rdfs:seeAlso":"https://www.caribbeanmarineatlas.net/"}

But the question more specifically is: does the current interface (or API?) have a mechanism to ask the graph for a list of records with a specific @id ?

And to be more specific - I can see that the current OIH interface accepts a query link this:

https://oceaninfohub.org/results/Dataset?page=0&facet_query=facetType%3Dtxt_provider%26facetName%3DCaribbean%2BMarine%2BAtlas%2Bcatalogue

that URL uses the text name of the provider "Caribbean Marine Atlas Catalogue" to return records.

What I want is to figure out a similar url query that instead takes the provider ID as the facet that is queried on... "@id":"https://catalogue.odis.org/view/616"

cc @fils @pbuttigieg

[jmckenna]

@pbuttigieg @fils the above is a great question submitted by the ICAN team. You can see that this primary key, the ODISCat ID, should be used for all of our ODIS queries, moving forward, for consistency (as they pointed out, that also means the front-end search API).

Please share your thoughts. thanks.