[Archivesspace_Users_Group] Digital object import behavior 2.8.0 vs. 2.8.1
Rees, John (NIH/NLM) [E]
reesj at mail.nlm.nih.gov
Wed Dec 9 10:13:59 EST 2020
We're on v.2.8.0 and are experimenting with the new Digital Object spreadsheet importer to append DO's to existing archival objects.
In 2.8.0, I understand that import will fail where another DO already exists which is a use case I'm testing. However, using the ASpace 2.8.1 sandbox I get the same processing error, but the job is still successful when there are pre-existing DOs. Is that expected behavior? See my real-world example at http://test.archivesspace.org/staff/resources/193/edit#tree::archival_object_43056 (JPR4 and 5 are the new imports)
Question 2: in v.2.8.0, the import process fails unless either file URN or thumbnail URN is included. This is not documented as a required element. With 2.8.1 imports with these fields empty run fine. Is this expected behavior? We are importing DOs as a pre-flight exercise and don't have URNs yet. We'd have to add dummy data and deleted afterwards.
I'm reckoning the solution to my 2.8.0 problems is moving to 2.8.1?
John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine
Teleworking M-F 8:00AM - 4:30PM Eastern Time each day until further notice
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group