170 likes | 311 Views
Preparing for the REF. CRIS implementation at Lancaster Michael Dunne. Background. Implementation of an Institutional Repository 2005 based on Eprints software something ‘we ought to be doing’ Library Policy Committee 2007 scope repository type activity across University
E N D
Preparing for the REF CRIS implementation at Lancaster Michael Dunne
Background • Implementation of an Institutional Repository • 2005 based on Eprints software • something ‘we ought to be doing’ • Library Policy Committee 2007 • scope repository type activity across University • agreement to stay with Eprints • make recommendations to Research Committee • establish critical mass • automate where possible
Background • Phase 1 • backfill Eprints from 1999-2007 • RAE census period 1st Jan 2001 – 31st Dec 2007 • commitment given for extra staff • funding for new server • Phase 2 • 2008 onwards – encourage self-archiving (with no mandate) • offer assistance with mediated archiving
Rapid Growth • Eprints grew • Jan 2008: 633 items • Jan 2009: 15361 items – 2264 full text • Importing from existing publications systems • Mediated plus self-archiving • Eprints did not support the RAE directly – the submission was by spreadsheet – plugin came too late
Why a CRIS? • Eprints lacked integration • authentication • human resource data • funding data • activities data • Eprints lacked reporting tools • either the open source developers were building them, or • it would need significant development • We lacked Eprints technical support in-house
Tender • Considered building our own CRIS • Tender issued 2009 • Won by Dutch company, Atira – Pure • Project managed by ISS • Prince2 • Repository Manager on project team
Pure Portal • Portal was an additional option – extra cost • Public facing side of Pure • There is duplication of content • Pure Portal • Eprints • faculty databases • personal Web pages • Rationalisation will (may?) be inevitable
CRIS vs Repository • Decision to retain Eprints, based on • its high visibility and ranking • a commitment to long-term preservation • Eprints accepts a wide variety of content • i.e. can accept things that RSO do not want in Portal • the portal is untested as yet
CRIS vs Repository • Fundamental differences • Portal is the ‘human face’ of Lancaster research • Portal enables connections between researchers • Repository is about open access to research • i.e. full text
It’s about the data • Sources for Pure • human resources: ResourceLink • finance: Agresso • grants: pFACT • publications: Eprints and LUMS • profiles: faculty Web pages
Data Matching • Export from Eprints and LUMS • Atira developed algorithm to match authors to HR • mostly successful • 1000s of unmatched authors • most of them external • some miss-matched authors
Data Tidying • Who does this? • the author knows best? • authors allowed to edit • Library has the ‘validation’ role • Library enriches the data • it’s an ongoing task, now part of business as usual
Workflow • Atira developed a connector for Eprints • publications added to Pure go into a buffer awaiting validation • simultaneously they are sent into the Eprints buffer • once validated in Pure they are made live on Eprints • any further edits in Pure are reflected in Eprints
Future Developments • Author matching • Thomson Reuters unique author IDs • Elsevier offer similar service • REF Module • implemented and in use by the RSO • Virtualisation • Eprints now on virtual platform