Dear Claudia,
Thanks for yuor suggestions.
I'll on a sandbox server.
Best regards
Massimiliano
Il giorno mercoledì 20 febbraio 2019 15:24:35 UTC+1, Claudia Jürgen ha
scritto:
>
> Hi Massimiliano,
>
> I would always work with a instance first, for all kinds of changes.,
> unless very small
Hi Claudia,
Ok but the system is in production accoding to you is safe to re build
and deploy?
Thanks
Best regards
Massimiliano
Il giorno martedì 19 febbraio 2019 16:06:00 UTC+1, Claudia Jürgen ha
scritto:
>
> Hello Massimiliano,
>
> if you change something in the source code you got to
Hello Massimiliano,
if you change something in the source code you got to build and deploy
your application again.
Hope this helps
Claudia Jürgen
Am 19.02.2019 um 14:11 schrieb Massimiliano CILURZO:
Dear Cluadia,
I have changed to Element identifier = new Element("identifier",
Dear Claudia,
After changing DataCiteConnector.java I have done now a reboot of
tomacat.
And now seems that dspace mint doi's.
But this doi couldn't be reserved on DataCite because there is still the
error
2019-02-19 14:45:49,857 WARN org.dspace.identifier.doi.DataCiteConnector @
While
Dear Cluadia,
I have changed to Element identifier = new Element("identifier",
"http://datacite.org/schema/kernel-3;);
In DataCiteConnector.java.
According to you I have to restart the system, after this change?
Thanks
Regards
Massimiliano
Il giorno martedì 19 febbraio 2019 13:02:39 UTC+1,
Hello Massimiliano,
as Mark already pointed out there is the issue for 5.x for the schema
being hardcoded see:
https://jira.duraspace.org/browse/DS-4044
in
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/identifier/doi/DataCiteConnector.java#L1039
Hope this
Dear Claudia,
The dc.identifier.uri is present in every item.
And till 2 weeks ago the doi's were mint with the schema 2.2.
Now our server doesn't mint any DOI, even with the new schema 3.
If I do /dspace/bin/dspace doi-organiser -l after inserting a new item.
There isn't new doi.
Thanks
Hello Massimiliano,
you need not add dc.identifier.uri (not doi). This is done prior to actually
registering a doi with datacite, depending on the status:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L69
A newly
Dear Claudia,
In this item there is no DOI but in the item submission form the field
dc.identifier.doi is present.
And generally I leave this field blank, than after the submission and doi
url appear on the item page after using
/dspace/bin/dspace doi-organiser -u
Is this correct or I'm
Dear Claudia,
I have tried to test the crosswalk with a test item.
The result is this :
http://datacite.org/schema/kernel-3;
xmlns:dspace="http://www.dspace.org/xmlns/dspace/dim;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://datacite.org/schema/kernel-3
On Thursday, February 14, 2019 at 10:56:00 AM UTC-5, Massimiliano CILURZO
wrote:
>
> Dear Tim,
> I have tried the second option and updated to schema 3.1 first.
> But the answer after
>
> /dspace/bin/dspace doi-organiser -u
>
> is this in dspace.log
> ERROR
P. S.
best try the check first this one:
http://elea.unisa.it/xmlui/handle/10556/2854?show=full
this seems not to have dc.identifier.doi which is necessary for
registration or update
So try
[dspace]/bin/dspace dsrun
org.dspace.content.crosswalk.XSLTDisseminationCrosswalk DataCite
10556/2854
Hello Massimiliano,
we are running DSpace 5.x with DataCite 4.1 (heavily relying on our own
metadata and thus not yet backported to DSpace).
Prior to this we had DataCite 3.1 with no problems.
You can test your crosswalk by crosswalking an item with:
[dspace]/bin/dspace dsrun
Hi Massimiliano,
The main error message there seems to be this one:
While reserving the DOI doi:10.10xxx/un**-1194, we got a http status code
422 and the message "This element is not expected. expected is one of ( {
http://datacite.org/schema/kernel-3}identifier, {
Dear Tim,
I have tried the second option and updated to schema 3.1 first.
But the answer after
/dspace/bin/dspace doi-organiser -u
is this in dspace.log
ERROR org.dspace.identifier.doi.DOIOrganiser @ It wasn't possible to
update this identifier: doi:10.14273/unisa-937 Exceptions
Hello Massimiliano,
Since you are running DSpace 5.6, you'd have two options to get to DataCite
v4.1 compatibility:
- Either you should upgrade to DSpace 6.3 (the latest version of 6.x),
and then apply this patch https://github.com/DSpace/DSpace/pull/2321
- Or, you would need to apply
Dear Tim.
I'm running DSpace 5.6 I could install this patch on it?
I would like to try this patch, If you tell me that I could use it only on
DSpace 6.0 I'll try it first on a test server with DSpace 6.0.
If I can I'll try to help for this patch with some notes about it.
Thanks
Best regards
17 matches
Mail list logo
