[dspace-tech] Re: DOI Error Message

Dear Richard, sorry for being unclear. My idea was, that your problem had something to do with the item you wanted to register/reserve or update at DataCite. But your logfile snippets do not fit into this idea, so I guess I was wrong with that... Anyway, what I was proposing was to look into

[dspace-tech] Re: DOI Error Message

Dear Oliver, I am not sure what you mean and I am not sure what you mean can you explain in greater detail what you mean and what I should change the handle with. I am totally lost at this point in this troubleshooting of DOI Regards, Richard On Monday, April 20, 2020 at 8:57:04 AM UTC+2,

[dspace-tech] Re: DOI Error Message

Hello Richard, I think I have seen this error in a context, where you try to send invalid XML to DataCite. This is specific to the item you want to register/reserve/update. You can see the XML output, which is sent to DataCite with this command: ./bin/dspace dsrun

[dspace-tech] Re: DOI Error Message

Hello Paul, Thank you for providing the link, unfortunately, I am unable to figure out how to solve this error and more importantly where do I solvethe problem. Your help is most needed in solving this matter. thank you Richard Dennis On Saturday, April 11, 2020 at 11:15:37 PM UTC+2, Richard

[dspace-tech] Re: DOI import error when DOI contains parentheses. Publisher, the American Society of Civil Engineer

Recently I was doing work with APIs and I ran across the documents for the Crossref REST API at https://github.com/CrossRef/rest-api-doc. This includes the following warning: "You should always url-encode DOIs and parameter values when using the API. DOIs are notorious for including characters

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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",

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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,

Re: [dspace-tech] Re: DOI DATACITE schema 4.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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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, {

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI DATACITE schema 4.1

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

[dspace-tech] Re: DOI DATACITE schema 4.1

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

Re: [dspace-tech] Re: DOI and XMLUI

Dear Monika, The dspace.baseurl is aaxxx.xy/xmlui So I don't know where the system takes the JSPUI layout. Thanks Best regards Massimiliano Il giorno venerdì 23 novembre 2018 16:48:59 UTC+1, momeven ha scritto: > > > My best guess is that the DOI service uses the dspace.baseUr setting from

Re: [dspace-tech] Re: DOI and XMLUI

My best guess is that the DOI service uses the dspace.baseUr setting from your dspace.cfg file I would also recommend for a production system to configure your web server to proxy from 8080 to port 80 Monika --— Monika Mevenkamp OIT - Princeton University Phone: 609 258 4161 Skype:

[dspace-tech] Re: DOI and XMLUI

No one couold give me an advice for this? Thanks Best regards Massimiliano Il giorno giovedì 15 novembre 2018 10:32:06 UTC+1, Massimiliano CILURZO ha scritto: > > Dear all, > We are using DSPACE 5 and we have implemented the DOI configuration. > But now if you click on the DOI URL you are

Re: [dspace-tech] Re: DOI via Proxy

As an addition to Claudia's database command. We have a DSpace 6.3 instance and so the command is a little bit different: INSERT into doi (doi_id, doi, resource_type_id, resource_id, status, dspace_object) SELECT nextval('doi_seq'),

Re: [dspace-tech] Re: DOI via Proxy

Hello Claudia, thank you very much for your detailed description. I didn't realise that only new items will be listed. Kind regards, Paul Münch Am 22.10.18 um 13:35 schrieb Claudia Jürgen: > Hello Paul, > > once you have configured and your DOI ( these notes are for4.x, 5.x) in >

Re: [dspace-tech] Re: DOI via Proxy

Hello Paul, once you have configured and your DOI ( these notes are for4.x, 5.x) in [dspace]/dspace/config/dspace.cfg * identifier.doi.prefix * identifier.doi.namespaceseparator * event.consumer.doi.class * event.consumer.doi.filters * event.dispatcher.default.consumers

Re: [dspace-tech] Re: DOI via Proxy

Hello Michael, unfortunately not. Is there something additional I had to do beside the configuration? Kind regards, Paul Münch Am 22.10.18 um 13:10 schrieb Michael Plate: > Hi Paul, > > Am 22.10.18 um 12:55 schrieb Paul Münch: >> Hello, >> >> I figured out that the Proxy configuration is not

[dspace-tech] Re: DOI via Proxy

Hi Paul, Am 22.10.18 um 12:55 schrieb Paul Münch: > Hello, > > I figured out that the Proxy configuration is not the problem. Somehow > it is not possible to do anything with the 'doi-organiser'. Everytime I > tried to reserve, register or update all for test purposes, I got these > error

[dspace-tech] Re: DOI registration only for specific collections

On Tuesday, September 13, 2016 at 10:29:11 AM UTC-4, Anthony Petryk wrote: > > Is it possible to turn on DOI registration, but only for specific > collections? For pre-existing publications/content, do you worry about > multiple DOI assignment for the same work? > > Not out-of-the-box, but

[dspace-tech] Re: DOI registration only for specific collections

Kia ora, I'd like to bump this query - I'm very interested in doing this as well. nā mihi, Anton On Wednesday, September 14, 2016 at 2:29:11 AM UTC+12, Anthony Petryk wrote: > > Hello, > > Is it possible to turn on DOI registration, but only for specific > collections? For pre-existing

[dspace-tech] Re: DOI registration on existing Dspace items

On Friday, March 9, 2018 at 10:06:38 AM UTC-5, Mark H. Wood wrote: > > It creates a new curation task for finding objects with missing > identifiers and creating those missing identifiers. It is written for the > upcoming DSpace 7 but probably isn't too difficult to back-port. It needs >

Re: [dspace-tech] Re: DOI registration on existing Dspace items

Ok, thanks! I will take a look. Best regards, Paul On Fri, Mar 9, 2018 at 4:06 PM, Mark H. Wood wrote: > You may be interested in trying out the pull request > https://github.com/DSpace/DSpace/pull/1857 associated with > https://jira.duraspace.org/browse/DS-2670 > > It

[dspace-tech] Re: DOI registration on existing Dspace items

You may be interested in trying out the pull request https://github.com/DSpace/DSpace/pull/1857 associated with https://jira.duraspace.org/browse/DS-2670 It creates a new curation task for finding objects with missing identifiers and creating those missing identifiers. It is written for the

[dspace-tech] Re: DOI

Dear All, I noticed that if I run /dspace/bin/dspace doi-organiser -l There are no DOIs queued for reservation. There are no DOIs queued for registration. DOIs queued for update: doi:10.14273/unisa-679 (belongs to item with handle 105xxx/x) doi:10.14273/unisa-680 (belongs to