Dear All, The repository I'm working on is running with the latest dspace-6_x branch. Based on this link: Updating Existing Handle Prefixes <https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-UpdatingExistingHandlePrefixes>, I run the following command [dspace]/bin/dspace update-handle-prefix 123456789 20.500.12066 after we received the handle prefix from CNRI and updating the config.dct file. Below is the output of the command:
Getting information about handles from database... In your repository will be updated 391 handles to new prefix 20.500.12066 from original 123456789! Servlet container (e.g. Apache Tomcat, Jetty, Caucho Resin) must be running. If it is necessary, please make a backup of the database. Are you ready to continue? [y/n]: y Updating handle table... 391 items updated Updating metadatavalues table... 2 metadata values updated Handles successfully updated in database. Re-creating browse and search indexes... Browse and search indexes are ready now. All done successfully. Please check the DSpace logs! Now, below is a screenshot of an item *before* I ran the update handle command. <https://lh3.googleusercontent.com/-OlfqlTpuXno/WVNJdV_8kuI/AAAAAAAABfA/RSuaHmeHQ28UpXXqt_ug3ru2zjH61WO4QCLcBGAs/s1600/b4-update-prefix.PNG> Below is the same item *after* the update prefix command: <https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/AAAAAAAABfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>Notice that the updated handle is now 20.500.12066/391 which is clearly wrong because it should be 20.500.12066/390 since the original URI was 123456789/390. The handle 20.500.12066/390 is now assigned to the owning collection of the item. Is this a bug? I hope someone from the list can reproduce this. Please help on how to resolve this issue. This could really be a problem if you have thousands of records from your demo system that you would like to migrate to a production server. <https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/AAAAAAAABfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG>Thanks in advance and hoping for your favorable response, <https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/AAAAAAAABfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG> <https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/AAAAAAAABfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG> euler <https://lh3.googleusercontent.com/-RJugrnf9jbA/WVNK8SRr8kI/AAAAAAAABfQ/UYa2gbQznR0Fgtth01Tk0X5X9FNpGeA1QCLcBGAs/s1600/after-update-prefix.PNG> -- 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.
