Connect CCHDO into ODIS

[cberys]

The CCHDO will initiate a request to be included in ODIS https://cchdo.ucsd.edu/

sitemap https://cchdo.ucsd.edu/sitemap.xml

[jmckenna]

thanks @cberys

@pbuttigieg here is a sample record, which has JSON-LD & validates through schema.org : https://cchdo.ucsd.edu/cruise/61TG20020206

[pbuttigieg]

Thanks @cberys

As we saw in our ESIP meeting just now, the JSON-LD/schema.org embedded in the webpages linked to your sitemap looks good, we could try test indexing right away.

@fils @jmckenna - these have DataCatalog types containing many Datasets with arrays of geospatial coordinates using schema.org - this should harvest, but I'm not sure how the DataCatalog type will interact with Dashboard counts and SOLR searches

@cberys in the meantime, you could set up an OceanExpert account for the manager of this resource and an ODISCat entry for your data source, as we discussed. ODIS will look at the ODISCat entry to find your sitemap.

[jmckenna]

@pbuttigieg @fils here is the JSON-LD for that record:

{
  "@context": {
    "@vocab": "http://schema.org/",
    "geolink": "http://schema.geolink.org/1.0/base/main#"
  },
  "@id": "https://cchdo.ucsd.edu/cruise/61TG20020206",
  "@type": "DataCatalog",
  "dataset": [
    {
      "@id": "https://cchdo.ucsd.edu/cruise/61TG20020206#bottle",
      "@type": "Dataset",
      "description": "Bottle data from the hydrographic cruise 61TG20020206",
      "distribution": [
        {
          "@type": "DataDownload",
          "contentSize": "81524 bytes",
          "contentUrl": "https://cchdo.ucsd.edu/data/6374/61TG20020206_hy1.csv",
          "encodingFormat": "text/csv",
          "name": "exchange"
        },
        {
          "@type": "DataDownload",
          "contentSize": "182324 bytes",
          "contentUrl": "https://cchdo.ucsd.edu/data/39212/61TG20020206_bottle.nc",
          "encodingFormat": "application/x-netcdf",
          "name": "cf_netcdf"
        }
      ],
      "isAccessibleForFree": true,
      "name": "NZ GO-SHIP Hydrographic Cruise 61TG20020206: Bottle Dataset",
      "provider": {
        "@id": "https://cchdo.ucsd.edu"
      },
      "publisher": {
        "@id": "https://cchdo.ucsd.edu",
        "@type": "Organization",
        "name": "CCHDO",
        "url": "https://cchdo.ucsd.edu"
      },
      "spatialCoverage": {
        "@id": "https://cchdo.ucsd.edu/cruise/61TG20020206#spatialCoverage",
        "@type": "Place",
        "geo": [
          {
            "@type": "GeoCoordinates",
            "description": "Profile 1",
            "latitude": -66.4217,
            "longitude": 139.993
          },
          {
            "@type": "GeoCoordinates",
            "description": "Profile 2",
            "latitude": -64,
            "longitude": 139.998
          },
          {
            "@type": "GeoCoordinates",
            "description": "Profile 3",
            "latitude": -65.435,
            "longitude": 139.85
          },
          {
            "@type": "GeoCoordinates",
            "description": "Profile 4",
            "latitude": -64.748,
            "longitude": 139.84
          },
          {
            "@type": "GeoCoordinates",
            "description": "Profile 5",
            "latitude": -63.248,
            "longitude": 140.015
          },
          {
            "@type": "GeoCoordinates",
            "description": "Profile 6",
            "latitude": -62.5,
            "longitude": 140.003
          },
          {
            "@type": "GeoCoordinates",
            "description": "Profile 7",
            "latitude": -61.75,
            "longitude": 140.002
          },
          {
            "@type": "GeoCoordinates",
            "description": "Profile 8",
            "latitude": -61,
            "longitude": 139.998
          }
        ]
      },
      "temporalCoverage": "2002-02-06/2002-03-07"
    }
  ],
  "description": "Data from the hydrographic cruise 61TG20020206",
  "keywords": [
    "TANGAROA",
    "bottle",
    "T Odate",
    "CARINA",
    "GO-SHIP",
    "southern",
    "SR03",
    "indian"
  ],
  "name": "NZ GO-SHIP Hydrographic Cruise 61TG20020206"
}

[cberys]

Thank you @pbuttigieg and @jmckenna!

I'm tagging Alan Yang @axyangsio who will be the manager of the resource.

Also - I want to confirm that this is still a preliminary assessment and we will be able to adjust our json-ld before it is publicly displayed and integrated, is that correct?

[pbuttigieg]

Thank you @pbuttigieg and @jmckenna!

I'm tagging Alan Yang @axyangsio who will be the manager of the resource.

Also - I want to confirm that this is still a preliminary assessment and we will be able to adjust our json-ld before it is publicly displayed and integrated, is that correct?

Yes, it's up to each node when they want to go live, and they can always update their holdings unilaterally.

However, we can test your current (valid) JSON-LD/schema.org content in our staging graph as an initial check .

I recommend you create your ODISCat entry for the resource in preparation.

[axyangsio]

Hi I did a testing submission for CCHDO data:

CLIVAR AND CARBON HYDROGRAPHIC DATA (ODIS ID: 3291)

[jmckenna]

@axyangsio regarding your sitemap, we'll be using the parameter changefreqto know how often to harvest your endpoint (see note), could you add it to your sitemap?