EPrints Technical Mailing List Archive

Message: #05947

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] DataCite DOI plugins

Indeed, it looks like there is a function in https://github.com/eprintsug/DataCiteDoi/blob/master/cfg/cfg.d/z_datacitedoi.pl that causes the three warnings/errors.

I was getting the warning six times, because I actually had the cfg.d/datacite_core.pl file with the same function still in my cfg folder – so I had the errors twice.

 

Tomasz

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Tomasz Neugebauer
Sent: September-19-16 4:06 PM
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] DataCite DOI plugins

 

Hi Rory,

 

Thank you! 

 

How do I decipher which file contains the problem when I have an error message like this during repo reload?

 

Using a hash as a reference is deprecated at (eval 158) line 5, <DATA> line 749.

Using a hash as a reference is deprecated at (eval 158) line 9, <DATA> line 749.

Using a hash as a reference is deprecated at (eval 158) line 10, <DATA> line 749                  

Using a hash as a reference is deprecated at (eval 159) line 95, <DATA> line 749                  

Using a hash as a reference is deprecated at (eval 159) line 99, <DATA> line 749                  

Using a hash as a reference is deprecated at (eval 159) line 100, <DATA> line 749.

 

Could  the DataCite DOI plugin be the cause of these errors?   They go away when I disable that plugin.  

My version of the plugin is very close to, although probably not identical to the 1.0 release.

 

Tomasz

 

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Rory McNicholl
Sent: September-08-16 8:13 AM
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] DataCite DOI plugins

 

Hmm..

 

Had another shot. This time I've double checked that the commit I've tagged is not the latest as that somewhat defeats the point. I've cracked open the zip for this one and it looks okay:

 

https://github.com/eprintsug/DataCiteDoi/releases/tag/1.0

Sorry about that.

 

Cheers,

 

Rory

 

 

Rory McNicholl

Lead developer

Digital Archives & Research Technologies

University of London Computer Centre

Senate House

Malet Street

London

WC1E 7HU

 

t: +44 (0)20 7863 1344

 

The University of London is an exempt charity in England and Wales.

From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
Sent: 07 September 2016 20:28:57
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] DataCite DOI plugins

 

Hi Rory,

 

I just downloaded the release zip you created, which is supposed to be using Schema 2.2

The config file now references 2.2, but the export still produces the same fields that are not valid in 2.2 ( givenName, familyName, xml:lang, etc.)– thus the release would return an error from DataCite.

 

Tomasz

 

 

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Rory McNicholl
Sent: September-07-16 9:19 AM
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] DataCite DOI plugins

 

Hi Liz,

 

You are correct. Borys has put together a new version based on the 4.0 schema. To avoid confusion I have create a release and pre-release here

 

https://github.com/eprintsug/DataCiteDoi/releases

 

Which highlights which version of the schema is being catered for.

 

Thanks,

 

Rory

 

Rory McNicholl

Lead developer

Digital Archives & Research Technologies

University of London Computer Centre

Senate House

Malet Street

London

WC1E 7HU

 

t: +44 (0)20 7863 1344

 

The University of London is an exempt charity in England and Wales.

From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of Lizz Jennings <E.Jennings@bath.ac.uk>
Sent: 07 September 2016 13:43:12
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] DataCite DOI plugins

 

It looks as though someone has updated the files to provide version 4 metadata, which isn’t actually live in DataCite yet (unless I missed a very recent announcement).  It is imminent, though.

 

If you use the DataCite Test environment, I understand that can handle the newer metadata schema.

 

Lizz

 

--

Lizz Jennings BA MSc ACLIP MCLIP (Revalidated 2015)

Technical Data Officer

The Library 4.10, University of Bath, Bath, BA2 7AY UK

Ext. 3570 (External 01225 383570)

E.Jennings@bath.ac.uk

Research Data Management: http://www.bath.ac.uk/research/data

 

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Tomasz Neugebauer
Sent: 06 September 2016 19:48
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] DataCite DOI plugins

 

Thanks Lizz and Rory (and the other contributors to the updated DataCiteDOI plugin),

 

OK, #4 is what I ended up starting with (https://github.com/eprintsug/DataCiteDoi).

However, this one also doesn’t seem to work, not as-is anyway.  DataCite rejects the XML due to an error with an unexpected <givenName> <familyName> fields in the XML.  For example, it produces this XML for creators:

 

<creators>

<creator>

<creatorName>Neugebauer, Tomasz</creatorName>

<givenName>Tomasz</givenName>

<familyName>Neugebauer</familyName>

<nameIdentifier schemeURI="http://orcid.org/" nameIdentifierScheme="ORCID">0000-0002-9743-5910</nameIdentifier>

</creator>

</creators>

 

But the declared schema doesn’t allow for <givenName> and <familyName> elements.

http://schema.datacite.org/meta/kernel-2.2/metadata.xsd

…

<xs:element name="creators">

<xs:complexType>

<xs:sequence>

<xs:element name="creator" maxOccurs="unbounded">

<xs:annotation>

<xs:documentation>

The main researchers involved working on the data, or the authors of the publication in priority order. May be a corporate/institutional or personal name.

</xs:documentation>

<xs:documentation>Format: Family, Given.</xs:documentation>

</xs:annotation>

<xs:complexType>

<xs:sequence>

