Project plan

Introduction The guiding principle of ORCID implementation at York will be the benefit it brings to researchers. Central to the function of an ORCID iD is that it is owned by the researcher and not by any one institution. This sense of researcher ownership and the use of ORCID as a tool to benefit rather than regulate researchers is vital to successful implementation. The institution would subsequently benefit in many ways, including: improved data capture, tracking outputs, improving open access monitoring, identifying impact, easier reporting to funders and sharing of information between systems. The key features of the pilot project are: An emphasis placed on the researcher registering for an ORCID iD supported by an advocacy programme and institutional support The implementation of a University Publications Policy which requires researchers to use an ORCID iD when preparing publications (i.e. registration will be backed by institutional policy) (formal approval in progress)  Integration of ORCID within the University’s Current Research Information System, Pure  Utilisation of Pure to populate the ePrints institutional repository (White Rose Research Online) with ORCID iDs via the automatic connector. It is also intended to align ORCID with other institutional systems, but this is likely to fall outside the project timeline. For example: University IDM system (a new IDM system is being procured)  Research data management infrastructure (currently being planned) Grants management system (at a very early review stage Implementation plan and timeline                                               Activity Who Months 1: Consultation Project team 1-3 With a number of stakeholders across the University it is essential to ensure coordination and agreement across all areas. Of central importance to this is researchers themselves, in particular through departmental and central Research Committees. This stage will deliver an analysis of stakeholders’ views on: benefits of ORCID to them, perceived issues and concerns, and how they would like to see implementation happen. 2:  Initial advocacy / information provision Project Team; Academic Liaison Librarians 1-5 To secure researcher engagement and uptake it is important that researchers are aware of the benefits of ORCID before they are asked to actively take part in the scheme. This stage will work in parallel with the consultation to develop researcher understanding of ORCID. Key activities will be to: identify ORCID advocates in departments; create web resources; deliver departmental information sessions; develop an Academic Liaison Librarian support service. 3: Publications Policy Information Directorate Research Support Team; Research Strategy and Policy; University Research Committee 1-5 The University of York Publications Policy (pending formal approval) will require the use of ORCID by York researchers when submitting and recording their publications (see Annex 1). This principle is supported by the PVC Research (see Annex 2) and will be approved by Research Committee which will provide strategic support for ORCID. It is intended that the Publications Policy will be implemented from the start of the 2014/15 academic year with ORCID being an important part of this implementation. 4:  White Rose Research Online (Repository) development Project team; Digital York; White Rose Libraries repository team 1-3 White Rose Research Online (WRRO) is the repository for the University and integration with ORCID will be an important part of the project. Information is pushed from Pure to WRRO and it is intended that ORCID iDs will be added to this information. The capability to do this currently exists within the WRRO ePrints software but must be correctly configured. All White Rose partners support this development. 5: Pure (CRIS) development Project team; Digital York; IT Services; Research Strategy and Policy; Atira; Pure UK User Group 2-6 (+ongoing) ORCID functionality has been available in Pure since February 2014 (v.4.18). As yet, this  functionality has not been widely tested. Implementation would be in two main phases: Phase 1: Running a Pure instance on a test server and testing functionality in a variety of situations including integration with existing identifiers, author registration of ORCID iDs, and importing of ORCID iDs from Scopus. Phase 2: Implementation of a live instance once full testing is complete. Supporting ORCID functionality within Pure will be one of the most important parts of the project. The Information Directorate and Research Strategy and Policy Office will work closely with Atira (providers of Pure) and the Pure UK User Group to identify and test bug fixes and new developments. An example of this will be integration with Scopus for import of bibliographic records. Implementation of the core functionality will be the initial focus, but development will be continuous throughout the project. 6:  Pure/WRRO connector development Digital York; White Rose Libraries repository team; Atira 3-6 This work will need to take place once functionality for ORCID iDs is established in Pure and WRRO. This will ensure that ORCID iDs within Pure are correctly transmitted to WRRO and that the two systems are synchronised. We have consulted with Atira and they currently view the revised Pure ePrints connector as a standard feature to be developed for the community. 7: Author data disambiguation for records in Pure and WRRO Additional staffing; White Rose Libraries repository team 5-9 Pure and WRRO do not currently use person identifiers for contributors, relying entirely on names. Addition of ORCID iDs as personal identifiers in Pure and WRRO will require work to disambiguate contributors currently in the systems with the same or similar names. Additional staff will be employed to do this clean-up work. The type and extent of the work needed is not known; part of this stage will be to make an assessment. 8:  Departmental case study Project team; Department(s) to be selected; Academic Liaison Librarians 5-7 This stage will involve working closely with a group of researchers to test workflows and systems. It will also contribute to identifying advocates for ORCID within the York academic community. 9:  University-wide implementation and promotion Project team; Academic Liaison Librarians 5-9 This stage will support roll-out of ORCID across the University. This is timed to correspond with implementation of the new University Publications Policy. 10: Review and reporting Project team 1-9 Review will be an ongoing and iterative process throughout the project. The final review process will both assess the effectiveness of the strategy adopted and also develop a sustainability plan. Progress will be reported to ORCID, Jisc, ARMA, UK HEIs, and other interested parties in accordance with the project brief, using blogs, Twitter and other appropriate channels and through our engagement with the Pure UK User Group.