Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding the right publishers @id and name to JSON-LD output #9613

Open
coret opened this issue May 24, 2023 · 2 comments
Open

Adding the right publishers @id and name to JSON-LD output #9613

coret opened this issue May 24, 2023 · 2 comments

Comments

@coret
Copy link

coret commented May 24, 2023

Datasetdescriptions, which are outputted as JSON-LD according to schema:Dataset currently have a publisher property of type schema:Organization and a schema:name. This can be traced back to the following code:

job.add("publisher", Json.createObjectBuilder()
.add("@type", "Organization")
.add("name", installationBrandName)
);

As an example from datasets on https://datasets.iisg.amsterdam/ you'd see
"publisher":{"@type":"Organization","name":"IISH Data Collection"}

In Linked Data, we like URI's, blank nodes are disliked.
The absence of an @id in the schema:publisher is strange, because schema:creator does have @id's in the GUI we see an identifier:

image

As the identifier (URI) is already available as data element within Dataverse, can this could be added to the publisher JSON-LD to become:
"publisher":{"@type":"Organization","@id": "https://datasets.iisg.amsterdam/dataverse/IISH","name":"IISH Data Collection"}

Although, are these Dataverse values really an schema:Organization? In this example the organization publishing the data via https://datasets.iisg.amsterdam/dataverse/IISH is the International Institute of Social History with URI http://www.iisg.amsterdam/.

I do see, this name and URI on https://datasets.iisg.amsterdam/dataverse/IISH so I'd imagine these values can be used in the publisher property to become:
"publisher":{"@type":"Organization","@id":"http://www.iisg.amsterdam/","name":"International Institute of Social History"}

@pdurbin
Copy link
Member

pdurbin commented May 24, 2023

@coret thanks for opening this issue. I'm not sure why some fields have @id's and some don't.

I'm reminded of what I think is a related discussion about what should be shown in the citation of a dataset. Should it continue to be the name of the installation of Dataverse (e.g. Harvard Dataverse)? Or should it be based on the collection the dataset happens to be in right now (it's possible to move datasets from one collection to another)? I posted some screenshots here: #2297 (comment)

@coret
Copy link
Author

coret commented May 24, 2023

@pdurbin in my opinion a Dataverse installation is a means used by an organization, two separate things with different meanings. For the datasetdescription the semantics of the schema:publisher is clear: it should be an organization. I'm no expert on citations, but I think you'd rather have the name of the organization, rather than the name of the means.

Or, maybe you could see the Dataverse Name as the name of a collection (as I see users are doing). But my argument would stay the same for the datasetdescription (organisation, not collectionname). For the citation, a collectionname should be included, of course next to the organization name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants