EPrints Technical Mailing List Archive

Message: #05524

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

Re: [EP-tech] Import from ORCID

Hi Tomasz
I agree that adding the orcid id as an additional id is a good idea and yes you can extend the functionality of the cgi/users/lookup/name script to extract the orcid id from the database and add it to the creator data on the workflow. Essentially you can copy what is done for the email (id) field i.e. if your new field was "orcid_id" you would then extract the current state of the field from the param _orcid_id, use it to search for values in the database table column creators_orcid_id and use the form: "for:value:relative:_orcid_id" to write the selected value back to the component field.
However, this will only allow you to reuse orcid ids that have been entered for other creators. If a lot of your creators are users and you have a way of getting users to connect their eprints user account to their orcid profile (which is something you can do using the member api) then you could consider changing your lookup to consider users rather than other creators.
If your creators are not users and you are interested in looking up orcid ids from the ORCID site then you could look at the Rioxx2 plugin as this includes an autocomplete that looks up authors using the public orcid api. 

I hope that helps
Peter

On 23/03/16 17:06, Tomasz Neugebauer wrote:

Thank you, I look forward to trying out the Tier 2 API plugin.  For now, I'm still confused about what additional functionality the Tier 2 API provides - I need to read up on this more.

About adding ORCID to creators metadata, this seems like an essential step.  Initially, I think I would be adding it as an additional ID, rather than replacing the email address which is being used now as an ID.
After I add ORCID to the creators, on my test server, I see that I can enter it on the deposit workflow, but the autocomplete for creators is ignoring the ORCID.  There is an autocomplete script in (cgi/users/lookup/name) that is responsible for the drop-downs while depositors enter metadata, is that what I would need to update to make sure that the ORCID ID gets filled in like the email address?

Tomasz



-----Original Message-----
From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of peter
Sent: February-06-16 6:36 AM
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Re: Import from ORCID

Hi Tomasz
I am glad the plugin works for you. It was only ever really intended as a demonstrator of what you could do with the public api so all of your suggestions are good ideas to take it further and make it more useful for your repository. For other ideas of what can be done (and the code to do it) please have a look at the orcid code on https://github.com/eprintsug/orcidt2. This uses the member api but you can register with Orcid.org for access to the sandbox to try things out.

Concerning adding IDs, personally, I would add the id to the users and the contributors (for some repositories users are contributors for others they are not)

Thanks
Peter

On 05/02/16 22:07, Tomasz Neugebauer wrote:

I recently installed the Import from ORCID plugin
(http://bazaar.eprints.org/354/)  on our repository, and it works
really well.

Thanks so much to the developer(s) of this excellent plugin.

A couple of questions:

1.Is there any reason not to make this plugin available to regular
"user" accounts?

2.How difficult would it be to do some basic 'duplicate' detection as
a part of this plugin? What I mean is, could the plugin check and
signal which of the items in ORCID are already in the repository?

I also have a related question about managing ORCID ids as a part of
the user profile in the repository.

I added the ORCID id to user profile fields, so that users can
associate their ORCID ID to their accounts.

  It shouldn't be too difficult to check for an ORCID id of the
currently logged in user, and if it exists, populate the import box
with it by default.

Would it also make sense to add the ORCID id to the creator/author
metadata?  Any comments on the best practice of doing that, given that
ORCID ids should be useful in metadata interoperability/export.

Tomasz



*** 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/


--
Peter J. West
Digital Repository Services Ltd


*** 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/

*** 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/




--
Peter J. West
Digital Repository Services Ltd