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

FORS change of identifiers #640

Open
john-shepherdson opened this issue Mar 13, 2024 · 5 comments
Open

FORS change of identifiers #640

john-shepherdson opened this issue Mar 13, 2024 · 5 comments
Assignees
Labels
external Issues caused by upstream dependencies

Comments

@john-shepherdson
Copy link
Contributor

From: Guillaume Lefebvre
Date: Fri, 8 Mar 2024 at 10:59
Subject: Question about OAI-PMH harvesting and identifier change
To: John Shepherdson

As you know, our application SWISSUbase is currently harvested by the CESSDA catalogue.

In a near future, we plan to change some bits about how our internal dataset versioning works within SWISSUBase. This would imply that we would change some metadata identifiers currently provided through our OAI-PMH endpoint

First, we will need to change the OAI-PMH record header "identifier" field from something like "oai:swissubase.ch:1000-1-0", to "oai:swissubase.ch:9517409b-6854-48cf-913a-2e84ea4782bd"
Second, we currently provide 2 IDNo within DDI profile, one being a DOI identifier and the other being an internal SWISSUbase identifier. We will drop the latter, only keeping the DOI identifier as unique IDNo.
Basically we we would like to know how to proceed with this ? I expect that records cannot be really updated, since the record "identifier" will change. So:

Shall we ust release our new SWISSUbase version with new versioning scheme, then it will be harvested by CESSDA, duplicates will be created, and CESSDA can then drop the old records ?
Shall we sync our release with CESSDA, so that old records are dropped first, and then new ones are harvested ?
Do you have another solution to propose ?

@john-shepherdson
Copy link
Contributor Author

john-shepherdson commented Mar 13, 2024

I think we should drop their current records then harvest the new ones. Any reason why not?

@matthew-morris-cessda matthew-morris-cessda added the external Issues caused by upstream dependencies label Mar 13, 2024
@matthew-morris-cessda
Copy link
Contributor

I don't think we need to do anything. The old records will be automatically deleted and having 2 IDNo elements isn't an issue, as we deal with this in other repositories.

@matthew-morris-cessda matthew-morris-cessda closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
@matthew-morris-cessda matthew-morris-cessda added the invalid This doesn't seem right label Mar 13, 2024
@john-shepherdson
Copy link
Contributor Author

Why will the old records be deleted automatically? The new records will have a different value in the OAI-PMH record header "identifier" field, won't they be considered to be different records from the existing ones?

@matthew-morris-cessda
Copy link
Contributor

Yes, that's why the old records will be automatically deleted. The pipeline will see the old identifiers as orphaned and delete them, and write out the records with the new identifiers.

@matthew-morris-cessda matthew-morris-cessda removed the invalid This doesn't seem right label Apr 23, 2024
@matthew-morris-cessda
Copy link
Contributor

@MortenSikt Could you follow this up with SWISSUbase?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external Issues caused by upstream dependencies
Projects
None yet
Development

No branches or pull requests

3 participants