connect UNEP (WESR) catalogue as ODIS node

[jmckenna]

• current status:
  • WESR team has enabled CKAN-DCAT extension, on dev server, to enable JSON-LD on each record page
  • production catalogue: https://wesr.unep.org/
  • WESR team to generate a sitemap.xml, to point to each catalogue page (that embeds JSON-LD)

cc @sobiero

[fils]

@jmckenna

During the call with WESR got the following URLs for us to inspect.

• https://stg-data.unep.org/app/
• https://stg-data.unep.org/dc/catalog.rdf
• https://stg-data.unep.org/dc/catalog.xml
• https://stg-data.unep.org/catalog.xml?page=1

Jeff, Simon Mogaka asked if you could send him the information on the JSON-LD/schema.org plugin for CKAN.

[sobiero]

@fils @jmckenna Please note the last link should be https://stg-data.unep.org/dc/catalog.xml?page=1 as the catalogue has been installed on the path /dc/

JSON-LD endpoint: https://stg-data.unep.org/dc/catalog.jsonld?page=1

And the documentation for the DCAT endpoint is available at: https://extensions.ckan.org/extension/dcat/#catalog-endpoint

[jmckenna]

updates from last meeting:

• catalogue is live: https://datacatalog.unep.org/app/
  • sample record: https://datacatalog.unep.org/app/dataset/unep-wcmc-rsrc-report-nature-risk-profile--a-methodology-for-profiling-nature-related-dependencies-a

Action items:

1. WESR implements the CKAN-DCAT extension on their CKAN pages, so each page contains JSON-LD/schema.org content for ODIS to harvest
   • must set the default profile to be schemaorg in the extension
2. WESR creates a sitemap.xml to point to the JSON-LD pages
   • for more info on the sitemap, see: https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap
3. WESR creates an entry in ODISCat for its catalogue
   • login with your OceanExpert ID and click Add
   • important fields are Startpoint URL for ODIS-Arch (this is your sitemap url) and Type of the ODIS-Arch URL (choose sitemap)
4. ODIS creates an export for WESR to harvest, developed in its archinterfaces directory
   • UPDATE: directory shell is created at archinterfaces/ODIS-WESR, where steps will be shared
5. ODIS and WESR test exchanges to make sure they can cross-index each other's resources
6. ODIS figures out how to extract ocean-relevant content from WESR

[jmckenna]

Updates from meeting on 2023-11-24:

• Herbert enabled entry of UNEP into the ODIS Catalogue using Ocean Expert ID and login details that we provided him. https://catalogue.odis.org/view/3288
• WESR implemented the CKAN-DCAT extension on their CKAN pages, so that each page contains JSON-LD/schema.org content for ODIS to harvest.
• WESR had also created a sitemap.xml to point to the JSON-LD pages https://datacatalog.unep.org/en/oceans_sitemap.xml
• From our side (GEMS Ocean), we identified ocean-relevant datasets from WCMC, GPML, and SDG groups that the ODIS could consume. Please find link to the Ocean Relevant Data Sets

[jmckenna]

from Hyrence email: Please find attached a document with some fields sourced from Ocean Info Hub for what we would like to pull. As per our previous discussion, the metadata we would like to obtain for the topics through your JSON API include; Title, description, source url, last-updated, keywords/category/variables attached, spatial, provider/organisation, provider email, data type e.g. html, doc, excel, etc,. More specifics could be discussed in the next meeting.

Data Sets R.xlsx

[pbuttigieg]

@fils @jmckenna

The next steps:

• We should test the WESR harvest through the sitemap they've provided
• We need to set up some queries that WESR can modify, to extract JSON-LD records with the keywords (including those in DefinedTerm stanzas) and variableMeasured values specified in the XLSX file here