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

Solve compatibility issue for Dataverse software #2

Open
abollini opened this issue Sep 19, 2021 · 3 comments
Open

Solve compatibility issue for Dataverse software #2

abollini opened this issue Sep 19, 2021 · 3 comments

Comments

@abollini
Copy link

Dataverse has included support for the unreleased version of the guidelines in v4.14 thank to the 4Science funded contribution IQSS/dataverse#4664

Unfortunately, the output generated by Dataverse is toward this unreleased version and it is not clear if further changes are required due to update since the original development (at this time datacite schema v.4.1 was used)

The dataverse community is now discussion a refactoring improvement of the datacite export it would be important to bring arguments from the OpenAIRE team to this discussion IQSS/dataverse#5889 and keep the two threads aligned

@abollini
Copy link
Author

@joschirr @ACz-UniBi do you have any update on that? Other than dataverse also dspace-cris provides support out-of-box for the new version of the Data Archive guideline based on the datacite schema version 4.
Please keep in mind that the Datacite schema version 3 is deprecated and it would be a no sense for platform maintainer to support it: it is approaching the 10th birthday...

@jggautier
Copy link

jggautier commented Apr 2, 2024

Hi all. @abollini, last week I updated the GitHub issue at IQSS/dataverse#5889 to propose merging Dataverse's "Datacite" and "OpenAIRE" exports. The proposal is in the comment at IQSS/dataverse#5889 (comment). We're still looking into when we can start the development work on this, but it's a priority.

In the proposal, I write that the schemaLocation element of the merged export will point to the xsd of DataCite's 4.5 schema, instead of the 4.1 schema that the OpenAIRE export points to now. And I wrote that we should follow up with you about this.

Are there reasons why we should not have the schemaLocation point to the xsd of DataCite's 4.5 schema?

You wrote that it would be important to "bring arguments from the OpenAIRE team" to the discussion in our GitHub issue at IQSS/dataverse#5889. I would love to hear from the OpenAIRE team, too, about this and other topics related to sending metadata to OpenAIRE's systems.

@jggautier
Copy link

Hi again @abollini. Last week I learned that we'll continue working this week and up to next Wednesday on "merging" Dataverse's "Datacite" and "OpenAIRE" exports. We'll be assuming that OpenAIRE's systems will still be able to harvest and index the metadata in the XML, even if the schemaLocation points to DataCite's 4.5 schema instead of its 4.1 schema.

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

No branches or pull requests

2 participants