[ 
http://jira.dspace.org/jira/browse/DS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10923#action_10923
 ] 

Stuart Lewis commented on DS-287:
---------------------------------

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


> Allow item exporter -m (migrate) option to be configurable
> ----------------------------------------------------------
>
>                 Key: DS-287
>                 URL: http://jira.dspace.org/jira/browse/DS-287
>             Project: DSpace 1.x
>          Issue Type: New Feature
>          Components: DSpace API
>    Affects Versions: 1.5.2
>            Reporter: Stuart Lewis
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> Allow the -m (migrate) option in the item exporter to be configurable as to 
> which metadata elements it will ignore.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
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
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to