You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Artsdata-minted entities have very shallow metadata. It's mostly administrative metadata and straight URIs in lieu of fully-fleshed nested objects. In the current state, if an Indigenous arts organization went to Artsdata, found there minted event (created by the Indigenous Librarian and then minted in Artsdata, and wanted to cut-and-paste their event structured data on their website, here's what they would get:
{
"@context": "https://kg.artsdata.ca/context.jsonld",
"id": "http://kg.artsdata.ca/resource/K43-973",
"type": "Event",
"sameAs": "http://indigenous-performances/row/temporary/797a9e93bde44055b16d9dfed25185bb",
"additionalType": "http://kg.artsdata.ca/resource/TheatrePerformance",
"location": "http://kg.artsdata.ca/resource/K2-5373",
"description": {
"@none": "Three basic cousins attend the 222nd Annual Powwow, but everything has changed. The powwow committee has sold out to a controlling corporation known as \"The Watcher\"; undoing all policy and rewriting all rules. For the first time in history, the powwow has become a competition bringing forth the cousins' nemesis and keeping the cousins and the emcee gripping with their own internal conflict and a fight to save the powwow. Playwright April Rogers is an alumni of GTNT’s Circle of Voices program and Powwow is their first produced work as a playwright. Powwow was commissioned by GTNT through the New Voices program - a GTNT initiative to cultivate the next generation of storytellers. New Voices is a paid, six month residency program focused on developing new Indigenous writers."
},
"image": "https://gtnt.ca/wp-content/uploads/2024/06/Powwow-HD.png",
"name": {
"@none": "Powwow a Theatrical Production"
},
"startDateTime": "2025-06-01T14:00:00-06:00",
"url": "https://gtnt.ca/production/powwow-a-theatrical-production/",
"generatedAtTime": "2025-01-23T22:04:19.536Z",
"skos:historyNote": "Minted Arstsdata ID for schema:Event named 'Powwow a Theatrical Production' on 2025-01-23T22:04:19.536Z"
}
This JSON-LD is light coded and super-efficient as long as it is used in Artsdata. However, it is not good enough for reuse into an arts organization's website:
The context is not schema.org;
organizer and performer data from the Indigenous Librarian's source spreadsheet is not reflected;
If the source had offer data, it would also be missing.
How could we provide Artsdata users a means of accessing fully parsed structured data with the schema.org context (and copying it to their clip board)?
The text was updated successfully, but these errors were encountered:
Currently, the scripts for generating JSON-LD in both the A10s prototype and in Artsdata smart chip prototype are not robust enough. When we create a copy of the sheet, the script does not follow / or else we are somehow breaking it as we edit the sheet.
If Artsdata was able to generate full JSON-LD, it might be better to direct spreadsheet users to the knowledge graph interface rather than providing this functionality in the spreadsheet.
Currently, Artsdata-minted entities have very shallow metadata. It's mostly administrative metadata and straight URIs in lieu of fully-fleshed nested objects. In the current state, if an Indigenous arts organization went to Artsdata, found there minted event (created by the Indigenous Librarian and then minted in Artsdata, and wanted to cut-and-paste their event structured data on their website, here's what they would get:
JSON-LD from http://kg.artsdata.ca/resource/K43-973
This JSON-LD is light coded and super-efficient as long as it is used in Artsdata. However, it is not good enough for reuse into an arts organization's website:
organizer
andperformer
data from the Indigenous Librarian's source spreadsheet is not reflected;offer
data, it would also be missing.How could we provide Artsdata users a means of accessing fully parsed structured data with the schema.org context (and copying it to their clip board)?
The text was updated successfully, but these errors were encountered: