Standardizing how standard licenses are configured in the Dataverse software

[Philipp at UiT]

A couple of months ago, I submitted a GitHub issue about standardizing the way standard licenses are configured in the Dataverse software. Currently, the way license information is configured and exposed to DataCite needs some changes to make it aligned with the recommendations from DataCite. I guess this might be of interest to many if not all Dataverse installations using dataset (and optionally file) DOIs provided by DataCite, so you might want to join the discussion on GitHub or by replying to this Google group discussion thread. Thanks!

Best, Philipp

[Philipp at UiT]

An update: One of the consequences of the license information in Dataverse not being aligned with the DataCite recommendations is that the discovery services relying on DataCite, e.g., Primo (see this discussion thread), treat all datasets from Dataverse-based repositories as not accessible. For details, see the GitHub issue.

[Lilian Vallejo Bustamante]

hola, busco proveedor 

[Philip Durbin]

JP and I just wrote some guidance on adding licenses the future: https://github.com/IQSS/dataverse/pull/10426#issuecomment-2050108042

Please take a look and let us know what you think!

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/2b11c24d-0567-4f32-a3ed-69c4ee61d3cfn%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin