From the ORCID Outreach Meeting, May 21-22, 2014, Chicago, Illinois, USA, https://orcid.org/content/orcid-outreach-meeting-and-codefest-may-2014
ORCID identifiers in access management
Universities and other research organizations have begun utilizing the ORCID identifier to manage access to repositories and research information systems. This session will feature a discussion of integration opportunities, policy and privacy issues, and demonstrations by research organizations.
Moderator: Ed Pentz, Executive Director, CrossRef
Presenters:
Keith Hazelton, Senior IT Architect the University of Wisconsin-Madison/Chair of Internet2 MACE-Dir working group
Jared Lyle, Director of Curation Services, Inter-university Consortium for Political and Social Research (ICPSR), University of Michigan
Ken Okaya, Product Manager, Rightsholder Services, Copyright Clearance Center / slides
Doug Hahn, Senior Information Technology Manager, Texas A&M University
Elaine Westbrooks, Associate University Librarian for Research, University of Michigan
3. The Project
All graduate students will have an ORCiD created for
them by TAMU and stored for later use.
• What is an ORCiD?
• An identifying number tied to a person that is
associated with all types of research.
• Maybe this is something that campus IT might be
interested in tackling.
4. Conversation
with
Campus
IT
• Everyone involved knew that placing the ORCiD in
the campus directory just made sense.
• Once in the campus directory it could be exposed
through Shibboleth, and existing web services.
• Campus IT was excited about the project and were
immediately on-board!
• Except for one thing…
• Campus IT was extremely busy and wouldn’t be
able to help with the project anytime soon.
Early on in the project we started having
conversations with campus IT.
5. Next Steps
with
Campus
IT
If the Library builds it, campus IT will use it.
• ORCiD would be stored in Campus LDAP.
• Campus IT would ensure that ORCiDs would be
exposed by campus Shibboleth and Web Services.
• The Library would undertake the process for
creating the ORCiDs.
• The Library would provide front line support for
any questions surrounding ORCiDs.
• The Library would maintain an authoritative list of
known ORCiDs that would be sent to campus LDAP
daily.
• This list would overwrite all existing ORCiDs in
campus directory.
6. The Division
of Labor
Early on we realized that two distinct applications
were going to be needed.
• One application was going to be needed to process
all the graduate students and create ORCiDs.
• Another application was needed for the ongoing
support and integration into other applications.
7. Integration
and Support
Web front ends that other applications can direct
patrons to that expose the ORCiD API.
Generic Web Services that can be used by other
TAMU applications related to ORCiD.
Provide a simple one stop application to manage tasks
surrounding ORCiDs at TAMU.
8. Creating of
ORCiDs
Of the two aspects of the project creating the ORCiDs
was the easiest.
• Understand the published API from ORCiD.
• Test various processes.
• Working with librarians on outreach (mass emails).
9. Process
workflow
TAMU stores token with READ access for later use
Email sent to patron with information about ORCiD
Patron goes to ORCiD to claim ID and add additional info
TAMU uses API to create new ORCiD with Last, First, email
TAMU asks for READ limited to patron account
10. The Backend
Scripts
Nothing glamorous or exciting about the scripts we used
to create the ORCiDs.
Backend database full of graduate students.
2 PHP scripts were created. Main program, and the
utilities. Maybe 400 lines of code max.
All of the scripts were based off of various command
lines examples that can be found in the ORCiD
knowledgebase.
01/2014 – Email to patrons telling them about ORCiD.
02/2014 – Email to patrons telling them we are creating.
03/2014 – created 10,000 ORCiD in about 4 hours.
13. Lessons
Learned
Spend more time with the ORCiD knowledge base.
Tokens granted to institutions by patrons can be
complicated and may not allow you to do what you
hope for.
Use the ORCiD sandbox more to test out all the
features available to you.