I went through the difficult process of trying to get the dspace_migrate script to work yesterday in DSpace 1.5.1, when I finally found a discussion via Google about the problems others have had with the script and the changes that have been made to ItemExport.java in DSpace release 1.5.2, specifically the "Migrate" option. I ended up downloading the 1.5.2 version of ItemExport.java and it worked great. I just have one suggestion: whenever we migrate Items from one DSpace instance to another, we *always* want to retain the handles for those records because we don't want to have more than one handle for the same record. We do have unusual circumstances having to do with security/authorization with limited documents and so we have some DSpace instances that have handle servers running on them and some instances that don't. This may be a unique situation and this may not make sense to others, however my suggestion is that an option be added to ItemExport.java in a future release that would allow for a command line "option" to retain handles, but still get rid of metadata that will be duplicated on import into another instance. Thanks, Sue
Sue Walker-Thornton ConITS Contract NASA Langley Research Center Integrated Library Systems Application & Database Administrator 130 Research Drive Hampton, VA 23666 Office: (757) 224-4074 Fax: (757) 224-4001 Mobile: (757) 506-9903 Email: [email protected]<mailto:[email protected]>
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
