1. The HIRMEOS Metrics Services
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731102
The HIRMEOS Metrics Services
Metrics and Altmetrics for Open Access Monographs
January 2019, Paris 1

2. Summary Why collecting metrics?
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731102
Summary
Why collecting metrics?
Main intricacies in metrics collection for monographs
OA Metrics Service
Open Standard
Information about implementation 2

3. Why collecting metrics​?
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731102
Why collecting metrics​?
Authors want to know if others find their research useful
Publishers want to know if their books are being read
Platforms want to know if people like their service
Funding bodies want to asses where to put their money on
Usage metrics have been widely adopted in Open Access works as an indication of the popularity or acceptance of a particular publication. Innevitably, performance assesment and funding allocation is being based on these statistics, making
metrics collection and reporting a fundamental need for any organisation producing and/or hosting digital monographs. 3

4. Main intricacies collecting metrics for monographs
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Main intricacies collecting metrics for monographs
Localisation
Identification
Usage
Format
Where are books located
How are books identified
How is usage measured
How we obtain the data 4

5. Main intricacies collecting metrics for monographs
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Main intricacies collecting metrics for monographs
Localisation: dissemination across multiple platforms.
Identification
Usage
Format
You may think: we know where our books are, we host them.
OA Anyone can go to our website, download one of our books, upload it anywhere else, without neither the author nor ourselves knowing about it. This is great for sharing knowledge, but a nightmare to collect usage statistics. 5

6. Main intricacies collecting metrics for monographs
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Main intricacies collecting metrics for monographs
Localisation: dissemination across multiple platforms.
Identification: each platform use a different ID
Usage
Format
Assume we have located our books in all these platforms, and that the platform provides us with usage reports generated by them. These reports contain any random identifier the platform chose to use (ISBN, DOI), and most of the commonly used identifiers do not identify a book. Even the title!! 6

7. Main intricacies collecting metrics for monographs
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Main intricacies collecting metrics for monographs
Localisation: dissemination across multiple platforms.
Identification: each platform use a different ID
Usage: different measuring mechanisms used
Format
Then each platform measures different things, some report number of views, others sessions, etc. 7

8. Main intricacies collecting metrics for monographs
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Main intricacies collecting metrics for monographs
Localisation: dissemination across multiple platforms.
Identification: each platform use a different ID
Usage: different measuring mechanisms used
Format: data is inconsistently reported back to authors/publishers.
And then how do we get these statistics. Clearly we want to process them with a computer, automatically, seamlesly; and clearly this is 2019 so we don’t need to worry about any of this, it’s all programmatically solved. Well guess what? Most platforms send us a spreadsheet via (spam folder). 8

9. OA Metrics Service: what does it (and doesn’t) solve?
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
OA Metrics Service: what does it (and doesn’t) solve?
Localisation
Identification: Identifier Translation Service
Usage*
Format: Drivers
* usage: it doesn’t impose a unique measure, but it does solve storing the data 9

10. OA Metrics Service: Drivers
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
OA Metrics Service: Drivers
Drivers run locally, within the publisher/platform environment.
Independent, modules (one per platform metrics are collected from).
Collect metrics and submit them to the metrics database via API.
Can be used by:
Publishers: to submit data from a third party platform hosting their books.
Platforms: to submit data from their own system.
Use the Identifier Translation Service for URI resolution. 10

11. OA Metrics Service: Drivers
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
OA Metrics Service: Drivers
Google Analytics*
Matomo*
Access Logs*
Google Books
OAPEN
Open Edition
JSTOR
World Reader
Classics Library
Unglue.it
OpenAIRE
IRUS-UK
Wikimedia
Drivers may be used as a template to develop more drivers. There is a finite ways in which data can be collected, e.g. via API, CSV report, scraping.
GA, Downloads, Matomo, may be used by platforms to collect their own data; others are third-party. 11

12. OA Metrics Service: Identifier Translation Service
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
OA Metrics Service: Identifier Translation Service
Runs locally, within the publisher/platform environment.
Translates book URIs to a preferred scheme (e.g. DOI).
Uses a database of book metadata from:
Publisher/platform
Crossref
Can be integrated into an existing system (e.g. OMP) via API; or
it can be controlled using a web-based interface.
Essentially equal to “find the DOI of a monograph associated to this ISBN”, or “find all ISBNs associated with this URL” 12

13. This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031 13

14. This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031 14

15. Open Standard Book ID (URI) Country (nullable) Timestamp Measure
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Open Standard
Book ID (URI)
Country (nullable)
Timestamp
Measure
Platform (e.g. Google Books, Open Edition, OBP HTML Reader)
Type (e.g. Session, Download, Page View, Sale)
Namespace (e.g. metrics.operas-eu.org)
Version (e.g. v1, v2)
The measure could be defined by just its platform and type (e.g. Google Books page views), however, users may (and will) have discrepancies towards whether platform A’s page views can be aggregated to platform B’s.
Therefore we are adding the flexibility for any implementing platform to define their aggregation methodology (which must be documented properly) and store their data under a particular namespace; if a namespace is contributed to by many (e.g. operas), then all uploaders should have to agree on the type of data that can be aggregated. 15

16. Open Standard: Identification
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Open Standard: Identification
e.g. info:doi: /OBP0001
e.g. urn:isbn:
We’ve decided to allow any identifier users may want (or need) to use, through the use of URIs - any existing (and future) identifier can be expressed in URI notation, not just books’, but any type of document: images, audio, chapters, data, etc.
Standard defined by IETF 16

17. Open Standard: Event in JSON format
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Open Standard: Event in JSON format {
"uri": "info:doi: /obp.0001",
"measure": "metrics.operas-eu.org/obp-html/sessions/v1",
"value": 3,
"timestamp": " T00:00: ",
"country": "urn:iso:std:3166:-2:FR" }
Explain measure 17

18. Open Standard: Events in CSV format
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Open Standard: Events in CSV format 18

19. Open Standard: Measures
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Open Standard: Measures 19

20. This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031 20

21. Information about implementation
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Information about implementation
The measure could be defined by just its platform and type (e.g. Google Books page views), however, users may (and will) have discrepancies towards whether platform A’s page views can be aggregated to platform B’s.
Therefore we are adding the flexibility for any implementing platform to define their aggregation methodology (which must be documented properly) and store their data under a particular namespace; if a namespace is contributed to by many (e.g. operas), then all uploaders should have to agree on the type of data that can be aggregated. 21

22. Thank you for your attention.
This project has received funding from the European Union‘s Horizon 2020 research and innovation programme under grant agreement No731031
Thank you for your attention. 22