Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,546
On Slideshare
0
From Embeds
0
Number of Embeds
4

Actions

Shares
Downloads
9
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • RepNet = Infrastructure support for UK IRs funded by Jisc Very much a collaborative development – for & of the community IRUS-UK – same team who brought you JUSP
  • Won’t go into PIRUS2 – was well publicised when completed - see project web site Google ‘PIRUS’, need to add ‘JISC’ otherwise connect to LA street gang information re Bloods (Found out before any merchandising got created – red t-shirt, etc Not resp for Street gang member/Usage Stats geek tragedy) Took the P out of PIRUS
  • National or other aggrgate level. Benchmarking/profiling/reporting Reduce duplicated effort!
  • Drew on expertise of involvement with: Knowledge Exchange w/shops & recommendations Drew on: MESUR project especially (Bollen & van de Sempel) Kept ‘pushed data’ to minimum Dspace patches – @Mire, Belgium (v1.8, v3.*) ePrints – Tim Brody, Soton (v 3.*) Fedora – coding required at each IR (Ben O’Steen wrote daemon & implemented for Oxford University as part of PIRUS2)
  • Any questions?
  • Just send Id & some other data agreed in KE guidelines. URL_VER: OpenURL standard URL_TIM: Timestamp REQ_ID: Client IP REQ_DAT: User Agent RFT_ARTNUM: Object Id SVC_FORMAT: MIME type RFR_ID: Source IR
  • 3 Step process – (‘Gimme 3 Steps’ Lynryd Skynryd) Step 3 can include finding DOI from CrossRef & providing to IR to supplement metadata – loads of other possibilities for IR metadata enrichment. (In spirit of Hitchikers Guide to the Universe) There is a Step 4 every month to package-up into familiar time slice.
  • Aim to get 50 -75 Irs by end July 2013. COUNTER web site PIRUS CoP Release 1 For Recording & Reporting Usage at Individual Article Level. Public comment from Feb-April 2013

