You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful to be able to produce MODS.xml files or others so they are named ready to be used as input to Islandora Datastream CRUD. The main use case here is using MIK to regenerate MODS files from CSV input for bulk replacement of bad or incomplete MODS datastreams (yes that is sadly a real thing) of MODS that were-good-enough-at-the-time-of-initial-ingest-but-now-that-collection-owners-have-changed-their-minds-we-need-to-replace-the-MODS. 😞
Since Datastream CRUD requires that filesnames encode the target object's PID, e.g., islandora_1300_MODS.xml, this post-write script would need a filename -> CRUD-friendly filename map. This could be supplied in an external CSV file.
The text was updated successfully, but these errors were encountered:
It would be very useful to be able to produce MODS.xml files or others so they are named ready to be used as input to Islandora Datastream CRUD. The main use case here is using MIK to regenerate MODS files from CSV input for bulk replacement of bad or incomplete MODS datastreams (yes that is sadly a real thing) of MODS that were-good-enough-at-the-time-of-initial-ingest-but-now-that-collection-owners-have-changed-their-minds-we-need-to-replace-the-MODS. 😞
Since Datastream CRUD requires that filesnames encode the target object's PID, e.g.,
islandora_1300_MODS.xml
, this post-write script would need a filename -> CRUD-friendly filename map. This could be supplied in an external CSV file.The text was updated successfully, but these errors were encountered: