Open coret opened 6 months ago
Discussed today and decided:
Would it be an option to consider schema.org
Types for the genres? Upside: follows NDE recommendations. Downside: difficult to add new types.
We could use sdo:
We miss sdo
types for genres:
sdo:PropertyValue
could do)sdo:Time
)@ddeboer and @EnnoMeijers can you give your ideas about using schema.org for the genres in the NoT dataset description?
Using schema.org as a generic ontology for classes and properties is a NDE recommendation. Using schema.org as a controlled vocabulary for NoT-genres only makes sense when there is a clear match for all genres. I don't have any objections to using a NoT/domain specific LOD-list to offer a complete and fined-grained list of genres.
Thanks for your reply @EnnoMeijers . I did not find a vocab suitable for our use yet. Perhaps we should make our own genre list using PoolParty? Benefit is that we can expand it when needed. I can maintain the list.
@ddeboer I've started with a genre list that we can use to categorize the datasets: https://data.cultureelerfgoed.nl/termennetwerk/onderwerpen.html
Let me know if this works for you. If you can adapt the json-ld datasets descriptions, I can add the genres per dataset.
Hi @ddeboer do you have enough to work with to implement a genre category in the dataset descriptions? I can fill in the specific genres per dataset if you can set up the fields in the json-ld files.
@rschalkrce You can now add the genres to https://github.com/netwerk-digitaal-erfgoed/network-of-terms/pull/1333.
As a first step, the genres are now shown at https://termennetwerk.netwerkdigitaalerfgoed.nl/reconciliation.
@rschalkrce Just wondering: should ‘Actoren en organismen’ perhaps be ‘Actoren en organisaties’?
To help heritage organisation select the right terminology source(s) to use, a new "selection aid" function in the NoT demonstrator would be needed.
Prototype by @rschalkrce:![image](https://github.com/netwerk-digitaal-erfgoed/network-of-terms-demo/assets/101820/1a573928-183c-45e9-b41c-debc24b7381b)
For this function to work the terminology source descriptions (such as https://github.com/netwerk-digitaal-erfgoed/network-of-terms/blob/master/packages/network-of-terms-catalog/catalog/datasets/cht.jsonld) should be expanded with a
schema:genre
property with one or more values from a controlled-by-us (or standard) vocabulary (in Dutch and English).The GraphQL API should be expanded in order for the demonstrator to query terminology source (datasets) on one or more selected 'genres'.
Additionally, it would be nice to give more information about a terminology source via this selection aid or an overview of terminology sources page, like
schema:mainEntityOfPage
andschema:description
. In the future, information from the Dataset KG about terminology source usage could be included (or used for sorting).