DOI functionality

[Jose Blanco]

I wonder if someone that has the DOI functionality in 6.3 setup could help me better understand it before I contact DataCite.

I kind of set it up in my test environment, but without a valid username and password, so I can see from the log file that after the metadata is entered the code tries to create a DOI ( this is just my assumption ).  I'm wondering what happens at this point.  Is the user presented with a DOI before he/she uploads files.  Ideally we would like the DOI to be presented to the user, so that he/she can then add it to the file to be uploaded before the deposit completes.  Is this what happens? Or is the DOI created after the deposit completes.  Also, is the value of the DOI stored in dc.identifier.doi?

Thank you! 

-Jose

[Mark H. Wood]

Much of this is described in:

https://wiki.lyrasis.org/display/DSDOC6x/DOI+Digital+Object+Identifier

In particular, the process by which DOIs are generated and registered
is described in:

https://wiki.lyrasis.org/display/DSDOC6x/DOI+Digital+Object+Identifier#DOIDigitalObjectIdentifier-CommandLineInterface

The DOI generated by the DataCite provider is stored in
'dc.identifier.uri'. You can find the code for this in
'dspace-api/src/main/java/org/dspace/identifier/DOIIdentifierProvider.java'.

Please ignore the section on the EzID provider, which is obsolete.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

[Jose Blanco]

Thanks, Mark. I had read this, but was still a bit confused.  I think now after reading it over, I realize that the DOI creation/management is done by the cron jobs and not during the deposit process.  

Thank you!

-Jose

--
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 dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/20201009145135.GA13687%40IUPUI.Edu.

[Jose Blanco]

I have configured our test area to use DataCite to mint doi using the dspace documentation, and everything is working fine.  I see that after the cronjobs run, a doi is created and I can see it on the item view page. But we have a use case for which this approach does not quite work.  Ideally we would like the doi to be minted during the deposit of the item, and before the user uploads the files.  This way the user can add the doi to the pdf file before uploading it.  I know we could probably use a header page to display the doi once it is generated, but ideally the user wishes to have the doi value so that he/she can add it directly to his/her file before uploading it.  Any suggestions about how to accomplish this with the out of box dspace 6.3?

Thank you!

-Jose

[Michael Plate]

Hi Jose,

Am 03.11.20 um 16:47 schrieb Jose Blanco:

> I have configured our test area to use DataCite to mint doi using the
> dspace documentation, and everything is working fine.

[…]

> Any suggestions about how
> to accomplish this with the out of box dspace 6.3?

No, not out of the box (we use 5.10)
We had the same requirements: get a PI before submit.

Solution is fetching the DOI by a web service and pre-filling the field
in the first step, so the submitter can note it down an put it inside
their file.
Save the submission, after that there is a DOI, so don't fetch an new
one on reopening (we have one user where this not works, gets a new one
every time, needs further investigation).

Disadvantage: you need your own scripts to register with DataCite…

I can give you the snippet for XMLUI, if you like.

Michael

[Jose Blanco]

Michael, If you can give me what you have done that would be very helpful.

Thank you!

-Jose

--
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 dspace-tech...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/10b8e751-2c6e-9be7-6f34-0f006f4a4e5f%40bibliothek.uni-kassel.de.