Adding DCAT and Schema.org repository description to the Dataverse homepage (#12022)

[juancorr]

What this PR does / why we need it:

• closes Feature Request: Add Schema.org and DCAT information in JSON-LD format to the repository homepage #12022

This PR is created to add Schema.org and DCAT information in JSON-LD format to the repository homepage in order to improve the visibility and trustworthiness of the repository. This could include:

Special notes for your reviewer:
It is a possible solution, obtaining the data from the setting table in the database. The json-ld data will be created into the html code:

[...]<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="description" content="Repositorio de Datos del Consorcio Madroño" />
<link rel="api-catalog" type="application/linkset+json" href="[http://bib6162invi6106:8080/resources/json/.well-known/api-catalog](view-source:http://bib6162invi6106:8080/resources/json/.well-known/api-catalog)" />
<script rel="describedby" type="application/ld+json">
{"@context":{"dcat":"http://www.w3.org/ns/dcat#","dct":"http://purl.org/dc/terms/","foaf":"http://xmlns.com/foaf/0.1/","rdf":"http://www.w3.org/1999/02/22-rdf-syntax-ns#"," ...................
</script><link type="text/css" rel="stylesheet" href="[/jakarta.faces.resource/ ............................
<link rel="apple-touch-icon" sizes="180x180" .............
[...]

Suggestions on how to test this:
Check the homepage to see that the json-ld code is into the html. It shouldn't be into other dataset or dataverse pages.

Additional documentation:
If this PR is approved, Dataverse api guide should be update too.

[pdurbin]

@juancorr thanks for the pull request! I added the "trusted data" label to this PR because it feels related to our work in that project, which is being tracked here:

• Project: Trusted Data dataverse-pm#425

To make this more concrete, Harvard Dataverse, for example doesn't programmatically expose any machine-readable information about its trustworthiness, etc. when you point a tool at its homepage. It looks this:

With this PR we can expose lots of machine-readable information like this:

I'm highlighting CoreTrustSeal above but there is all kinds of good stuff in there about what standards are supported and what APIs are available. For a complete list, see https://validator.schema.org/#url=https%3A%2F%2Fedatos.consorciomadrono.es%2F

[coveralls]

coverage: 24.069% (-0.1%) from 24.168%
when pulling 4986714 on Consorcio-Madrono:jsonInfoInHomePage
into d2b6a46 on IQSS:develop.

[juancorr]

Thanks @pdurbin for give context to the PR.
We can also inspect the dcat json metadata with the Google Rich Result test: https://search.google.com/test/rich-results

The code of this PR extract some information from the current Dataverse installation and settings database table, and allows adding extra information in the setting database using new fields:
:dcat_repository_country,
:dcat_repository_language,
:dcat_repository_research_area,
:dcat_repository_prev_policy,
:dcat_repository_terms,
:dcat_repository_license,
:dcat_repository_certification,
:dcat_repository_org_name,
:dcat_repository_access_terms,
:dcat_repositoryDescription

[pdurbin]

@juancorr we discussed this during our Trusted Data project meeting on Monday and during "Triage Tuesday" today. We gave it a status of "On Hold" because we don't plan to actively review and QA your solution until we've had time to consider other solutions as well. Thanks again for the PR!

[juancorr]

Thanks @philip Durbin ***@***.***> . I'll keep an eye out for any new proposals. El mar, 9 dic 2025 a las 19:56, Philip Durbin ***@***.***>) escribió:

…

*pdurbin* left a comment (IQSS/dataverse#12025) <#12025 (comment)> @juancorr <https://github.com/juancorr> we discussed this during our Trusted Data project meeting on Monday and during "Triage Tuesday" today. We gave it a status of "On Hold" because we don't plan to actively review and QA your solution until we've had time to consider other solutions as well. Thanks again for the PR! — Reply to this email directly, view it on GitHub <#12025 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACPSCB4MJ5SO2DR6CIDF5D4A4LPDAVCNFSM6AAAAACOFBU4O2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMZTHAYDEOJTGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>