Re: [Dspace-tech] Moving items between installations keeping handle
Dear helix, I've made some experiments in this period of time, and concluded that moving between two DSpace 1.7 (or 1.8) installations everything works fine in keeping the handle, but when I'm moving between two DSpace 1.6.3 or from one DS1.7 to a DS1.6 it does not work; in both cases the handles are not kept, even though I see a handle file in the exported directory and I supress the --migrate argument. Is there any known bug in DS1.6.2 importer related to not keeping the handle? Thank you and regards Andre 2012/8/27 helix84 heli...@centrum.sk On Mon, Aug 27, 2012 at 4:03 PM, André andre.ass...@usp.br wrote: when moving items between - for instance - a test and a production DSpace installation, one should export using the --migrate argument so that the (date.accessioned, date.available, date.issued, description.provenance, format.extent, format.mimetype and the identifier.uri) metadata will be removed to receive new data from the import. Hi André, the question is - do you actually care about the values of these metadata fields? If not, you can just take them with you to the other repository unchanged. You can use AIP to transfer the whole object along with the handle. You may want to take a look at the submission mode when restoring and using the -o ignoreHandle=false option: https://wiki.duraspace.org/display/DSDOC18/AIP+Backup+and+Restore#AIPBackupandRestore-Thedifferencebetween%22Submit%22and%22Restore%2FReplace%22modes The question then is what happens if you're copying the item over second time (i.e. if it already exists in the target repository from a previous import). Regards, ~~helix84 -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Moving items between installations keeping handle
Andre, Between the DSpace 1.6.2 and 1.7.0 releases, the ItemImporter underwent several improvements bug fixes. However, I'm unaware of any bugs relating to not keeping around the handle, though it's possible there may have been a bug that we unknowingly fixed in 1.7.0. If you'd like to see a list of these bug fixes to the import script, they are listed in the 1.7.0 section of the History page of the Documentation: https://wiki.duraspace.org/display/DSDOC18/History#History-ChangesinDSpace1.7.0 You'd specifically want to search/scan that area for the word import. I see four specific fixes that were applied in DSpace 1.7.0: https://jira.duraspace.org/browse/DS-662 https://jira.duraspace.org/browse/DS-736 https://jira.duraspace.org/browse/DS-629 https://jira.duraspace.org/browse/DS-743 I'm not sure if this is much help, but that's the all I'm able to determine has changed between 1.6.2 and 1.7.0. - Tim On 9/27/2012 1:35 PM, André wrote: Dear helix, I've made some experiments in this period of time, and concluded that moving between two DSpace 1.7 (or 1.8) installations everything works fine in keeping the handle, but when I'm moving between two DSpace 1.6.3 or from one DS1.7 to a DS1.6 it does not work; in both cases the handles are not kept, even though I see a handle file in the exported directory and I supress the --migrate argument. Is there any known bug in DS1.6.2 importer related to not keeping the handle? Thank you and regards Andre 2012/8/27 helix84 heli...@centrum.sk mailto:heli...@centrum.sk On Mon, Aug 27, 2012 at 4:03 PM, André andre.ass...@usp.br mailto:andre.ass...@usp.br wrote: when moving items between - for instance - a test and a production DSpace installation, one should export using the --migrate argument so that the (date.accessioned, date.available, date.issued, description.provenance, format.extent, format.mimetype and the identifier.uri) metadata will be removed to receive new data from the import. Hi André, the question is - do you actually care about the values of these metadata fields? If not, you can just take them with you to the other repository unchanged. You can use AIP to transfer the whole object along with the handle. You may want to take a look at the submission mode when restoring and using the -o ignoreHandle=false option: https://wiki.duraspace.org/display/DSDOC18/AIP+Backup+and+Restore#AIPBackupandRestore-Thedifferencebetween%22Submit%22and%22Restore%2FReplace%22modes The question then is what happens if you're copying the item over second time (i.e. if it already exists in the target repository from a previous import). Regards, ~~helix84 -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Moving items between installations keeping handle
On Mon, Aug 27, 2012 at 4:03 PM, André andre.ass...@usp.br wrote: when moving items between - for instance - a test and a production DSpace installation, one should export using the --migrate argument so that the (date.accessioned, date.available, date.issued, description.provenance, format.extent, format.mimetype and the identifier.uri) metadata will be removed to receive new data from the import. Hi André, the question is - do you actually care about the values of these metadata fields? If not, you can just take them with you to the other repository unchanged. You can use AIP to transfer the whole object along with the handle. You may want to take a look at the submission mode when restoring and using the -o ignoreHandle=false option: https://wiki.duraspace.org/display/DSDOC18/AIP+Backup+and+Restore#AIPBackupandRestore-Thedifferencebetween%22Submit%22and%22Restore%2FReplace%22modes The question then is what happens if you're copying the item over second time (i.e. if it already exists in the target repository from a previous import). Regards, ~~helix84 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
