EPrints Technical Mailing List Archive

Message: #07424

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

Re: [EP-tech] ORCID Support Advance Plugin

Thank you for the information.

We have some improvements done resp. are working on them for the plugin, e.g. date filtering for import/export. We are happy to contribute these things over GitHub to the official plugin, such that everybody can reuse them. However, we are currently preparing our roll-out of ORCID which should already happen next month. Thus, we have to concentrate first on our local roll-out, and therefore any pull request on GitHub is probably postponed for the time afterwards.

We appreciate on the other hand any tipps for working with the code from EPrints or the ORCID plugin. Also, if you have any design principles we should respect or any fixed ideas how a feature should work, then it would be good to discuss these things before any implementation. And let us know when you start to work on some aspects, such that we can avoid double work.

Best regards,

Am 21.08.2018 um 17:45 schrieb Will Fyson:

Thanks for alerting us to this issue and apologies for not getting back to your
previous email Volker. We'll take a look at this along with all the other
feedback we've received concerning the ORCID Support Advance plugin and begin
prioritising the next steps for development. However, I'm afraid I'm unable to
confirm any dates for when these updates will be delivered right now, but will
try and keep you all up to date with any developments.

This project was originally funded, but future development remains unfunded.
Therefore if anyone is willing to make contributions via the GitHub repository,
then please let us know.

Many thanks,


*From:* Philipp Zumstein [philipp.zumstein@bib.uni-mannheim.de] *Sent:* 21
August 2018 14:09 *To:* Eprints-tech *Subject:* Re: [EP-tech] ORCID Support
Advance Plugin

I tried to replicate this issue, because it sounds like a major issue in
the plugin:

1. Change my name, email to some person with >100 publications
2. Disconnect and connect again to my ORCID-Sandbox-Account
3. Wait a little for the trigger to go through all the publications with
my new name and add my ORCID id there
4. Export X items to ORCID

I could successfully export one single entry and also a few entries to
ORCID, e.g. a selection of 67 entries worked for me. However, when
trying to export everything (>500 entries) then this does not work, and
an export of 104 entries does fail as wellr.

How can we pack the publications into smaller chunks when exporting to
ORCID? Can we put the lines 114-135 [2] into a loop where we 'splice'
the array $orcid_works before into smaller parts of size less than 100
and only use that part within the write_orcid_record?

For errors like this an error message is missing and in the code marked
as a TODO [1]. When will this TODO been tackled?

Best regards,


Am 14.08.2018 um 17:14 schrieb Schallehn, Volker:

Hi Will,

we are using the ORCID support and ORCID Support Advance plugins (both from Github). We have discovered some problems trying to export publications from our EPrints repository (3.3.15) to ORCID. According to a mail I got from the ORCID support it's not possible to export more than 100 publications at once. The EPrints ORCID export function should set a limit to 100 publications, because any export with more publications will fail.

But the export of individual publications also fails if the author has more than 100 publications. It looks as if the selection of the individual publication to be exported is not effective, but the entire list is transferred in the background. I received this mail from ORCID Support today, after trying to export a single publication:

"I can see that your request to post works is still using the bulk works end point (/works). That will return a 200 status as long as the call is successful and then a full error message that has the status of each work included in the bulk file with either the success status for that work, or a error with information why the specific work couldn't be posted. If there's a way to get the EPrints software to return the full error message that will be easiest to determine what is going wrong."

Do you have any idea, what's going wrong with the ORCID Support Advance plugin? Since there are no meaningful logs, it is difficult to detect the error. If you are trying to export 1 publication, there is always the message that 1 publication has been exported to ORCID successfully, but it never arrives in ORCID.

Thanks for your help