Helix, We¹re thinking of exporting all the data out, and completely rebuilding the server from ground up and then IMPORT all that data and bitstreams. So would it be possible to import the data back in with their current handles. We have targeted 10 possible conflicts and we¹re willing to take that chance.
Our testing of upgrading our database and other components have not been successful for version 1.6 and we believe that just reloading into a new version is simple and quicker‹and less frustrating. ‹Jeff Jeffrey Trimble, MLS William F. Maag Library Youngstown State University 330.941.2483 (Office) [email protected] http://www.maag.ysu.edu http://digital.maag.ysu.edu On 11/14/16, 4:11 AM, "[email protected] on behalf of helix84" <[email protected] on behalf of [email protected]> wrote: >Hi Jeff, > >I'm not sure I fully understood your problem. I understand you want to >keep handles, which you definitely should. I don't understand why >there would be any handle conflicts on an upgrade. > >To answer your question - no, changing provenance will not pose a >problem for DSpace as this field is not machine-readable. > >Anyway, why do you need to change provenance? By default, it's only >visible to administrators, so you'd be removing information that could >be potentially helpful to you in the future. > > >Regards, >~~helix84 > >Compulsory reading: DSpace Mailing List Etiquette >https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > > >On Sat, Nov 12, 2016 at 9:19 PM, Jeffrey A Trimble <[email protected]> >wrote: >> We¹ve run into several difficulties upgrading from 1.6 to 5.x in test. >>This >> makes us very weary about attempting in production. >> >> I¹m wondering if it is possible to Export the collections, keeping the >> handles, but removing the provenance data (change the m flag logic in >> export) and reload keeping the handles intact. >> >> We¹ve identified only 10 handle conflicts where item handle and >>collection >> handle conflict. We¹re willing to risk that issue easily. What we are >>not >> wanting to do is risk a reload of some 15,000 items and have the handle >>IDs >> change. >> >> Any comments as to why not to do this, or a limitation with version 5.x? >> >> Thanks in advance, >> >> Jeff >> >> Jeffrey Trimble, MLS >> William F. Maag Library >> Youngstown State University >> 330.941.2483 (Office) >> [email protected] >> http://www.maag.ysu.edu >> http://digital.maag.ysu.edu >> >> -- >> You received this message because you are subscribed to the Google >>Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send >>an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. > >-- >You received this message because you are subscribed to the Google Groups >"DSpace Technical Support" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to [email protected]. >To post to this group, send email to [email protected]. >Visit this group at https://groups.google.com/group/dspace-tech. >For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
