ORCID/ORCID-Mock-API-Web-Application — Issue #12: Batch work uploads
Author: wjrsimpson
Created: 2012-03-09 15:56:46+00:00
State: open

There are enough legitimate authors with 500+ titles for it to be a known problem. And some with 1000+ - and believe it or not, we have legitimate papers with 1000+ authors. Mostly these later come from the same area: particle physics. The first set tend to come from commercial labs – for example, I found a lab in china that produces effectively boilerplated papers on doping effects in semiconductors. They are authored by the same folk, and they publish more than 1 a week. And again, in datasets that use genome data, you get massive quantities of authoring metadata.

(There are plenty of overmerged authors too, I have a research strand on that area.)

Hm, that sounds good, but the multiple permission sounds like a fiddle, I thought we could run more updates as long as it was in the 5 minutes.

Cheers,

Mike

From: Will Simpson [mailto:Will.Simpson@semantico.com]
Sent: 09 March 2012 14:59
To: Taylor, Michael (ELS-OXF)
Cc: Geoffrey Bilder; Declan Newman
Subject: Re: FW: Small Enhancements 12-2 - Analysis

Hi Mike,

You are right, the API specification (ORCID Deposit/Update API Phase 1) does indeed say that you can either do either of the following.

a) send (and replace) all works
b) add an individual work

However, I suspect we are being a bit mean with b) and we should allowing POSTing of multiple works in a single API call. In other words, the body of the POST request would include multiple elements. How does that sound?

One thing to consider though, is that you will have to ask the user for permission for each and every batch (via the OAuth work flow). This is because the access token you will be granted will only be good for a single update call to the API (you may use the token again after that, but it will be downgraded to read-protected only).

You are also correct about not needing to send an element when PUTting or POSTing to /{ORCID}/orcid-works. In fact, we are going to return an error if it is included (HTTP 400), so that it is more explicit that this call will never update the .

How many users do you have that have >500 works? How do they get so many works, and what kind of content is it? I know Scopus has some excellent tools for merging records, but still I am wondering if there could be some duplication or incorrect assignment going on there?

Regards,

Will

On 08/03/2012 13:22, Taylor, Michael (ELS-OXF) wrote:

Hi Will, Declan

We’re having a discussion about sending data from Scopus to Orcid, following on from our recent telecom. Case is where we have users who have a very large data set, > 500. Our developers would like to send orcid-bio data, then batches of orcid-work data. Documentation appears to allow for either sending all (and replacing), or adding individual works. Is there middle ground?

The developers also ask if we have to send orcid-bio each time we send orcid-work, I believe that it’s clear from the API Deposit / Update API that we do *not* need to do that.

Thanks

Mike