Re: [Dspace-tech] Error with dspace_migrate
I'm actually not certain, but their handle information is still in the dublin_core.xml, thus requiring me to run dspace_migrate. Thank you for the reply, however. -- Shane Beers Digital Repository Services Librarian George Mason University sbe...@gmu.edu http://mars.gmu.edu 703-993-3742 On Apr 20, 2009, at 5:40 PM, Stuart Lewis wrote: > Hi Shane, > > This probably won't help you, but is the other repository running > 1.5.2? > > The item exporter was upgraded in 1.5.2 to include a new -m (or > --migrate) option to perform the same processing as part of the item > exporter (and in Java, so it works on all platforms) so that the > export > archive does not contain the repository specific item attributes. > > Cheers, > > > Stuart Lewis > Digital Services Programmer > Te Tumu Herenga The University of Auckland Library > Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand > Ph: 64 9 373-7599 x81928 > http://www.library.auckland.ac.nz/ > > > > -Original Message- > From: Shane Beers [mailto:sbe...@gmu.edu] > Sent: Tuesday, 21 April 2009 8:59 a.m. > To: Dspace Tech > Subject: [Dspace-tech] Error with dspace_migrate > > I am importing a large collection that was exported for us from > another DSpace repository. To remove their handle and other > institution-specific metadata, I am running the dspace_migrate > function on the exported data. However, it is proving INCREDIBLY > frustrating, because I routinely am getting: > > ERROR: filesize for /dspace/incoming-docs/exp-090414/401-500//439/ > dublin_core.xml is 0 > > randomly during the process. Anywhere from 2 to 200 will process just > fine, and then that error will take place. I will then have to delete > the temporary dublin_core.xml, rename the dublin_core.xml.orig file to > dublin_core.xml, move the successfully processed files somewhere else, > and cross my fingers that it will work the next time. > > For over 1000 items, this is INCREDIBLY tedious and just seems like it > shouldn't be happening. Any idea what's going on? > > Thanks! > Shane > > -- > Shane Beers > Digital Repository Services Librarian > George Mason University > sbe...@gmu.edu > http://mars.gmu.edu > 703-993-3742 > > > -- > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Error with dspace_migrate
Hi Shane, This probably won't help you, but is the other repository running 1.5.2? The item exporter was upgraded in 1.5.2 to include a new -m (or --migrate) option to perform the same processing as part of the item exporter (and in Java, so it works on all platforms) so that the export archive does not contain the repository specific item attributes. Cheers, Stuart Lewis Digital Services Programmer Te Tumu Herenga The University of Auckland Library Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand Ph: 64 9 373-7599 x81928 http://www.library.auckland.ac.nz/ -Original Message- From: Shane Beers [mailto:sbe...@gmu.edu] Sent: Tuesday, 21 April 2009 8:59 a.m. To: Dspace Tech Subject: [Dspace-tech] Error with dspace_migrate I am importing a large collection that was exported for us from another DSpace repository. To remove their handle and other institution-specific metadata, I am running the dspace_migrate function on the exported data. However, it is proving INCREDIBLY frustrating, because I routinely am getting: ERROR: filesize for /dspace/incoming-docs/exp-090414/401-500//439/ dublin_core.xml is 0 randomly during the process. Anywhere from 2 to 200 will process just fine, and then that error will take place. I will then have to delete the temporary dublin_core.xml, rename the dublin_core.xml.orig file to dublin_core.xml, move the successfully processed files somewhere else, and cross my fingers that it will work the next time. For over 1000 items, this is INCREDIBLY tedious and just seems like it shouldn't be happening. Any idea what's going on? Thanks! Shane -- Shane Beers Digital Repository Services Librarian George Mason University sbe...@gmu.edu http://mars.gmu.edu 703-993-3742 -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Error with dspace_migrate
I am importing a large collection that was exported for us from another DSpace repository. To remove their handle and other institution-specific metadata, I am running the dspace_migrate function on the exported data. However, it is proving INCREDIBLY frustrating, because I routinely am getting: ERROR: filesize for /dspace/incoming-docs/exp-090414/401-500//439/ dublin_core.xml is 0 randomly during the process. Anywhere from 2 to 200 will process just fine, and then that error will take place. I will then have to delete the temporary dublin_core.xml, rename the dublin_core.xml.orig file to dublin_core.xml, move the successfully processed files somewhere else, and cross my fingers that it will work the next time. For over 1000 items, this is INCREDIBLY tedious and just seems like it shouldn't be happening. Any idea what's going on? Thanks! Shane -- Shane Beers Digital Repository Services Librarian George Mason University sbe...@gmu.edu http://mars.gmu.edu 703-993-3742 -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
