Schema.org dataset metadata doesn't include file PIDs on Harvard Dataverse

[jggautier]

The Dataverse 4.10 release includes additions to the dataset metadata that Dataverse publishes in schema.org JSON (#4371). On Harvard Dataverse, it looks like all of those additions show up the way we expect them to except for file persistent IDs. (If the last version of a dataset was published before Harvard Dataverse was upgraded on Jan 8, its schema.org metadata won't have extra fields, yet).

This is what some of the file metadata looks like for this dataset:

"distribution": [
    {
      "@type": "DataDownload",
      "name": "ESCOManalyses_SR.do",
      "fileFormat": "application/x-stata-syntax",
      "contentSize": 7436,
      "description": "Stata do file that replicates analyses reported in the article and appendix, with the exception of the Bayesian analyses that were conducted using R.",
      "contentUrl": "https://dataverse.harvard.edu/api/access/datafile/3317147"

Below "contentUrl" there should be "@id" and "identifier" properties.

Demo Dataverse was also upgraded to 4.10 and does include the file PIDs, e.g. for this dataset (which doesn't include "contentURL" because it's a restricted file):

"distribution": [
    {
      "@type": "DataDownload",
      "name": "CallForSponsors2019.pdf",
      "fileFormat": "application/pdf",
      "contentSize": 146336,
      "description": "File description",
      "@id": "https://doi.org/10.5072/FK2/ALQKV2/F4EVJR",
      "identifier": "https://doi.org/10.5072/FK2/ALQKV2/F4EVJR"

I'm not sure why it shows up in schema.org metadata on Demo Dataverse but not on Harvard Dataverse.

[jggautier]

@pdurbin mentioned that we're not seeing the file PIDs in the dataset metadata on Harvard Dataverse because Harvard Dataverse turned off file PIDs recently. Closing this ticket.