On Mon, Aug 27, 2012 at 4:03 PM, André <[email protected]> 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 [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
