Hello euler,
5 is the site see:
https://github.com/DSpace/DSpace/blob/dspace-6.0/dspace-api/src/main/java/org/dspace/core/Constants.java
It tested the update handle prefix and this line was the only one
changed see
https://jira.duraspace.org/browse/DS-3632
In your old db did any other lines exist where the handle_id did not
match the number in handle?
Claudia
Am 29.06.2017 um 08:43 schrieb euler:
Hi Claudia,
From your suggestion to compare the handle table from the backup to the new
one, I found out that the original handle table contains 123456789/0 handle
entry with a value of a 5 in the resource_type_id. When I run the update
handle script, this handle becomes 20.500.12066/1. I'm pretty sure this is
the same row because the uuid is still the same. And so, all the updated
handles was incremented by 1 from the original handles. I wonder why the
handle table has an entry of [handle]/0. Is this expected? With regards to
my issue of the handles that are off by 1 from the original handle, how can
I fix it? I suppose this should be done in the database level. Please
advise for the appropriate sql query.
Thanks in advance,
euler
On Wednesday, June 28, 2017 at 9:11:03 PM UTC+8, Claudia Jürgen wrote:
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+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>
--
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] <javascript:>
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.
--
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.
