1. Metrics for Repository Impact Mark MacGillivray Cottage Labs http://cottagelabs.com

2. Who am I Co-founding partner, coder / manager. Developer / project manager on various projects, JISC and other funders. PhD student in the School of Informatics at the University of Edinburgh. Open Access, Biblio, Science working groups member at Open Knowledge Foundation.

3. What is Cottage Labs A core of developers working on software for higher education and research. Some of us are still affiliated with academic institutions, and we collaborate with many. Our goal is to help build the foundations of free and open access to scholarship. As information and software are now the key resources of our community, we should make our community self-sustaining by supporting open software development and open scholarship. With open licensing, we can share our software and data across our community.

4. What we do Software development, project management, report writing. ● Software infrastructure like SWORD ● Research infrastructure like dspace, DMP Online, Bibserver ● National infrastructure projects like DUO in Norway ● Identifiers report – recommendations on ORCID etc http://cottagelabs.com/projects

5. Collecting metrics - resources All information about the resources themselves is inherently available. As long as the information exists and can be delivered in a usable format... So depending on quality of record metadata, all resource information can be used for metrics. This means it is possible to do things like “list all books with more than ten views” - if we know which things are books.

6. Collecting metrics - usage Uploads / Downloads / Views ● Time – when did it happen? Useful for daily / monthly reports etc. ● Location – IP address leads to LatLong / country / city / institute. Learn where the audience is. ● How – device type, browser / OS configuration. How are people interacting with the resources?

7. Collecting metrics - users Less well defined – more interesting – higher risk (data protection?) ● Who is interested in a resource? ● What do they want it for? ● When do they want it? ● Do they care about copyright / access permissions? ● Do they circumvent them? If so, how?

8. Metrics - compliance ● COUNTER http://www.projectcounter.orghttp://www.projectcounter.org ● IRUS-UK - http://www.irus.mimas.ac.ukhttp://www.irus.mimas.ac.uk Collecting and using compliant metrics could result in standardised reports

9. Our approach Index the hell out of it... Using indexing engines rather than databases to present and cut data based on queries. Then build UI to automate complex queries. http://www.elasticsearch.org http://github.com/okfn/facetview

10. Recent work Total Impact / Impact Story http://impactstory.org Aggregates usage across various social media, and presents an overall score. Has an API, can be embedded in other apps.

11. Recent work XCRI-CAP course feed data. A current ongoing project... quite new. May or may not be interesting, will give a brief description.

12. Recent work Mimas Jorum http://test.cottagelabs.com/jorum A repository of repositories? A large collection of many Open Educational Resources. Undergoing heavy redevelopment.

13. Useful links http://uni-of-nottingham.adobeconnect.com/metrics/ http://www.rsp.ac.uk/help/publications/#webinars http://cottagelabs.com http://test.cottagelabs.com/jorum http://mimas.ac.uk http://www.jorum.ac.uk https://github.com/Mimas/jorum_rails/tree/stats https://github.com/CottageLabs/metadata-enhancement http://www.irus.mimas.ac.uk http://www.projectcounter.org http://impactstory.org http://swordapp.org http://www.elasticsearch.org