A Case Study in Development, Workflows,
and Ongoing Support
Technical Implementation of
ORCID Support for
Texas A&M Schola...
Talk Outline
 Background and Context
 Software Development Methodology
 Use Cases and Workflows
 Reflections and Futur...
Project
Background
 Institutional grant imperatives vs.
Campus IT capabilities
 Library Development Team’s role
 ORCID ...
 Agile Scrum
 Cyclical development with product-owner
review for each iteration
 Daily review of feature/bug-fix
develo...
 ORCID creation for present graduate
students
 ORCID association for present
ORCID owners
 ORCID creation for future st...
 Read-access to ORCID record
 Needed to see if a student/researcher has
a record yet
 Write-access to ORCID record
 Ne...
 Email prelude sent to students based
on campus records
 ORCID creation script - as a member
institution, we are permitt...
 The essential element of the grant as
communicated by our PI
 The ORCID is now a field in the Vireo
ETD Submission/Mana...
ETD Work (in batch) is exported from
Vireo
Workflows:
Adding ETDs
ETD Work (in batch) is exported from
Vireo
Workflows:
Adding ETDs
ORCID Management App – Front Page
Workflows:
Adding ETDs
ORCID Management App – Upload
Vireo Export Zipfile of Work XML Docs
Workflows:
Adding ETDs
ORCID Management App – Zipfile
Upload console information
Workflows:
Technical
View of ETD
Addition
ORCID Central –following email link to
provide authorization
Workflows:
Adding ETDs
ORCID Central Redirects to ORCID
Middleware
Workflows:
Adding ETDs
ORCID Central Redirects to ORCID
Middleware – console output
ORCID Central Reflects Work Addition
Workflows:
Adding ETDs
Reflections
and Future
Work
 Emails to graduates
(potentially months after ETD
submittal) may not succeed…
 Our PI is pu...
Reflections
and Future
Work – Recent
Developments
 ORCID values have recently
been put into campus LDAP
and made delivera...
Reflections
and Future
Work
 Currently planning for
production roll-out
 Developer wish-list
 Mock ORCID-central server...
Upcoming SlideShare
Loading in...5
×

Technical implementation of ORCID support for Texas A&M scholars

560

Published on

From the ORCID Outreach Meeting, May 21-22, 2014, held in Chicago, Illinois, USA. https://orcid.org/content/orcid-outreach-meeting-and-codefest-may-2014

Best practices in the creation of ORCID identifiers for faculty, staff, and students: technical integration

Research organizations are creating ORCID iDs and integrating them into a variety of systems, from personnel databases, to directories, repositories, and university presses. In this session, organizations will share information and strategies on technical aspects of working with ORCID APIs, strategies for modifying internal systems to capture and store ORCID iDs, and interactions with other identifiers.

Moderator: Simeon Warner, Research Associate, Cornell University

Presenters:

Urban Andersson, IT Librarian, Chalmers University of Technology
Peter Flynn, Lead Developer, Boston University
James Creel, Senior Lead Software Applications Developer, Texas A&M University

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
560
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Technical implementation of ORCID support for Texas A&M scholars

  1. 1. A Case Study in Development, Workflows, and Ongoing Support Technical Implementation of ORCID Support for Texas A&M Scholars James Creel, Senior Lead Software Applications Developer http://orcid.org/0000-0001-9108-5190
  2. 2. Talk Outline  Background and Context  Software Development Methodology  Use Cases and Workflows  Reflections and Future Work
  3. 3. Project Background  Institutional grant imperatives vs. Campus IT capabilities  Library Development Team’s role  ORCID Assignment for all graduate students  Future plans for Campus-wide identifiers
  4. 4.  Agile Scrum  Cyclical development with product-owner review for each iteration  Daily review of feature/bug-fix development  Product Ownership  Grant PI  Customer-facing concerns Development Methodology
  5. 5.  ORCID creation for present graduate students  ORCID association for present ORCID owners  ORCID creation for future students, faculty, and staff contributors  Work association for ETDs (Electronic Theses and Dissertations) from the Vireo ETD Management System Use Cases
  6. 6.  Read-access to ORCID record  Needed to see if a student/researcher has a record yet  Write-access to ORCID record  Needed to associate ETDs (electronic theses and dissertations) with students’ records  Central requirement of grant, as communicated by our PI product owner Use Cases, Continued: Institutional Concerns
  7. 7.  Email prelude sent to students based on campus records  ORCID creation script - as a member institution, we are permitted to create a record for each of our graduate students  This does invoke a request for each scholar’s acknowledgement/claim  It behooves us to provide a middleware application for TAMU scholars to manage their ORCID accounts during their association with the University Workflows (1): Mass ORCID Creation
  8. 8.  The essential element of the grant as communicated by our PI  The ORCID is now a field in the Vireo ETD Submission/Management system and provided by campus LDAP if available  Vireo records can be exported in the ORCID Works XML format to be read TAMU Libraries middleware Workflows (2): ETD works
  9. 9. ETD Work (in batch) is exported from Vireo Workflows: Adding ETDs
  10. 10. ETD Work (in batch) is exported from Vireo Workflows: Adding ETDs
  11. 11. ORCID Management App – Front Page Workflows: Adding ETDs
  12. 12. ORCID Management App – Upload Vireo Export Zipfile of Work XML Docs Workflows: Adding ETDs
  13. 13. ORCID Management App – Zipfile Upload console information Workflows: Technical View of ETD Addition
  14. 14. ORCID Central –following email link to provide authorization Workflows: Adding ETDs
  15. 15. ORCID Central Redirects to ORCID Middleware Workflows: Adding ETDs
  16. 16. ORCID Central Redirects to ORCID Middleware – console output
  17. 17. ORCID Central Reflects Work Addition Workflows: Adding ETDs
  18. 18. Reflections and Future Work  Emails to graduates (potentially months after ETD submittal) may not succeed…  Our PI is pursuing a delegation of update privileges that occurs during Vireo workflow
  19. 19. Reflections and Future Work – Recent Developments  ORCID values have recently been put into campus LDAP and made deliverable in Shibboleth payloads  Vireo and our ORCID Management App are already enabled to receive this information – we will further enable our IR and other applications as we are able.
  20. 20. Reflections and Future Work  Currently planning for production roll-out  Developer wish-list  Mock ORCID-central server for unit-testing  Pure HTML5/Angular.js frontend uncoupled from Middleware API for next generation of the software
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×