Need some help with AIP backup/ingest

97 views
Skip to first unread message

Bill T

unread,
Dec 13, 2016, 4:43:44 PM12/13/16
to DSpace Technical Support
In DSpace 5.x, I'm attempting to use AIP in submission mode to ingest a community from another site.  The community contains a handful of collections each of which has some items.  My command to do this is:

./dspace packager -s -a -t AIP -e a...@some.com -p 12345/6 /path/to/my/zip.zip

where 12345 is my handle prefix

The tool responds with

Destination parents:
Owner: 12345/6

Ingesting package located at...

Also ingesting referenced packages (recursive mode)...

And then the well-known: Could not find a parent DSpaceObject referenced as '56789/1' in the METS Manifest for hdl:56789/2' etc etc error and the command returns immediately
(where 56789 is the other site's handle prefix.)

None of the items are mapped, by the way.  Shouldn't the -parent option on the command line override what is in the METS?

Naturally, none of the child collections or items are created since the command fails right away, but the dspace log indicates the creation of the brand new community, within the correct, existing community. Although when I actually check the handle, the community does not exist.  The handle suffix, and the collection resource ID are incremented with each attempt, so something is getting created and destroyed...

Without the -a option, the command successfully creates the top level imported community.  So does the skipIfParentMissing option, but the recursion seems not to be working.

https://jira.duraspace.org/browse/DS-2404 seems to be related, but this issue seems to be about mapped items.

What am I doing wrong??

Thanks for any advice!
Bill

Bill T

unread,
Dec 14, 2016, 3:51:26 PM12/14/16
to DSpace Technical Support
For what it's worth, this command works in restore mode;  That's good enough for me now, but I'm still befuddled as to why it doesn't work in submit mode...

Bill T

unread,
Dec 15, 2016, 3:20:03 PM12/15/16
to DSpace Technical Support
Solved: The missing piece of the puzzle here is to add the ignoreHandle=false option. 

The actually manifests another problem -- child communities and collections are created with their existing handles, but child item's handles are ignored and new handles are minted for them.  If I can't figure out what I'm doing wrong here, I will submit a new post under a different topic...
Cheers!
Bill


On Tuesday, December 13, 2016 at 3:43:44 PM UTC-6, Bill T wrote:
Reply all
Reply to author
Forward
0 new messages