Transcript

  • 1. Making scholarly statistics count in UK repositoriesRoss MacIntyre, Mimas, The University of Manchester UKSG Conference April 2013
  • 2. IRUS-UK Funded by Jisc as part of UK RepositoryNet+ Led by Mimas Primary Project Team Members:  Mimas, The University of Manchester  Cranfield University  EvidenceBase, Birmingham City University IRUS-UK: Institutional Repository Usage Statistics - UK irus.mimas.ac.uk
  • 3. IRUS-UK: history Emerged as an outcome of PIRUS2  Publisher and Institution Repository Usage Statistics project  http://www.cranfieldlibrary.cranfield.ac.uk/pirus2/  Aimed to develop a global standard to enable the recording, reporting and consolidation of online usage statistics for individual journal articles hosted by Institutional Repositories, Publishers and others  Proved it was *technically feasible*, but …  However, crisis/opportunity… we now knew it was possible to… irus.mimas.ac.uk
  • 4. IRUS-UK: aim Enable UK IRs to share/expose usage statistics based on a global standard – COUNTER  Produced on the same basis as publishers  Filtered to remove robots and double clicks  Comparable  Reliable  Trustworthy  Authoritative irus.mimas.ac.uk
  • 5. IRUS-UK: objectives Collect raw usage data from UK IRs for *all item types* within repositories  Downloads not record views  Not just articles Process those raw data into COUNTER-compliant statistics Return those statistics back to the originating repositories for their own use Give Jisc (and others) a nation-wide picture of the overall use of UK repositories  demonstrate their value and place in the dissemination of scholarly outputs Offer opportunities for benchmarking Act as an intermediary between UK repositories and other agencies  e.g. global central clearinghouse, national shared services, OpenAIRE irus.mimas.ac.uk
  • 6. IRUS-UK: gathering data Considered 2 scenarios for gathering data  ‘Tracker’ code  a server-side ‘Google Analytics’ for item downloads  Pushes metadata to a third-party server as OpenURL Key/Value strings  OAI-PMH harvesting  Used to by third parties to ‘pull’ metadata from repositories  Repurposed to expose usage events as OpenURL Context Objects Opted for the Tracker  Just easier  Plugins/patches available for DSpace and Eprints  Implementation guidelines for Fedora irus.mimas.ac.uk
  • 7. IRUS-UK: gathering data What does the tracker actually send to IRUS-UK when a download happens?  http://www.jusp.mimas.ac.uk/counter/?url_ver=Z39.88- 2004&url_tim=2012-07-05T22%3A59%3A59Z&req_id=urn %3Aip%3A86.15.47.114&req_dat=Mozilla%2F5.0+(iPhone %3B+U%3B+CPU+iPhone+OS+5_1_1+like+Mac+OS+X %3B+en-us)+AppleWebKit%2F534.46.0+(KHTML %2C+like+Gecko)+CriOS%2F19.0.1084.60+Mobile %2F9B208+Safari%2F7534.48.3&rft.artnum=oai %3Aeprints.hud.ac.uk%3A8795&svc_format=application %2Fpdf&rfr_id=eprints.hud.ac.uk irus.mimas.ac.uk
  • 8. IRUS-UK: Tracker OpenURL strings The OpenURL key/value pairs  url_ver=Z39.88-2004  url_tim=2012-07-05T22%3A59%3A59Z  req_id=urn%3Aip%3A86.15.47.114  req_dat=Mozilla%2F5.0+(iPhone%3B+U %3B+CPU+iPhone+OS+5_1_1+like+Mac+OS+X%3B+en-us) +AppleWebKit%2F534.46.0+(KHTML%2C+like+Gecko)+CriOS %2F19.0.1084.60+Mobile%2F9B208+Safari%2F7534.48.3  rft.artnum=oai%3Aeprints.hud.ac.uk%3A8795  svc_format=application%2Fpdf  rfr_id=eprints.hud.ac.uk irus.mimas.ac.uk
  • 9. IRUS-UK: processing data Logs are processed daily Step 1: Perl script parses the logs  Processes entries from recognised IRs  Sorts and filters entries following COUNTER rules  Consolidates daily accesses for each item  Outputs to intermediate file Step 2: Perl script parses intermediate file  Looks up each item in the IRUS DB  If item is unknown to the system add item with (most) metadata “unknown”  Updates DB with new statistics (for both ‘known’ & ‘known unknowns’) Step 3: Obtain “unknown” metadata  For the ‘known unknowns’ uses an OAI GetRecord to retrieve  Updates the metadata to DB irus.mimas.ac.uk
  • 10. IRUS-UK: Overall Summary irus.mimas.ac.uk
  • 11. IRUS-UK: Repository Totals irus.mimas.ac.uk
  • 12. IRUS-UK: Item Types Totals irus.mimas.ac.uk
  • 13. IRUS-UK: Item Type <->IR: Item Type irus.mimas.ac.uk
  • 14. IRUS-UK: DOI Summary Stats irus.mimas.ac.uk
  • 15. IRUS-UK: Title/Author Search irus.mimas.ac.uk
  • 16. IRUS-UK: Ingest Summary Stats irus.mimas.ac.uk
  • 17. IRUS-UK: IR1 Report LSE Jan-Feb 2013 irus.mimas.ac.uk
  • 18. IRUS-UK: CAR1 Report Jan-Feb 2013 irus.mimas.ac.uk
  • 19. IRUS-UK: Exposing statistics Through the User Interface - The Portal Various reports are available to Institutions  For humans, downloads as CSV/Excel spreadsheet files  Monthly and daily granularity  For machines, harvesting via SUSHI  Monthly granularity Usage statistics for incorporation into Repositories  Via an API/Web Service  Initial version in place  Further requirements to be determined irus.mimas.ac.uk
  • 20. IRUS-UK: where we are now Pioneering sites sending data to IRUS include:  ePrints: Bournemouth, City, UEA, Greenwich, Huddersfield, LSE, NERC, Northumbria, Open, Reading, Salford, Sussex, Warwick  DSpace: Aberystwyth, Cranfield, RGU  Others in the pipeline We’re working on:  Ingest scripts  Portal UI – basic until informed choices can be made  Spreading the word about IRUS irus.mimas.ac.uk
  • 21. IRUS-UK: next steps More of what we’re already doing… Community Engagement  Getting more IRs on-board  Defining and evaluating user requirements  including surveys, interviews, monitoring feedback, etc. Processes to support  institutional liaison, data collection, monitoring and responding to future requirements, ensuring interoperability  development and production environments including monitoring, back-up, authentication and archiving polices and processes Formal application for COUNTER-compliance irus.mimas.ac.uk
  • 22. IRUS-UK: future webinars IRUS-UK is planning to run more webinars:  17 April 14.00 – aimed primarily at repository managers  22 May 14.00 – aimed primarily at repository technical managers  17 July 14.00 – end of project webinar More details to follow irus.mimas.ac.uk
  • 23. Contacts & Information For general enquiries, please contact  support@repositorynet.ac.uk If you are a UK repository wishing to participate in IRUS-UK, please contact  irus@mimas.ac.uk Project web site:  http://www.irus.mimas.ac.uk/ Thank you! irus.mimas.ac.uk