Tim, "helix84" and Wally, Thanks very much for the responses! Have forwarded all the replies to the hosting company and will work with the people there to resolve the problem.
Regarding the ways to get metadata and bitstreams in the collection level from DSpace, I have a quick question: If we need to do quite some editing for the exported metadata (e.g. adding new fields, splitting information in one field to several fields, changing field names and values etc.), how can this step be integrated to the workflow by either using AIP backup (in METS-based AIP format) or harvesting metadata in an arbitrary format? Need to read the resources you guys sent. Thanks a lot! Sophie -----Original Message----- From: Tim Donohue [mailto:tdono...@duraspace.org] Sent: Tuesday, February 05, 2013 9:47 AM To: Sai Deng Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] DSpace collection export maximum size Hi Sophie, You should be able to disable that maximum size check by either commenting out that "org.dspace.app.itemexport.max.size" setting in your dspace.cfg or by setting it to zero (which will also disable the check): org.dspace.app.itemexport.max.size = 0 After that, it should just be a matter of assuring you have the necessary space on your server to store the export files. Your process itself sounds reasonable (assuming you really want to get everything into an Excel spreadsheet in the end). The other bulk export tool that DSpace (versions 1.7.x and above) offers is the "AIP Backup & Restore tools". This tool can perform an export of all DSpace content (Communities, Collections and Items) to a set of METS-based Zip files (called AIPs). https://wiki.duraspace.org/display/DSDOC18/AIP+Backup+and+Restore - Tim On 2/5/2013 8:07 AM, Sai Deng wrote: > Dear list, > > We're trying to export DSpace collections from the front end (Admin > Tools- Export Collection, or Export (migrate) Collection), it reports > errors for certain collections: > > *Error with export* > > The overall size of this export is too large. Please contact your > administrator for more information. > > The hosting company said that it's because DSPACE was running out of space > and did adjustments in the server side (I assume), it still reports the same > error. We then searched DSpace-Tech and changed the itemexport maximum size > config to ""org.dspace.app.itemexport.max.size = 1024", it still reports the > same error for certain collections. > > > > What else can be done to resolve this issue? > > > > Our goal actually is to export collections in DSpace to CONTENTdm and > eventually to a state-wide sharing system. Currently, we get metadata from > the front end (Admin Tools- Export metadata) in csv file for a whole > collection, and we acquire the actual bitstreams from the collection export. > It involves some manual work to add the bitstream names to the csv file (in > spreadsheet). There are probably better ways. If you have any insights, > please reply! > > Thanks very much! > > > > Sophie > > Metadata Librarian > > UCF Library > > > > ---------------------------------------------------------------------- > -------- > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 and get > the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > > > > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
