bondjimbond
commented
7 years ago Some thoughts on those questions...
What does it mean to "update" a DOI?
Does "Update" also include "delete", or is that a separate task? Cases where a DOI should be deleted - if object already has one from another source and a new one was minted accidentally.
URL change use cases
Yes, ideally a URL would only change with migrations, but in reality humans work a bit more messily. e.g. one of our sites batch loaded thousands of theses, decided the metadata was no good, and mass deleted them all. Then they re-ingested those same objects, which of course got new PIDs assigned and therefore new URLs.
This happens fairly frequently. If DOIs were minted for each of these, their URLs would certainly need to be updated.
The above is also a use case for the batch updating question.
mjordan
This is a general issue to track ideas for batch assignment and updating of DOIs. Work on individual aspects of the functionality described below should be addressed in their own issues.
Batch assignment of DOIs
A known use case (Simon Fraser University Library's) is that after enabling this module, the repo admin wants to assign DOIs to a large set of existing objects.
This should be in principle easy, since we can reuse the functionality we already have for assigning DOIs to individual objects via the GUI. The biggest challenge is that only objects that have metadata that meets DataCite's (and probably other registrars') requirements can be assigned DOIs, and in practice this is not very common. One particularly challenging aspect of DataCite's metadata requirements is that its mandatory 'resourceType' element must use values from the following list: 'Audiovisual', 'Collection', 'Dataset', 'Event', 'Image', 'InteractiveResource', 'Model', 'PhysicalObject', 'Service', 'Software', 'Sound', 'Text', 'Workflow', and 'Other'.
Any bulk DOI assignment tool needs to be able to detect whether an object has the required metadata, and report out and skip objects that do not. It might also be useful to be able to "audit" a set of objects prior to assignment to see how many pass and how many fail. The repo admin can then add metadata to the failures and try again.
What does it mean to "update" a DOI?
Assuming that the DOI identifier itself never changes (that's its purpose), "updating" a DOI should be limited to updating the metadata and location (URL) of the resource identified by the DOI. There is already an option to do this manually in the GUI, and the DataCite module supports it. The most common use case here is that we want to push changes in local metadata to the registrar, e.g., after the local object's MODS datastream is updated.
But why would be update an object's URL? URLs for Islandora are persistent. Is the only use case for updating a URL associated with a DOI for an Islandora object if the Islandora URL is not longer viable, e.g., after migration from Islandora to another platform?
Batch updating of DOIs
How likely is it that we will need to update the metadata for a set of objects? If we have a way of updating the DOI metadata when the local objects are modified, probably not very likely. If we don't automatically update the metadata, we may want to be able to give the repo admin the ability to "sync" the local metadata with the DOIs.
As suggested above, updating the URLs associated with a DOI will probably only happen after a migration away from Islandora, in which case the URLs associated with the DOIs will need to be updated.