Hi Pascal,
Thanks for your help now Im understanding how it works.
When I execute [dspace]/bin/dspace doi-organiser u the answer is this:
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-1
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-2
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-3
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-4
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx/unisa-5
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx/unisa-6
Da: Becker, Pascal-Nicolas [mailto:[email protected]]
Inviato: giovedì 23 gennaio 2014 13:00
A: [email protected]
Cc: Massimiliano Cilurzo
Oggetto: RE: [Dspace-tech] DOI DATACITE
Hi Massimiliano,
as written in the DSpace Documentation DSpace uses an asynchronous approach
to register DOIs. Whenever DSpace wants to reserver/register a DOI, it just
writes in the DOI table what should be done. The doi-organiser does the real
work (by sending one or multiple requests to datacite, containing the
metadata and the information if a doi should be reserved, registered,
). So
to send your registration request to DataCite, you have to run the
doi-organiser as described here:
https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier#DOI
DigitalObjectIdentifier-%27cron%27jobforasynchronousreservation/registration
To test it, you can start these commands manually on the command line. For
regular use I would suggest a cronjob.
Its up to you to decide how often the doi-organiser should be triggered by
the cronjob. The decision you have to make is how much time is acceptable
for you between the moment DSpace adds a DOI to the metadata of an item and
the moment the DOI is functional (registered). I would make this decision
depending on the number of submissions you have per day. On smaller
repositories it should be acceptable to run the doi-organsier perhaps twice
a doi. But if you want to, you can run it more often, f.e. every 15 minutes
The reason we did it this way, is to ensure that DSpace is still working
even if DataCite should have some down time
Did this helps you? What happens if you run [dspace]/bin/dspace
doi-organiser u?
Regards,
Pascal
From: Massimiliano Cilurzo [mailto:[email protected]]
Sent: Thursday, January 23, 2014 8:46 AM
To: [email protected]; Becker, Pascal-Nicolas
Subject: R: [Dspace-tech] DOI DATACITE
Hi Pascal,
I have executed dspace doi-organiser in the wrong directory.
When I execute bin/dspace doi-organiser -l?
The system answer is:
There are no DOIs queued for reservation.
There are no DOIs queued for registration.
DOIs queued for update:
doi:10.xxxx,10.5072/unisa-1 (belongs to item with handle 123456789/479)
doi:10.xxxxx,10.5072/un-2 (belongs to item with handle 123456789/480)
doi:10.xxxxx,10.5072/unisa-3 (belongs to item with handle 123456789/481)
doi:10.xxxx,10.5072/unisa-4 (belongs to item with handle 123456789/482)
doi: 10.5072/unisa-5 (belongs to item with handle 123456789/485)
doi: 10.5072/unisa-6 (belongs to item with handle 123456789/486)
There are no DOIs queued for deletion.
When I go in the Datacite site, I cant see any of this item.
Thanks
Kind regards
Massimiliano
Da: Becker, Pascal-Nicolas [mailto:[email protected]]
Inviato: venerdì 17 gennaio 2014 16:56
A: [email protected]
Cc: Massimiliano Cilurzo
Oggetto: RE: [Dspace-tech] DOI DATACITE
Hi Massimiliano,
did you entered into a contract with a DOI registration agency? Did they
provide you a username, a password and a (test-)prefix? Are you sure, they
want you to use the DataCite API directly?
If you followed the instructions in the documentation, DSpace should mint
DOIs whenever new items gets published into the repository. With publish I
mean that the item is part of your repository, can be found using the normal
search, and is not waiting for the user to finish the submission or for an
administrator to accept it. The DOI is stored as metadata value of the item
in the field dc.identifier.uri. So If you take a look on the published item
you should find it there. As the documentation describes DSpace uses an
asynchronous mechanism to register DOIs. Using the command line interface
(https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier#DO
IDigitalObjectIdentifier-CommandLineInterface) you can list all DOIs waiting
for reservation and/or registration. So, do you already have published an
item after you configured DSpace to use DOIs? What happens if you executes
[dspace-install]/bin/dspace doi-organiser -l?
Regards,
Pascal
From: Massimiliano Cilurzo [mailto:[email protected]]
Sent: Friday, January 17, 2014 12:25 PM
To: [email protected]
Subject: [Dspace-tech] DOI DATACITE
Hi All,
We have installed in a test server DSPACE 4.0, we have configured it
for the use of DOI from DATACITE.
We followed the guide line at
https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier
But now I wonder how we can test if.
Could someone give an help?
Thanks
Best regards
Massimiliano Cilurzo
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
