Hi All,
We’ve encountered a number of issues recently in the production system, which did not come up in our testing (though this is most likely down to our test data, rather than anything to do with API versions). When users have attempted to use our app to send publication metadata from our repository to their ORCID Record as works.
Specifically, we have allowed them to select multiple works to be sent, and they get errors when multiple items are published in the same Journal or Book, as the API error on multiple items with the same ISSN or ISBN.
Is this really intended behaviour? It seems odd to me.
I imagine the workaround is to send each work as a new work-update process, rather than sending them in batches.
Your input would be appreciated.
Andrew Devenish-Meares
Solutions Analyst/Programmer
Administrative Applications, Information Services
Information Technology Directorate
University of New England
Armidale NSW 2351 Australia
Skype for Business: sip:adev...@une.edu.au
Phone: 61 2 6773 4098
Email
adev...@une.edu.au
www.une.edu.au
CRICOS Provider Number: 00003G
--
You received this message because you are subscribed to the Google Groups "ORCID API Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orcid-api-users+unsubscribe@googlegroups.com.
To post to this group, send email to orcid-api-users@googlegroups.com.
Visit this group at https://groups.google.com/group/orcid-api-users.
For more options, visit https://groups.google.com/d/optout.
Hi Catalina,
Thanks.
In our repository, we record the type against the Higher Education Research Data Collection (HERDC) type, and we have a table to map HERDC to ORCID work-type. Looking at the items in question in this instance, we have:
a. An item that's recorded as HERDC type B1, which we're mapping to book-chapter
b. An item that's recorded as HERDC type A3, which we're mapping to edited-book
This produces the error
Bad Request : Works "Utopia and a Garden Party" and "Branching Out through VirtualPREX: Enhancing Teaching in Second Life"(put-code '745370') have the same external id "9781848881402"
We get this in production and sandbox, using API v1.2.
Is this expected? Should the record holder really only be pushing the book or the chapters and not both?
I'll prompt the Library team to ensure this classification is correct as well.
Cheers
Andrew
Hi,
We're sending this as ISBN. The generated XML looks like:
<work-external-identifier>
<work-external-identifier-type>isbn</work-external-identifier-type>
<work-external-identifier-id>9781848881402</work-external-identifier-id>
</work-external-identifier>
Thanks.
Andrew
Andrew Devenish-Meares
Solutions Analyst/Programmer
Administrative Applications, Information Services
Information Technology Directorate
University of New England
Armidale NSW 2351 Australia
Phone: 61 2 6773 4098
Email:
adev...@une.edu.au
www.une.edu.au
CRICOS Provider Number: 00003G
Hi Catalina,
Thanks for that. Not the outcome I'd have liked, but we'll make it work.
Is there a page somewhere detailing the v2 changes and anticipated timeline?
Thanks
ADM
Andrew Devenish-Meares
Solutions Analyst/Programmer
Administrative Applications, Information Services
Information Technology Directorate
University of New England
Armidale NSW 2351 Australia
Phone: 61 2 6773 4098
Email:
adev...@une.edu.au
www.une.edu.au
CRICOS Provider Number: 00003G