After a discussion in today's Community Call about sending DataCite file-level metadata that includes the file checksum, @mercecrosas added in this Google Groups comment a table recommending ways to map to schema.org more dataset.

The table includes more metadata fields that have been added.

An open question, that might deserve its own github issue, is if Dataverse should produce schema.org metadata at the file level.

Let's exclude File Download URL for now. It can follow on in a separate issue.

Thanks to @jggautier I was able to track down some tools for validating schema.org JSON-LD. https://github.com/jessedc/ajv-cli can be used from the command line to validate the JSON against a schema ; after using https://github.com/scrapinghub/extruct to retrieve the JSON-LD from the generated html/xhtml.

I just made the changes @jggautier @scolapasta @djbrooke @kcondon and I agreed to after standup:

• 3a95edf remove "schemaVersion" from output As a researcher, I want more dataset metadata in schema.org exports so that my data is more discoverable #4371
• 50bc8ca remove "url" from output As a researcher, I want more dataset metadata in schema.org exports so that my data is more discoverable #4371
• 882cbfb clarify publisher vs. provider comment As a researcher, I want more dataset metadata in schema.org exports so that my data is more discoverable #4371
• 7cd5622 single "isValidAuthorIdentifier" method, pass in regex As a researcher, I want more dataset metadata in schema.org exports so that my data is more discoverable #4371

So, aside from internal code restructuring, this pr:
-adds new fields to schema.org
(create/export dataset, verify against list julian provides)
-changes the structure of some fields in schema.org (multiple, object type)
(same as above, add multiple where appropriate, paste into Google validation tool)
-adds optional hide files jvm option to block download urls in export
(verify on/off behavior and pubic/restricted file behavior)
-publisher and provider will be the instance name (root dv)
(verify against export)

Issues/questions:

1. files/distribution section contains additional, unspecified info: file name, pid.
2. author id is missing if value is entered in a nonconforming format but not indication exists what the conforming format is.

Discussed above with Julian and he will complete review. Will discuss with Julian and Phil to see what needs to be addressed.

Another issue:

3. The URLs for the related publications show up wrapped in html:

"citation": [
    {
      "@type": "CreativeWork",
      "text": "Related pub citation 1",
      "@id": "<a href=\"https://doi.org/10.7910/DVN/P7EVGF\" target=\"_blank\">https://doi.org/10.7910/DVN/P7EVGF</a>",
      "identifier": "<a href=\"https://doi.org/10.7910/DVN/P7EVGF\" target=\"_blank\">https://doi.org/10.7910/DVN/P7EVGF</a>"

4. @id is missing from the files/distribution section @kcondon mentioned in his comment (@pdurbin and I agreed to keep the extra file info.) We're always using @id whenever identifier is used. I discussed with @pdurbin and he'll update.

"distribution": [
    {
      "@type": "DataDownload",
      "name": "file1.txt",
      "fileFormat": "text/plain",
      "contentSize": 26,
      "description": "File description 1",
      "identifier": "https://hdl.handle.net/20.500.12050/FK2/TWFVRE/222222",
      "@id": "https://hdl.handle.net/20.500.12050/FK2/TWFVRE/222222",
      "contentUrl": "https://demo.dataverse.org/api/access/datafile/:persistentId?persistentId=doi:10.5072/FK2/CFWNSH/ZEHFD0"

(contentUrl should appear only when the installation indicates that they want download URLs appearing in their schema.org exports.)

Yep, I got rid of the "href" stuff in fcae94e and added @id at the file level in 0e0b55d.

I looked at the schema.org export and all four issues are resolved!

@kcondon noticed that contentUrl isn't showing up in the schema.org export of a test dataset, although we expect it to. (It's the dataset titled "Test Schema Org Julian 5 Schema" on the "internal" test instance.)

For the record, as discussed with @kcondon and @jggautier , the FileUtil.isPubliclyDownloadable logic is used to contentUrl wasn't being shown because the dataset had terms of use. It also checks for guestbooks. Both of these require a popup to agree to or fill out in the UI.