<xs:element name="creatorName">

<xs:simpleType>

<xs:restriction base="nonemptycontentStringType"/>

</xs:simpleType>

</xs:element>

<xs:element name="nameIdentifier" minOccurs="0">

<xs:complexType>

<xs:simpleContent>

<xs:extension base="nonemptycontentStringType">

<xs:attribute name="nameIdentifierScheme" use="required"/>

</xs:extension>

</xs:simpleContent>

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:sequence>

</xs:complexType>

</xs:element>

…

 

I suppose we should move the technical discussion onto the GitHub for the DataCite plugin.

Is there a way to activate and coin a DOI using the command line for testing purposes?

Thank you so much for working on the DataCite plugin, and I hope we can have a working Bazaar plugin for this. 

 

Tomasz

 

 

 

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Lizz Jennings
Sent: September-05-16 4:38 AM
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] DataCite DOI plugins

 

Hi Tomasz,

 

We’re using Number 4 – it’s very reliable.  We’ve extended the metadata profile to export a lot more fields than the default, and made some tweaks to navigate our firewall, but otherwise use it as is.

 

Lizz

 

--

Lizz Jennings BA MSc ACLIP MCLIP (Revalidated 2015)

Technical Data Officer

The Library 4.10, University of Bath, Bath, BA2 7AY UK

Ext. 3570 (External 01225 383570)

E.Jennings@bath.ac.uk

Research Data Management: http://www.bath.ac.uk/research/data

 

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Rory McNicholl
Sent: 05 September 2016 08:42
To: eprints-tech@ecs.soton.ac.uk
Subject: Re: [EP-tech] DataCite DOI plugins

 

Hi Tomasz,

 

Number 4 is the one we're keeping up to date.

 

The original did not actually read the response from the datacite API to see whether the request to mint a DOI had been successful. This had led to the possibility of DOIs being faithfully kept in EPrints that datacite had no valid record for and therefore did not resolve.

 

We also added the action to allow administrators to mint DOIs by-button, as well as a few other features and bug fixes along the way.

 

Additional to that we are currently working with a number of institutions in the UK to map more EPrints metadata over to the optional Datacite metadata elements (whilst providing hooks to allow for a customised profile mapping where necessary)

 

Thanks,

 

Rory

 

Rory McNicholl

Lead developer

Digital Archives & Research Technologies

University of London Computer Centre

Senate House

Malet Street

London

WC1E 7HU

 

t: +44 (0)20 7863 1344

 

The University of London is an exempt charity in England and Wales.

From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
Sent: 02 September 2016 20:09:26
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] DataCite DOI plugins

 

I'm trying to install DataCite DOI minting plugin and having difficulties figuring out the best starting place.

 

We have these sources:

 

1.

http://bazaar.eprints.org/307/

This one looks like an early version from 2013. 

 

We also have this code in GitHub:

https://github.com/eprints/datacite

Is this the same code as 307?

 

2.

http://bazaar.eprints.org/380/

This one shows up twice in the Bazaar “Available” search for DOI (once as version 1.0.0 and then again as 1.1.0), both lead to this URL (http://bazaar.eprints.org/id/epm/DataCiteDoi-dev)

-          No file list

 

3.

http://bazaar.eprints.org/439/

-          No File List – doesn’t seem to be working

 

4.

And source here:

https://github.com/eprintsug/DataCiteDoi

 

-          This looks to have some updates, a button to control the DOI minting.

 

 

Which of these sources is the best place to start in terms of getting DataCite DOI minting working on a repository?

 

 

Tomasz

 

 

 

 

 

 

-----Original Message-----
From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Florian Heß
Sent: April-26-16 10:34 AM
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Defect bazaar package #439 (DataCiteDOI)

 

Hi,

 

may I follow up on this one. Unfortunately, the bazaar package of DataCite DOI plugin version 1.1.0, URL http://bazaar.eprints.org/439/, uploaded January 2016, is defect. EPrints 3.3.15 error message reads:

"No files found in package". The data in the epm package is not extractable. So do I have to do it manually, de-base64 files from .epmi and spoon-feed them to the system, download the files from GitHub, or how? :-)

 

Can I find the e-mail of a bazaar package maintainer somewhere, who may or may not be also the creator of the code, to notify in such cases?

 

 

Kind regards

Florian

 

 

Am 08.02.2016 um 10:24 schrieb Florian Heß:

> Hi E-Prints users and devs,

> 

> there are currently to versions of the DataCite DOI plugin,

> 

>    * https://github.com/eprintsug/DataCiteDoi - fork, not installable

> through EPrints basar, on-demand or automatic DOI coining.

> 

>    * https://github.com/eprints/datacite - original version, installable

> through E-Prints basar, auto-only DOI coining that bothers me after

> recent experiences from triggered magic in Coverpage plugin.

> 

> So, is there maybe a specific reason why the User Group version is not

> packed in an EPM package, yet?

> 

> 

> Regards

> Florian

> 

 

 

--

UB Heidelberg (Altstadt)

Plöck 107-109, 69117 HD

Abt. Informationstechnik

http://www.ub.uni-heidelberg.de/

 

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech

*** Archive: http://www.eprints.org/tech.php/

*** EPrints community wiki: http://wiki.eprints.org/

*** EPrints developers Forum: http://forum.eprints.org/