Hi again, On 01/11/13 11:41, Andrea Schweer wrote: > I just used this sequence to add a file to an existing item using > export/import (DSpace 1.8.2): > [dspace]/bin/dspace export -i [prefix]/3998 -t ITEM -d /data/tmp -n 0 > echo handles-with-fulltext.xml > /data/tmp/0/contents > cd /data/tmp && [dspace]/bin/dspace itemupdate -A --source . --verbose > -e [email protected] > > There is something odd going on with interpolating the "source" > argument it seems. /data/tmp is the parent of the "0" directory > created by the export. Note I had to cd to that directory and use "." > as the source. Using /data/tmp or /data/tmp/ as the source argument, I > get "ERROR creating Undo Archive directory".
I had a look at the code and the undo information is created one step higher up in the directory hierarchy than I expected; in this case the undo information was going to go into /data but the dspace user doesn't have write permission there. When I use /data/tmp/addfile as the export destination (ie the exported item ends up in /data/tmp/addfile/0) and make sure that the dspace user has write permission in /data/tmp, I can use /data/tmp/addfile as the --source flag just fine. Anton, I assume you were just using the wrong spot in the filesystem hierarchy. cheers, Andrea -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
