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 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:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)
2019-02-14 16:43:43,985 WARN org.dspace.identifier.doi.DataCiteConnector @
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,
{http://datacite.org/schema/kernel-3}creators,
{http://datacite.org/schema/kernel-3}titles,
{http://datacite.org/schema/kernel-3}publisher,
{http://datacite.org/schema/kernel-3}publicationyear,
{http://datacite.org/schema/kernel-3}subjects,
{http://datacite.org/schema/kernel-3}contributors,
{http://datacite.org/schema/kernel-3}dates,
{http://datacite.org/schema/kernel-3}language,
{http://datacite.org/schema/kernel-3}resourcetype ). at line 3, column 0".
2019-02-14 16:43:43,985 ERROR org.dspace.identifier.doi.DOIOrganiser @ It
wasn't possible to update this identifier: doi:10.14273/unisa-1194
Exceptions code: BAD_ANSWER
Could you help me to understand the reason?
Thanks
Best regards
Massimiliano
Il giorno martedì 12 febbraio 2019 19:23:47 UTC+1, Tim Donohue ha scritto:
>
> 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 *two* patches to DSpace 5.x. First,
> you'd have to apply the fixes to update to DataCite schema v3.1 :
> https://github.com/DSpace/DSpace/pull/1197 (This is the fix that was
> included as part of 6.0). Then you would need to apply this patch:
> https://github.com/DSpace/DSpace/pull/2321
>
> You also may want to simply see if upgrading to DSpace 6.3 would *solve*
> the issues you are having. In your original email, it was unclear if you
> absolutely *must* be running DataCite schema v4.1, or if possibly DataCite
> schema v3.1 would work. So, honestly, my recommendation would be to first
> start up a test server with DSpace 6.3 on it to see if compatibility with
> DataCite schema 3.1 fixes the issues you are seeing. If so, you may not
> even need to apply the patch to update to DataCite schema 4.1. I cannot
> give advice myself on whether upgrading to DSpace 6.3 will solve the issue
> or not -- that's likely something you'd need to either test out yourself,
> or talk to the DataCite team about.
>
> - Tim
>
>
>
>
>
> On Tue, Feb 12, 2019 at 12:12 PM Massimiliano CILURZO <[email protected]
> <javascript:>> wrote:
>
>> 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
>> Massimiliano
>>
>> Il giorno martedì 12 febbraio 2019 17:13:42 UTC+1, Tim Donohue ha scritto:
>>
>>> Massimiliano,
>>>
>>> Just a follow-up to Mark's previous note. DSpace 6.x is using DataCite
>>> Schema 3.1 (so if you are seeing Schema 2.2, I'm assuming you aren't using
>>> the latest DSpace), see this update which was released in DSpace 6.0:
>>> https://jira.duraspace.org/browse/DS-2924
>>>
>>> As Mark notes, we have a pending update to DataCite Schema 4.1, which
>>> likely won't be released until 6.4 (at the earliest). If you are already
>>> running DSpace 6.x, this patch should be relatively easy to apply
>>> immediately. If you are able to help test this patch, then we'd appreciate
>>> it if you could add notes to the patch (in GitHub), as that will allow us
>>> to more easily approve/merge the change in time for 6.4. Again, here's
>>> where this patch is: https://github.com/DSpace/DSpace/pull/2321
>>>
>>> If you have further questions, let us know on this list.
>>>
>>> Tim
>>>
>>> On Mon, Feb 11, 2019 at 8:00 AM Mark H. Wood <[email protected]> wrote:
>>>
>> On Monday, February 11, 2019 at 4:23:53 AM UTC-5, Massimiliano CILURZO
>>>> wrote:
>>>>>
>>>>> The DOI Datacite schema now is arrived to 4.1, we have on DSpace
>>>>> version 2.2 and it could have some problem with the new managemant
>>>>> software
>>>>> of DATACITE.
>>>>> With a schema version 2.2 it cuold be impossible to do an update via
>>>>> the "DOI DataCite Fabrica" system.
>>>>> So I would like to know if it is possible to update this schema to 4.1.
>>>>>
>>>>
>>>>
>>>> There is a patch to upgrade to 4.0:
>>>> https://github.com/DSpace/DSpace/pull/2321 which has not yet been
>>>> merged.
>>>>
>>>>
>>>> --
>>>> All messages to this mailing list should adhere to the DuraSpace Code
>>>> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
>>>> ---
>>>> 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.
>>>>
>>> --
>>> Tim Donohue
>>> Technical Lead for DSpace & DSpaceDirect
>>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>>
>> --
>> All messages to this mailing list should adhere to the DuraSpace Code of
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> ---
>> 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] <javascript:>.
>> To post to this group, send email to [email protected]
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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.
