Re: [Dspace-tech] retrospectively assigning DOIs to live items
Hi Andrea and Pascal,
it's on my todo-list too to add it to the doi-organiser, but low. Done
the fixes for the provider though and going to make a patch for these,
as soon as I got the doi stuff locally running.
At the moment the crosswalk itself needs a bit more work.
Run it with ~16.000 documents on the test.datacite.org site and it
produced a lot of errors, especially with regards to maxOccurences
(never checked in our existing crosswalk), required attributes etc.
Nearly fixed these too and going to test it again.
I only wonder whether we should make corrections to the 2.2 kernel or
rather 3.1 which is the preferred version from DataCite:
https://schema.datacite.org/meta/kernel-3.1/doc/DataCite-MetadataKernel_v3.1.pdf
or both 2.2 for existing DSpace versions and 3.1 for future release?
Btw DataCite flags (for oai harvesters) data with the flag reference
quality. Does anyone know the quality creteria for this flag, could not
find it in their documentation?
Sunny Greetings
Claudia
Am 04.08.2015 um 01:47 schrieb Andrea Schweer:
Hi Pascal,
On 03/08/15 21:04, Becker, Pascal-Nicolas wrote:
On 03/08/15 1:48 AM, Andrea Schweer wrote:
On 03/08/15 11:16, Claudia Jürgen wrote:
yes this is right. If you enable the identifier service this will only
cover new items.
Assuming you are using the DataCite Connector, the easiest way would
be to manipulate the database (usual warnings about that) to give the
old items the status of newly items in archive:
INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'),
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2,
item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
resource_id from doi where resource_type_id=2);
Then the cron job for the usual doi-organiser commands will pick up
the job.
Perfect, thanks a lot for that!
It should be easy to add a command in the doi-organiser that adds
those entries into the database. I just didn't had the use case and
the time. ;-)
All good :) It just wasn't obvious to me from the documentation. Perhaps
I'll have the time to change the docs / add this functionality to
doi-organiser, but no promises -- I have the use case but not
necessarily the time...
cheers,
Andrea
--
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
claudia.juer...@ub.tu-dortmund.de
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.
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] retrospectively assigning DOIs to live items
Hi Pascal,
On 03/08/15 21:04, Becker, Pascal-Nicolas wrote:
On 03/08/15 1:48 AM, Andrea Schweer wrote:
On 03/08/15 11:16, Claudia Jürgen wrote:
yes this is right. If you enable the identifier service this will only
cover new items.
Assuming you are using the DataCite Connector, the easiest way would
be to manipulate the database (usual warnings about that) to give the
old items the status of newly items in archive:
INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'),
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2,
item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
resource_id from doi where resource_type_id=2);
Then the cron job for the usual doi-organiser commands will pick up the job.
Perfect, thanks a lot for that!
It should be easy to add a command in the doi-organiser that adds those
entries into the database. I just didn't had the use case and the time. ;-)
All good :) It just wasn't obvious to me from the documentation. Perhaps
I'll have the time to change the docs / add this functionality to
doi-organiser, but no promises -- I have the use case but not
necessarily the time...
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] retrospectively assigning DOIs to live items
Hi Claudia, Hi Andrea,
On 03/08/15 1:48 AM, Andrea Schweer wrote:
On 03/08/15 11:16, Claudia Jürgen wrote:
yes this is right. If you enable the identifier service this will only
cover new items.
Assuming you are using the DataCite Connector, the easiest way would
be to manipulate the database (usual warnings about that) to give the
old items the status of newly items in archive:
INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'),
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2,
item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
resource_id from doi where resource_type_id=2);
Then the cron job for the usual doi-organiser commands will pick up the
job.
Perfect, thanks a lot for that!
It should be easy to add a command in the doi-organiser that adds those entries
into the database. I just didn't had the use case and the time. ;-)
I've just been investigating the use of doi's for us. There are a couple of
issues with it, especially the datacite connector crosswalk and data
provider,
see the latest JIRA issues.
At the moment with datacite the update of metadata does not work
among other things.
Thanks for reporting those issues! It worked fine once and is still working
here (highly patched DSpace 4). I hope I find some time to look into those, but
no promises...
Regards,
Pascal
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] retrospectively assigning DOIs to live items
Hi all, I'm looking into switching on DOIs for an existing DSpace repository with ~1,000 live items. We'd like to retrospectively generate DOIs for the live items. How do I do that? The documentation about the doi-organiser tool [1] says Currently you cannot generate new DOIs with this tool. You can only send information about changes in your local DSpace database to the registration agency. Does this mean I'd have to figure out how to change the state of the already live items to whatever the starting point of doi-organiser is (presumably to be reserved)? cheers, Andrea [1] https://wiki.duraspace.org/display/DSDOC5x/DOI+Digital+Object+Identifier#DOIDigitalObjectIdentifier-CommandLineInterface -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] retrospectively assigning DOIs to live items
Hello Andrea,
yes this is right. If you enable the identifier service this will only
cover new items.
Assuming you are using the DataCite Connector, the easiest way would be
to manipulate the database (usual warnings about that) to give the old
items the status of newly items in archive:
INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'),
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id, 7
FROM item
WHERE in_archive=true and item_id not in (select resource_id from doi where
resource_type_id=2);
Then the cron job for the usual doi-organiser commands will pick up the job.
I've just been investigating the use of doi's for us. There are a couple of
issues with it, especially the datacite connector crosswalk and data provider,
see the latest JIRA issues.
At the moment with datacite the update of metadata does not work among other
things.
Hope this helps
Claudia
Am 02.08.2015 um 23:27 schrieb Andrea Schweer:
Hi all,
I'm looking into switching on DOIs for an existing DSpace repository
with ~1,000 live items. We'd like to retrospectively generate DOIs for
the live items. How do I do that? The documentation about the
doi-organiser tool [1] says Currently you cannot generate new DOIs with
this tool. You can only send information about changes in your local
DSpace database to the registration agency.
Does this mean I'd have to figure out how to change the state of the
already live items to whatever the starting point of doi-organiser is
(presumably to be reserved)?
cheers,
Andrea
[1]
https://wiki.duraspace.org/display/DSDOC5x/DOI+Digital+Object+Identifier#DOIDigitalObjectIdentifier-CommandLineInterface
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] retrospectively assigning DOIs to live items
Hi Claudia,
On 03/08/15 11:16, Claudia Jürgen wrote:
yes this is right. If you enable the identifier service this will only
cover new items.
Assuming you are using the DataCite Connector, the easiest way would be
to manipulate the database (usual warnings about that) to give the old
items the status of newly items in archive:
INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'),
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id,
7 FROM item
WHERE in_archive=true and item_id not in (select resource_id from doi where
resource_type_id=2);
Then the cron job for the usual doi-organiser commands will pick up the job.
Perfect, thanks a lot for that!
I've just been investigating the use of doi's for us. There are a couple of
issues with it, especially the datacite connector crosswalk and data
provider, see the latest JIRA issues.
At the moment with datacite the update of metadata does not work among other
things.
Good to know; I had seen some DOI-related Jira issues come through but
I'll make sure to review them in more detail. Yes, we'll be using
DataCite; luckily with this particular repository, we're not really
expecting metadata changes once the submission is completed.
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
