Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Problem: cannot store AIP in DSpace due to file extension returned #69
You should be able to store an AIP in DSpace. The AIP is chunked into 2 parts- one for the objects and one that contains all the metadata, logs, etc.
When you attempt to store an AIP in DSpace it will deposit successfully, but the Storage Service is returning an error because of DSpace returning an extension for one of the AIP chunks as .atom. In this function: https://github.com/artefactual/archivematica-storage-service/blob/5a94ce5e8a19be6fff22848bd366f6d6eb2c731d/storage_service/locations/models/package.py#L1210-L1247 the SS is expecting either the extension .7z or .bz2. Note that the DSpace space in the SS is "special-" you can set it to make zip files from your AIP chunks instead of 7z or bz2.
The Dashboard fails in Store the AIP job and the SS logs contain this error:
Steps to reproduce
To store an AIP in DSpace, ensure you have configured the location/space correctly and also it is expecting several pieces of DC metadata (I forget exactly which ones so I've been filling out the whole DC template in testing).
Your environment (version of Archivematica, OS version, etc)
Archivematica qa deployed on a VM, with Storage Service 0.12 release candidate.
How to reproduce and QA:
Set up DSpace Space
Make sure that
Add location AIP Storage
Start the transfer!
pushed a commit
Oct 10, 2018
referenced this issue
Oct 10, 2018
@sevein - test continuously fails during Store AIP. Keep getting error that looks like this:
@sevein - I've also tested locally on my Compose environment and checked the logs:
Seems like I need to make /var/archivematica/storage_service_dspace writable ?
So I created and made that directory writable, then ran a new transfer per your specifications in comments ^.
Now getting this cryptic error in the logs...
Thanks @mamedin for restarting dspace server.
For some reason, I'm not getting that latest commit/bug fix when I update. Not sure why that is happening. If that was resolved, then I think we could put this bugger to bed.
If you're using compose:
So similar to https://github.com/artefactual-labs/am/tree/master/compose#upgrading-to-the-latest-version-of-archivematica but it does not assume that the submodules are up to date!