At the December 11th meeting I mentioned the prospect of modifying the
schema.org JSON-LD that is embedded in ArchiveGrid records to include the Archive and ArchiveComponent types and the holdingArchive relationship.
I've finally implemented that change (for uninteresting reasons it necessitated moving ArchiveGrid to a new platform), and have been testing this change for the past week or so. I think it's ready for some wider evaluation. If you have a chance, could you take a look and give me advice on how to improve upon this?
All of the 5.4M ArchiveGrid records that are based on MARC records in WorldCat include JSON-LD
schema.org data in their HTML source.
Here's an ArchiveGrid search to return MARC records:
And here's a URL to view one of those records in the Google Structure Data testing tool, which should detect and display the embedded JSON-LD:
The testing tool throws errors for the (currently) unrecognized Schema.org classes and predicates, as expected.
I have questions about rendering information about the institution that holds the item.
My previous practice had been to make use of the "offers" relationship and the "offeredBy" structure to link to the associated institution:
"offers": {
"@type":"Offer",
"offeredBy": {
"@type": [
"Organization",
"Archive"
],
"name":"American Antiquarian Society"
}
}
I've retained that structure, and have added a parallel "holdingArchive" relationship:
"holdingArchive": {
"@type":"Archive",
"name":"American Antiquarian Society"
}
I noted that ArchivesSpace is now embedding JSON-LD on collection pages (on at least some sites), where the "provider" relationship is used to indicate the responsible institution.
"provider": {
"@id": null,
"@type": "Organization",
"name": "Archives of Appalachia"
}
So I'm wondering what the best practice is, and whether the parallel rendering I've adopted would be acceptable, at least for now.
Thanks,
Bruce