Open jm-jones opened 4 years ago
Hi, Jasmine,
I wrote the plugin to support Harvard's workflow, which depends upon the auto-generation of Ref IDs; indeed, I know that most other institutions that use this plugin also use some auto-gen algorithm.
You can see what Harvard does to take advantage of auto-generation at: https://github.com/harvard-library/aspace-refid_rules
I'm sorry this doesn't apply to your workflow. I'm going to mark this as an enhancement request.
Thanks so much, Bobbi, for this plugin, as well as information about how Harvard's use of auto-generation of ref IDs. I appreciate you marking this as an enhancement request.
Hello. We have been testing import of both the Archival Object and Digital Object spreadsheets, so that we can get more information into the digital object records than we are able to just via the archival object spreadsheet. However, I'm finding that the Ref ID values that I'm inputting into the archival object spreadsheet are not being imported into the resource record. (This is the only content that is not being imported as input.) Are there requirements on the characters in that field that might be hindering import, other than that it should be a string? I know that the ref ID field is really important for pairing the digital object instances with their archival object components, so figuring out this gap in the workflow is key. Any feedback would be very welcome and appreciated.
Thanks so much -- Jasmine Jones
P.S. Hi Dave. Hope you are doing well!