Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
The University of Sydney Page 1
ORCID @ Sydney
Nathaniel Lewis| Director
Research Reporting Analysis Data & Systems | Rese...
Institutional perspective
–  Joined ORCID as Institutional Member June 2014
–  Developed a project plan with a phased appr...
Alignment to Research Strategy
–  For the Researcher
–  Distinguish research outputs and affiliations from researchers wit...
ORCID Entry Points opportunities – Create or Link
–  New HDR student enrolment at the university: include ORCID ID as requ...
Challenges
–  Policy, procedures & workflows
–  Aim to manage ORCID content on behalf of all Sydney researchers
–  Conside...
Technical Successes - IRMA Integration
IRMA Integration - Creation of ORCID within IRMA
IRMA Integration – Confirmation of ORCID creation
IRMA Integration – Confirmation of ORCID creation
IRMA Integration – Claiming of ORCID creation
IRMA Integration - Manage Authorisation
IRMA Integration - Confirmed Authorisation
What Next
–  Consistent approach for research outputs & records management
–  Support for researcher mobility
–  Identific...
What Next
ORCID	
  |	
  RegistryUniversity	
  |	
  RRADSUniversity	
  |	
  CommunicationsYear
PILOT:	
  Communications	
  ...
Questions?
nathaniel.lewis@sydney.edu.au
Upcoming SlideShare
Loading in …5
×

ORCID Implementations with University RIM Systems (The University of Sydney, N. Lewis)

856 views

Published on

Lightning demo presentation at the 2016 February ORCID Outreach Meeting in Canberra, Australia (15-16 February 2016)

Published in: Technology
  • Be the first to comment

  • Be the first to like this

