Hi Massimiliano,
you should configure your E-Mail settings. DSpace wanted to send a mail to the
address configured in alert.recipient, but this field was empty (you can find
more information here:
https://wiki.duraspace.org/display/DSDOC4x/Configuration+Reference#ConfigurationReference-DSpaceEmailSettings).
I see two problems with your DOI-Configuration in the log. The first is, that
the DOIs have strange names (doi:10.xxxx,10.5072/unisa-1), the second is that
the request seems to be send to the wrong address.
Which values have you set in [dspace]/config/dspace.cfg for
doi.identifier.prefix and doi.identifier.namespaceseparator? Please DO NOT send
the complete dspace.cfg as it may contain different username/password
combinations (e.g. for your database connection, for your doi-namespaces and so
on). By the way: did you set identifier.doi.user and identifier.doi.password
correctly (again: please DO NOT send the values you put in there).
In [dspace]/config/spring/api/identifier-service.xml you added a bean with the
id org.dspace.identifier.doi.DOIConnector (you added it by removing comments).
In the configuration of the bean you can set the host and paths the
DOIConnector should connect to. Can you please send me those lines? The
important part begins with <bean id="org.dspace.identifier.doi.DOIConnector"
and ends with </bean> (in my file these are the lines 56 to 64, but it may
differ).
Regards,
Pascal
From: Massimiliano Cilurzo [mailto:[email protected]]
Sent: Friday, January 24, 2014 9:58 AM
To: Becker, Pascal-Nicolas; [email protected]
Subject: R: [Dspace-tech] DOI DATACITE
Hi Pascal,
in this is the dspace.log after the command dspace/bin/dspace doi-organiser -u
...
....
org.dspace.content.MetadataSchema @ Loading schema cache for fast finds
2014-01-24 09:53:40,896 WARN org.dspace.identifier.doi.DataCiteConnector @
While reserving the DOI doi:10.xxxx,10.5072/unisa-1, we got a http status code
404 and the message "<?xml version="1.0" encoding="UTF-8"?>
<html><head><meta content="text/html; charset=UTF-8"
http-equiv="Content-Type"/><meta content="IE=8"
http-equiv="X-UA-Compatible"/><link
href="/resources/dijit/themes/tundra/tundra.css;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"
type="text/css" rel="stylesheet"></link><link
href="/resources/styles/standard.css;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"
media="screen" type="text/css" rel="stylesheet"></link><link
href="/resources/dojox/highlight/resources/pygments/emacs.css;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"
rel="stylesheet"></link><link
href="/resources/images/favicon.ico;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"
rel="SHORTCUT ICON"/><script type="text/javascript">var djConfig="en_US";
</script><script type="text/javascript"
src="/resources/dojo/dojo.js;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"></script><script
type="text/javascript"
src="/resources/spring/Spring.js;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"></script><script
type="text/javascript"
src="/resources/spring/Spring-Dojo.js;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"></script><script
type="text/javascript"
src="/resources/js/jquery-1.5.1.min.js;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"></script><script
type="text/javascript"
language="JavaScript">dojo.require("dojo.parser");</script><title>Welcome to
DataCite Metadata Store</title></head><body class="tundra spring"><div
id="wrapper"><div version="2.0" id="header"><div id="title"><a title="Home"
name="Home" href="/;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"><img
src="/resources/images/dc-logo.gif;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"/>
Metadata Store
</a></div><div id="topmenu">You are not logged in | <span><a
href="/login;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2">Login</a></span></div><br
style="clear:both"/></div><div id="main"><div version="2.0"><script
type="text/javascript">dojo.require('dijit.TitlePane');</script><div
id="_title_title_id"><script type="text/javascript">Spring.addDecoration(new
Spring.ElementDecoration({elementId : '_title_title_id', widgetType :
'dijit.TitlePane', widgetAttrs : {title: 'Requested Resource Not Found', open:
true}})); </script><h2>Requested Resource Not Found</h2><p>Sorry, we did not
find the resource you were looking for.</p></div></div><div version="2.0"
id="footer"><span><a
href="/;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2">Home</a></span> | <span
id="language">Language: <a title="Switch language to English"
href="?lang=en"><img alt="Switch language to English"
src="/resources/images/flags/en.png;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"
class="flag"/></a> <a title="Switch language to Deutsch" href="?lang=de"><img
alt="Switch language to Deutsch"
src="/resources/images/flags/de.png;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"
class="flag"/></a> <a title="Switch language to French" href="?lang=fr"><img
alt="Switch language to French"
src="/resources/images/flags/fr.png;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2"
class="flag"/></a> </span> | <span><a
href="/login;jsessionid=8EC5E96E127CC2CD35C2A70011CCE3B2">Login</a></span></div></div></div></body></html>".
2014-01-24 09:53:40,920 WARN org.dspace.identifier.doi.DOIOrganiser @ Unable
to send email alert
javax.mail.internet.AddressException: Illegal address in string ``''
at javax.mail.internet.InternetAddress.<init>(InternetAddress.java:94)
at org.dspace.core.Email.send(Email.java:261)
at
org.dspace.identifier.doi.DOIOrganiser.sendAlertMail(DOIOrganiser.java:914)
at org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:689)
at org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:265)
at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:225)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)
2014-01-24 09:53:40,921 ERROR org.dspace.identifier.doi.DOIOrganiser @ It
wasn't possible to update this identifier: doi:10.xxxx,10.5072/unisa-1
Exceptions code: BAD_ANSWER
org.dspace.identifier.doi.DOIIdentifierException: Unable to parse an answer
from DataCite API. Please have a look into DSpace logs.
at
org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:564)
at
org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector.java:681)
at
org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifierProvider.java:412)
at org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:669)
at org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:265)
at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:225)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)
2014-01-24 09:53:42,294 WARN org.dspace.identifier.doi.DataCiteConnector @
While reserving the DOI doi:10.14273,10.5072/unisa-2, we got a http status code
404 and the message "<?xml version="1.0" encoding="UTF-8"?>
Thanks
Best regards,
Massimiliano
Da: Becker, Pascal-Nicolas [mailto:[email protected]]
Inviato: giovedì 23 gennaio 2014 18:10
A: Massimiliano Cilurzo;
[email protected]<mailto:[email protected]>
Oggetto: RE: [Dspace-tech] DOI DATACITE
Hi Massimiliano,
you're on the right way, but there is still some error. What does the
doi-organiser writes into [dpsace]/logs/dspace.logs?
Regards,
Pascal
From: Massimiliano Cilurzo [mailto:[email protected]]
Sent: Thursday, January 23, 2014 1:09 PM
To: Becker, Pascal-Nicolas;
[email protected]<mailto:[email protected]>
Subject: R: [Dspace-tech] DOI DATACITE
Hi Pascal,
Thanks for your help now I'm 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]<mailto:[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#DOIDigitalObjectIdentifier-%27cron%27jobforasynchronousreservation/registration
To test it, you can start these commands manually on the command line. For
regular use I would suggest a cronjob.
It's 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]<mailto:[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 can't 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]<mailto:[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#DOIDigitalObjectIdentifier-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]<mailto:[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
