No problem, thank you for testing. Can you please leave a comment at the mentioned pull-request? In that case we might be just in time for the DSpace 6.1 release.
Best regards, Tom [image: logo] Tom Desair 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 Gaston Geenslaan 14, Leuven 3001, Belgium www.atmire.com <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> 2017-07-03 13:03 GMT+02:00 euler <[email protected]>: > Hi Tom, > > Please ignore my previous message. I did not apply all the commits from > your pull request, hence I have the issue of two forward slashes in the > handle. I just noticed that you have 2 commits there. Your pull request in > the update-handle-prefix script fixed the issue that I'm having. > > Thank you so much and best regards, > euler > > > On Monday, July 3, 2017 at 11:05:15 AM UTC+8, euler wrote: >> >> Hi Tom, >> >> Unfortunately when I applied you pull request, it adds an extra slash eg >> [old-prefix]/123 becomes [new-prefix]//123 so in effect when you go to the >> items directly via browser's address bar, the item cannot be found. Browse >> by is also not working. >> >> Thanks and best regards, >> euler >> >> On Friday, June 30, 2017 at 11:17:18 PM UTC+8, Tom Desair (Atmire) wrote: >>> >>> I've created pull-request https://github.com/DSpace/DSpace/pull/1790 to >>> fix this for DSpace 6. >>> >>> You can please test the corrected update-handle-prefix script from that >>> pull-request and verify that it corrects the behaviour? >>> >>> Thanks and best regards, >>> >>> Tom >>> >>> [image: logo] Tom Desair >>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 >>> Gaston Geenslaan 14, Leuven 3001, Belgium >>> www.atmire.com >>> <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> >>> >>> 2017-06-30 8:08 GMT+02:00 euler <[email protected]>: >>> >>>> Hi Tom, >>>> >>>> Even if I batch edit the metadata fields to start with >>>> http://hdl.handle.net/, and re-run the script, although it will update >>>> the prefix, the problem is that the generated new URL will not match the >>>> dc.identifier.uri value. It is always off by 1. I also tried merging my >>>> local branch to the latest upstream 6_x branch (Since the pull request you >>>> mentioned was already merged). Same results. Any advice on how to fix this? >>>> >>>> Thanks in advance, >>>> euler >>>> >>>> On Wednesday, June 28, 2017 at 9:52:14 PM UTC+8, Tom Desair (Atmire) >>>> wrote: >>>>> >>>>> I've corrected this in the following pull-request >>>>> https://github.com/DSpace/DSpace/pull/1727 >>>>> >>>>> In DSpace 6.0 the update-handle-prefix script only updates metadata >>>>> fields if they start with "http://hdl.handle.net/";. That is why your >>>>> metadata values are not updated. >>>>> >>>>> You can port the changes to the UpdateHandlePrefix.java file ( >>>>> https://github.com/DSpace/DSpace/pull/1727/files#diff- >>>>> 5c44dc1a4d6071cdcfdf65b29e108d6d) and then re-run the script. >>>>> >>>>> Best regards, >>>>> Tom >>>>> >>>>> [image: logo] Tom Desair >>>>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 >>>>> Gaston Geenslaan 14, Leuven 3001, Belgium >>>>> www.atmire.com >>>>> <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> >>>>> >>>>> 2017-06-28 15:11 GMT+02:00 Claudia Jürgen <[email protected]>: >>>>> >>>>>> Hello euler, >>>>>> >>>>>> did you backup your db prior to updating the handle sequence? >>>>>> Actually the handle_id is taken to build the new handle rather than >>>>>> the >>>>>> existing handle. >>>>>> You may take a look at the handle table in the backup and the new one. >>>>>> >>>>>> I'll file a ticket in JIRA this may have sideeffects on AIP and other >>>>>> things. >>>>>> >>>>>> Hope this helps >>>>>> >>>>>> Claudia Jürgen >>>>>> >>>>>> Am 28.06.2017 um 08:37 schrieb euler: >>>>>> >>>>>>> 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+DSpac >>>>>>> e#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/b >>>>>>> 4-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> >>>>>>> >>>>>>> >>>>>> -- >>>>>> Claudia Juergen >>>>>> Eldorado >>>>>> >>>>>> Technische Universität Dortmund >>>>>> Universitätsbibliothek >>>>>> Vogelpothsweg 76 >>>>>> 44227 Dortmund >>>>>> >>>>>> Tel.: +49 231-755 40 43 >>>>>> Fax: +49 231-755 40 32 >>>>>> [email protected] >>>>>> www.ub.tu-dortmund.de >>>>>> >>>>>> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. >>>>>> Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der >>>>>> für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den >>>>>> Absender und vernichten Sie diese Mail. Vielen Dank. >>>>>> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen >>>>>> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher >>>>>> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung >>>>>> eines >>>>>> solchen Schriftstücks per Telefax erfolgen. >>>>>> >>>>>> Important note: The information included in this e-mail is >>>>>> confidential. It is solely intended for the recipient. If you are not the >>>>>> intended recipient of this e-mail please contact the sender and delete >>>>>> this >>>>>> message. Thank you. Without prejudice of e-mail correspondence, our >>>>>> statements are only legally binding when they are made in the >>>>>> conventional >>>>>> written form (with personal signature) or when such documents are sent by >>>>>> fax. >>>>>> >>>>>> >>>>>> -- >>>>>> 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. >>>>>> >>>>> >>>>> -- >>>> 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. >>>> >>> >>> -- > 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. > -- 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.