ORCID Implementations with University RIM Systems (The University of Sydney, N. Lewis)

  1. 1. The University of Sydney Page 1 ORCID @ Sydney Nathaniel Lewis| Director Research Reporting Analysis Data & Systems | Research Portfolio ORCID Outreach Presentation Tuesday 16th February 2015
  2. 2. Institutional perspective –  Joined ORCID as Institutional Member June 2014 –  Developed a project plan with a phased approach through 2015/16 to; –  Enable University of Sydney researchers and research students to claim ORCIDs and authorise the University to manage their ORCID registry record on their behalf; –  Implement ORCID researcher identifiers in research support systems including IRMA, Academic Profiles Online, ERA, Sydney eScholarship and Sydney Research Online repositories, Research Data Registry, Student and HR systems; –  Encourage University of Sydney researchers to include ORCIDs in journal manuscript and grant submission systems, making it easier to identify and harvest researcher publications data from external systems such as SCOPUS and Web of Knowledge/Web of Science. –  Next to pilot ORCID implementation across Sydney to align to grants submission –  Now have ORCID operating through IRMA Strategy, challenges and successes of ORCID implementation
  3. 3. Alignment to Research Strategy –  For the Researcher –  Distinguish research outputs and affiliations from researchers with identical or similar names. –  Ensure the correct attribution of all research outputs, including research publications, data sets, grants and awards. –  Adopt an international unique identifier and publicly available profile of research outputs that will follow the researcher across institutions and affiliations – even if the researcher moves overseas. –  Appropriate recognition for complete scholarly output. –  For the University –  Complete and accurate attribution of University of Sydney-authored publications in research publication data sets for submission to ERA and HERDC research reporting exercises and external ranking agencies. –  Improved research assessment and ranking results, which in turn results in increased block funding and improves the University’s capacity for the strategic recruitment and retention of high-performing staff and students. –  Accurate citation and researcher affiliation data in external systems such as journal citation databases, journal publication databases and research grants management systems. –  Improved data quality in external systems (e.g. citation databases) streamlines the publications data acquisition process and reduces the administrative burden on research support and data acquisition teams.
  4. 4. ORCID Entry Points opportunities – Create or Link –  New HDR student enrolment at the university: include ORCID ID as required item on enrolment form. –  Submission of HDR student research proposal: include ORCID ID as required item on form. –  Submission of HDR student thesis: require ORCID ID before submission is permitted. –  New academic staff member joins the university: require ORCID ID before SID is generated. –  Creation of academic staff record in IRMA: require ORCID ID (linked to SID) to create IRMA account. –  Publication submission: university policy requiring ORCID ID to be part of the signature/affiliation for submitted publications. –  Requiring ORCID IDs in email signatures for academic staff: include ORCID ID in university policy about email signature. (???) –  Grant submission: university policy requiring ORCID ID to be part of the grants application process.
  5. 5. Challenges –  Policy, procedures & workflows –  Aim to manage ORCID content on behalf of all Sydney researchers –  Considering policy frameworks, governance and implementation •  Population & Maintenance of records - capacity •  Supplementing Scopus / Thompson publications sweeps •  Use of ORCID to manage non–citation based disciplines –  Technical considerations –  Integration into existing Student, ICT, HR systems –  Minimise researcher burden –  Levering quality assured research information •  IRMA is populated with rigorously assured research outputs •  Populates Academic Profiles, OA Publications Repository, HERDC & ERA •  Data assurance processes & ORCID – record integrity
  6. 6. Technical Successes - IRMA Integration
  7. 7. IRMA Integration - Creation of ORCID within IRMA
  8. 8. IRMA Integration – Confirmation of ORCID creation
  9. 9. IRMA Integration – Confirmation of ORCID creation
  10. 10. IRMA Integration – Claiming of ORCID creation
  11. 11. IRMA Integration - Manage Authorisation
  12. 12. IRMA Integration - Confirmed Authorisation
  13. 13. What Next –  Consistent approach for research outputs & records management –  Support for researcher mobility –  Identification of further research opportunities such as collaboration and strategic recruitment –  Alignment to Scopus & Thompson databases, linking Scopus IDs, ResearcherIDs and harvesting of works –  Links to FigShare etc and researcher focussed social media platforms –  Use ORCID when submitting journal manuscripts & grant applications –  Integration into Student, ICT, HR Systems –  Use ORCID in correspondence/university signature block ORCID into the Future
  14. 14. What Next ORCID  |  RegistryUniversity  |  RRADSUniversity  |  CommunicationsYear PILOT:  Communications  to  pilot   participants:  HCRs,  VELiM,  SMS Communicate  upcoming  creation   of  ORCIDs  to  Staff  News,  Research   News,  RMN,  FLLs,  Champions  –   ahead  of  email  from  ORCID. PILOT:  Generate  email  to  pilot   group:  “Claim  and  authorise   Sydney  to  manage  ORCID” REVIEW  PILOT:  Gather  feedback   from  pilot  groups.  Invite  pilot   participants  to  be    “champions”.   Finalise  project  plan  and  pilot,  and   engage  project  steering  group,  PM Paper  to  SEG  RG Information  to/consultation  with   Faculty  RCs:  Discuss  ORCID  with   Faculty  RCs,  RMN,  FLLs ORCID  |  API PILOT:  Prepare  dataset  (IRMA) CALL  API:  Create  ORCIDs  and   populate  records Set  registry  permissions Communicate  outcomes  of  Pilot   and  feedback  to  SEG  RC.  Request   to  endorse  full  implementation   (ADRs) Prepare  full  dataset  (IRMA) Generate  email:  “Claim/ authorise  Sydney  to  manage   ORCID” Set  registry  permissions   PILOT:  CALL  API:  Create  ORCIDs Check  records  for  duplications Check  ORCID  registry  for  existing   records  (exclude  from  set) 10  days:  Follow  up  if  not  claimed 10  days:  Follow  up  if  not  claimed Contact  ORCID  technical  team  to   merge  duplicate  records Website:  Update  information   ORCID  web    page  (info  resources) Maintain  dataset  (IRMA).  Create   new  ORCIDs  and  update  ORCID   records  from  new  data  in  IRMA   (quarterly  -­‐  ongoing) CALL  API:  Create  ORCIDs  and   populate  new  identifier  records   (quarterly  -­‐  ongoing) Generate  email  based  on   quarterly  dataset:  “Claim/ authorise  Sydney  to  manage   ORCID” Set  registry  permissions  for  long-­‐ lived  access  tokens. 10  days:  Follow  up  if  not  claimed Include  note  about  ORCID  in  HR/   induction  information  (on   intranet?)   Begin  approved  integrations   with  University  systems.   Schedule  implementation  of   id_ORCID  (or  similar,  depending   on  system)  field  in: • Research  Data  Registry   (implemented)   • IRMA  (Schedule  2015) • Academic  Profiles  Online • Sydney  eScholarship   Repository • ERA  Repository • SRO  Repository Communicate  upcoming   integrations  and  actions   researchers  can  take  to  leverage   the  benefits  of  ORCID  by   connecting  to  other  systems.   Including:   • Link  SCOPUS  to  ORCID • Link  ThompsonID  to  ORCID • Link  to  FigShare,  Reesarch   Gate  and  researcher-­‐ focussed  social  media   platforms • Use  ORCID  when  submitting   journal  manuscripts • Use  ORCID  in  grant   applications • Use  ORCID  in  all   correspondence/university   signature  block Work  with  SRRP  WP  to  promote   ORCIDs  in  standard  signature   blocks Ongoing:  Maintain  information   resources       HANDOVER  TO  RRADS  APPLICATIONS  TEAM  –  TRANSITION  TO  MAINTAINING  ORCID  RECORDS  AS  BUSINESS  AS  USUAL. IMPLEMENTATION MAINTENANCE  &  INTEGRATION PILOT  IMPLEMENTATION  &  STAKEHOLDER  CONSULTATIONS 2015/16 Plan  integrations  with  University   systems.  Seek  endorsement    in   paper  to  SEG Add  endorsed  changes  to   University  systems  to  production   schedules  for  Q3/Q4  2015 2016/17
  15. 15. Questions? nathaniel.lewis@sydney.edu.au

×