Downloaded 14 times
Uploaded byNASIG
Release 5 of the COUNTER Code of Practice
COUNTER Release 5 aims to simplify usage statistics reporting. It reduces the number of metric types and eliminates format-specific metrics. Release 5 introduces four master reports - Platform, Database, Title, and Item. It also defines standard views to address common use cases. Feedback on the initial draft has led to amendments to address implementation challenges. The new draft provides additional clarification and guidance. The project timeline is outlined, with the code of practice now available for consultation online.
More Related Content
![[SharePoint Korea Conference 2013 / 김승진] Share point 2013 검색 개발 방법](https://cdn.slidesharecdn.com/ss_thumbnails/sharepoint2013-130724092303-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Release 5 of the COUNTER Code of Practice
Release 5 of the COUNTER Code of Practice
- 1. Release 5 “consistency, clarity, simplificationand continuous maintenance” NASIG Conference June 11 2017 @pearsosz @ProjectCounter
- 2. Release 5 Why COUNTER Release 5 •Current Code of Practice is complex • Inconsistencies in reports, metric types and formats • Needs have evolved and continue to evolve @pearsosz @ProjectCounter
- 3. Release 5 Objective for Release5 Seek the balance between addressing changing needs and reducing the complexity of the Code of Practice to ensure that all publishers and content providers are able to achieve compliance @pearsosz @ProjectCounter
- 4. Release 5 Four Master Reportsare the Foundation of COUNTER R5 Reports Platform Master Report Database Master Report Title Master Report Item Master Report @pearsosz @ProjectCounter
- 5. Release 5 Master Reports canbe Filtered and Configured to Tailor Analysis For illustrative purposes only @pearsosz @ProjectCounter
- 6. Release 5 “Standard Views” Addressthe Most Common Use Cases Platform Master Report Platform Usage Database Master Report Database Search and Item Usage Database Access Denied Title Master Report Book Requests (Excluding OA_Gold) Book Access Denied Book Usage by Access Type Journal Requests (Excluding OA_Gold) Journal Access Denied Journal Usage by Access Type Journal Requests by YOP (Excluding OA_Gold) Item Master Report Journal Article Requests Multimedia Item Requests @pearsosz @ProjectCounter
- 7. Release 5 Platform MasterReport Platform Usage Database Master Report Database Search and Item Usage Database Access Denied Title Master Report Book Requests (Excluding OA_Gold) Book Access Denied Book Usage by Access Type Journal Requests (Excluding OA_Gold) Journal Access Denied Journal Usage by Access Type Journal Requests by YOP (Excluding OA_Gold) Item Master Report Journal Article Requests Multimedia Item Requests Analyze database performance with searches, and activity related to abstracts and full text “Standard Views” Address the Most Common Use Cases @pearsosz @ProjectCounter
- 8. Release 5 Platform MasterReport Platform Usage Database Master Report Database Search and Item Usage Database Access Denied Title Master Report Book Requests (Excluding OA_Gold) Book Access Denied Book Usage by Access Type Journal Requests (Excluding OA_Gold) Journal Access Denied Journal Usage by Access Type Journal Requests by YOP (Excluding OA_Gold) Item Master Report Journal Article Requests Multimedia Item Requests Comparable usage of acquired books, regardless of how those books are delivered. “Standard Views” Address the Most Common Use Cases @pearsosz @ProjectCounter
- 9. Release 5 Platform MasterReport Platform Usage Database Master Report Database Search and Item Usage Database Access Denied Title Master Report Book Requests (Excluding OA_Gold) Book Access Denied Book Usage by Access Type Journal Requests (Excluding OA_Gold) Journal Access Denied Journal Usage by Access Type Journal Requests by YOP (Excluding OA_Gold) Item Master Report Journal Article Requests Multimedia Item Requests Usage for subscribed journals supporting cost-per-use analysis “Standard Views” Address the Most Common Use Cases @pearsosz @ProjectCounter
- 10. Release 5 Platform MasterReport Platform Usage Database Master Report Database Search and Item Usage Database Access Denied Title Master Report Book Requests (Excluding OA_Gold) Book Access Denied Book Usage by Access Type Journal Requests (Excluding OA_Gold) Journal Access Denied Journal Usage by Access Type Journal Requests by YOP (Excluding OA_Gold) Item Master Report Journal Article Requests Multimedia Item Requests A closer look at subscribed journal usage for analysis by YOP “Standard Views” Address the Most Common Use Cases @pearsosz @ProjectCounter
- 11. Release 5 Platform MasterReport Platform Usage Database Master Report Database Search and Item Usage Database Access Denied Title Master Report Book Requests (Excluding OA_Gold) Book Access Denied Book Usage by Access Type Journal Requests (Excluding OA_Gold) Journal Access Denied Journal Usage by Access Type Journal Requests by YOP (Excluding OA_Gold) Item Master Report Journal Article Requests Multimedia Item Requests Analyze usage of multimedia content at the item level. “Standard Views” Address the Most Common Use Cases @pearsosz @ProjectCounter
- 12. Release 5 Example ofa Standard View for the Title Master Report @pearsosz @ProjectCounter
- 13. Release 5 Example ofa Standard View for the Title Master Report @pearsosz @ProjectCounter
- 14. Release 5 Example ofa Standard View for the Title Master Report @pearsosz @ProjectCounter
- 15. Release 5 Example ofa Standard View for the Title Master Report @pearsosz @ProjectCounter
- 16. Release 5 R5’s SimplifiedMetric Types & Related Attributes Simplicity and Clarity @pearsosz @ProjectCounter
- 17. Release 5 COUNTER Release5: Metric Types Release 4 • abstract • no_license • audio • other • data_set • podcast • ft_epub • record_view • ft_html • reference • ft_html_mobile • result_click • ft_pdf • search_fed • ft_pdf_mobile • search_reg • ft_ps • sectioned_html • ft_ps_mobile • toc • ft_total • turnaway • image • video • multimedia Release 5 • total_item_investigations • total_item_requests • unique_item_investigations • unique_item_requests • unique_title_investigations • unique_title_requests • searches_regular • searches_federated • searches_automated • searches_platform • no_license • limit_exceeded metric types in R4 reduced to in R5. Format-specific metrics eliminated! Item Database Platform Item @pearsosz @ProjectCounter
- 18. Release 5 COUNTER Release5: Metric Types Release • total_item_investigations • total_item_requests • unique_item_investigations • unique_item_requests • unique_title_investigations • unique_title_requests • searches_regular • searches_federated • searches_automated • searches_platform • no_license • limit_exceeded Investigations versus Requests… Item Database Platform Item View abstract Link to Link Resolver View cited references Link to ILL form View HTML full text View PDF View content… User Action View article preview @pearsosz @ProjectCounter
- 19. Release 5 Additional Attributes • DataType • Section Type • Access Type • Access Method • Year of Publication (YOP) These can be used in combination to break out usage details @pearsosz @ProjectCounter
- 20. Release 5 COUNTER Release5: Data Types Data_Type • Article • Book • Book Segment • Database • Dataset • Journal • Multimedia • Newspaper or Newsletter • Platform • Other • Repository Item • Report • Thesis or Dissertation Data_Type identifies the general type of content being accessed or for which usage is being reported. This attribute is used when creating Standard Views for Books and Journals and is an optional parameter for the Title Master Report and can be used to generate summaries in a Database Master Report or Platform Master Report. @pearsosz @ProjectCounter
- 21. Release 5 COUNTER Release5: Section Types Section_Type • Article • Book • Chapter • Other • Section Section_Type when content is delivered in “chunks” (sections) this describes what that section is, e.g. a book may be accessed by the chapter; content in a journal is accessed by article. This attribute is an optional parameter for the Title Master Report. @pearsosz @ProjectCounter
- 22. Release 5 COUNTER Release5: Access Types Access_Type • Controlled • OA_Delayed* (reserved for future use) • OA_Gold • Other_Free_to_Read (repositories only) Access_Type describes the nature of access control that was in place when the content item was accessed. This attribute is in filtering for Standard Views and Master Reports and is included in Book Usage by Access Type and Journal Usage by Access Type Standard Views. It’s primary role is to differential usage of gold open access content from content that requires a license. OA_Delayed is content that became open access after an embargo period had expired. * OA_Delayed is NOT part of the initial release of R5. It will be introduced at a future date (with sufficient advance notice) after further study. @pearsosz @ProjectCounter
- 23. Release 5 COUNTER Release5: Access Methods Access_Method • Regular • TDM Access_Method is an attribute indicating whether the usage related to investigations and requests was generated by a human user browsing and searching a website (“regular”) or by Text and Data Mining processes (TDM). This attribute appears as an optional parameter the Master Reports. TDM usage is excluded from the standard views for Journal and Book usage. @pearsosz @ProjectCounter
- 24. Release 5 COUNTER Release5: Year of Publication YOP • yyyy • 0001 (unknown) • 9999 (articles in press) YOP is the year of publication for the content item accessed. If content is available in print and online format and the publication dates of these two formats differ, the year of publication of version of record (normally the format that is published first) is used. YOP is an option attribute in Title Master Report, Database Master Report and Platform Master Report. It appears as a column in the Journal Requests by YOP (Excluding OA_Gold) Standard View. @pearsosz @ProjectCounter
- 25. Release 5 R5’s SimplifiedReport Formats Simplicity and Clarity @pearsosz @ProjectCounter
- 26. Release 5 COUNTER Release4: Report Formats Database Report breaks out usage by metric type. Journal (and book) reports don’t. Excel version of Journal Report 1 has totals for PDF and HTML, XML version breaks them out by month @pearsosz @ProjectCounter
- 27. Release 5 COUNTER Release5: Report Formats @pearsosz @ProjectCounter
- 28. Release 5 COUNTER Release5: Report Formats @pearsosz @ProjectCounter
- 29. Release 5 COUNTER Release5: Report Formats @pearsosz @ProjectCounter
- 30. Release 5 COUNTER_SUSHI forRelease 5 RESTful interface returning JSON- formatted reports Familiar to most web developers Allows retrieval of full reports, or snippets of usage Allows usage display to be embedded in other applications @pearsosz @ProjectCounter
- 31. Release 5 COUNTER_SUSHI for R5uses a URL to request the report https://jusp.jisc.ac.uk/api/sushi/counter/r5/reports/ tr_j1/?requestor_id=test&customer_id=test&platfor m=110&begin_date=2016-01&end_date=2016- 02&pretty=pretty @pearsosz @ProjectCounter
- 32. Release 5 COUNTER_SUSHI for R5responses are JSON @pearsosz @ProjectCounter
- 33. Release 5 COUNTER_SUSHI for R5responses are JSON @pearsosz @ProjectCounter
- 34. Release 5 COUNTER_SUSHI for R5responses are JSON @pearsosz @ProjectCounter
- 35. Release 5 COUNTER_SUSHI for R5responses are JSON @pearsosz @ProjectCounter
- 36. Release 5 Addressing CommunityFeedback on Draft 1 @pearsosz @ProjectCounter
- 37. Release 5 Amendments to Draft1 to remove implementation challenges • Is_Archive has be eliminated • OA_Gold_APC and OA_Gold_Non_APC have be eliminated in favor of “OA_Gold” • Other_Free_To_Read will not apply to publishers (only Repositories). • OA_Delayed will listed in R5 but designated as "reserved for future use" and to be introduced at some future time given the complexity for implementation • Standard Views specifically focused on library use cases have been introduced to address the potential that reports will be longer. @pearsosz @ProjectCounter
- 38. Release 5 Draft 2 includes additional clarification andguidance • The new metrics Investigations and Requests were a source of confusion and have been clarified with graphics and explanatory text. • Concern about HTML and PDF and the transition from R4 to R5 have been addressed through the inclusion of a section in the CoP that specifically addresses this issue and provide a mapping of R4 metrics and the R5 equivalents @pearsosz @ProjectCounter
- 39. Release 5 Things we cannotdirectly address • Sessions • modern interfaces make sessions hard to capture and somewhat inconsistent in their interpretation. • Output the report header to a separate tab • When reports are downloaded as TSV, there are no tabs • R5 reports have a blank row before the report body to making sorting and filtering operations and generating pivot tables painless (the header is not an issue) • Excel and Google Sheets allows users to “Freeze” the header row to make it easy to compensate @pearsosz @ProjectCounter
- 40. Release 5 New approaches • Concernsabout no reporting of zero usage • Not all publishers produce their COUNTER statistics from the same system they use to manage their access control • COUNTER is being represented on a new NISO initiative, currently referred to as KBART-Automation for SUSHI harvesting of BOTH usage and entitlements • R4’s Journal Title Report 5 considered as critical for library decision-making • The “Journal Requests (Non-Gold OA) by YOP” standard view provides the same information but with greater detail. @pearsosz @ProjectCounter
- 41. Release 5 New approaches • ConsortiumReports as Separate Reports • Due to size, creating and consuming R4 consortium reports was not always possible • Methods included in R5 simplify the retrieval of any R5 report for all consortium members • COUNTER is committed to facilitate development Open Source tools that will provide consortium administrators with the ability to generate consolidated usage reports for the consortium @pearsosz @ProjectCounter
- 42. Release 5 Project timeline Support Guide Encourage Jul2017 – Dec 2018 Post Publish Connect Jul 2017 Review Revise Improve Apr – Jun 2017 Consult Check Discuss Jan- Apr 2017 Conceive Design Develop Sep – Dec 2016 Jan 2019 @pearsosz @ProjectCounter
- 43. Release 5 Draft 2of Release 5 Now Available Online https://www.projectcounter.org/code-of-practice/counter-release-5-draft-code-practice-consultation/ http://www.usus.org.uk/draft-2-of-the-code-of-practice-release-5/ Webinars 15 June 2017 at 15:00:00 BST, 10:00:00 EDT, 16:00:00 CEST 17 July 2017 2PM ET (NASIG webinar) Mailing list COUNTER-R5@JISCMAIL.AC.UK @pearsosz @ProjectCounter
- 44. Release 5 Answers toquestions from session: • How is PPV usage reported in R5 against other access_types? • Articles accessed through payment of a pay-per-view fee or similar token-payment arrangement will be categorized under Access_Type = Controlled. • Since zero usage is not included in COUNTER reports, how does an institution determine entitlements that were not used? • Using a tool like Excel, load the list of entitlements in a spreadsheet and copy the COUNTER usage report from the same publisher in a separate worksheet. Use Excel’s “SumIF()” formula to add usage to the entitlement worksheet. Titles in the entitlements worksheet without usage have zero usage. Note that COUNTER is a co-sponsor of NISO’s KBART-Automation working group which is developing a recommended practice for publishers to provide a customer’s access entitlements in a KBART format. Publishers that implement the KBART-Automation initiative are expected to include the same proprietary identifiers for both access entitlements and COUNTER usage reports to ensure a natural and simple match-point between these two reports. • How does R5 improves book reporting comparisons at unique_title level to improve comparison between different platforms? • With R5, COUNTER addressed the fact that eBooks are delivered in different ways by different platforms by introducing the “unique_title_request” metric types. These metric types provide comparable metrics across platforms by counting the unique activity at the book level. If a book in Platform A is downloaded as a single PDF; and a book in Platform B Is downloaded as 10 separate chapters; each platform will reflect this activity as ONE unique_title_request. The new metric type effectively eliminates the way in which the book is delivered (whole book vs section vs chapter vs article) as a factor in comparable metrics. • How does COUNTER R5 differentiate between TDM usage and unauthorised downloads? • TDM only reflects authorized downloads for the purpose of text and data mining. The content provider will use various techniques to determine this, such as the use of a special API, the registration of a specific IP address, the use of a specific login, etc. Non-authorized TDM activity should be detected as unauthorized robot/crawler activity and should be ignored or may be treated as “regular” usage if the behaviour of the system downloading the content for text and data mining is similar to an end user. In short, text and data mining usage will only be captured as TDM usage if there is a prior arrangement with the content provider and an approved method of access is used. @pearsosz @ProjectCounter
Editor's Notes
- #2 Aim of this presentation is to provide a summary of Release 5 And to update you on the changes to draft 2 and timescale for implementation Also Q&A / feedback after the presentation
- #3 Previous codes of practices had evolved over the years. Reports were added to address specific needs. The resulting code is somewhat complex and has a lot of inconsistencies. Needs continue to change and the code of practice needs to keep up.
- #4 A main goal of Release 5 is to balance changing reporting needs with the need to make things simpler so that all content providers can achieve compliance and librarians can have usage statistics that is credible, consistent and comparable. This approach also allows for future proofing – making the COP more easily implementable and maintainable.
- #5 Firstly, Release 5 gets away from the notion of mandatory and optional reports. In rethinking reporting for R5 we have introduced four “Master Reports” – one for each level in which usage is reported. Librarians will be able to use the Master Report to customize their analysis to meet specific reporting needs.
- #6 Here is a mock-up of a reporting interface (for illustrative purposes only) in which the library staff would be able to report on title level usage by picking which metric types to show, limit to certain data types (e.g. books or journals) decide if they want usage for material under subscription (Access Type = Controlled), Gold Open Access or both; and be able to select a range of Year’s of publication.
- #7 While flexibility is great, it does offer challenges when comparability is desired; therefore, R5 goes further to define a series of “standard views” on the Master Reports. Standard Views address common use cases and are essentially a set of pre-defined attributes and filters for the corresponding Master Report.
- #13 Here we have the Standard View “Journal Requests (Excluding OA_Gold)
- #14 Here is a closer look at the header
- #15 And a closer look at the columns
- #16 And more columns…. We will discuss these in more detail later in this presentation – but this gives you a flavor of how R5 reports will look.
- #17 Lets talk about metric types and related attributes in more detail
- #18 Lets talk metric types. COUNTER R4 metric types are on the left and Release 5 on the right. We have eliminated format-specific metrics and reduced the number of metric types by half.
- #19 We are introducing a new vocabulary as well since we need metric types to be format-agnostic – i.e. A video is not “text” so full text is not appropriate. “Investigations” is a superset metric in that it counts all activity a user has for an item where an item is the unit of content accessed – ie. Article, chapter, etc. Users viewing a detailed record, clicking an OpenURL link, viewing the full text, are all considered “investigations”… Another way of looking at it is that “investigations” are an overall measure of the user’s interest in a content item. Metrics include total item investigations… plus unique_item investigations in which an article or chapter can only get credit for one action in a user session; and, unique title investigations – which applies mostly to books – where the title, or book gets only credit for one unique_title_investigation in a user session… This resolves the incompatibility between book report 1 and book report 2 in that it no longer matters how the book is delivered.
- #20 In order to offer the flexibility and depth or reporting, COUNTER R5 introduces a series of additional attributes that can be combined with the simplified set of metric types.
- #21 Data types are captured to reflect the nature of the material being used.
- #22 Section type helps with measuring book usage by indicating if the unit of content delivered as an article, chapter, section or the entire book.
- #23 Access types relate to the access control that was in place when the content was requested. Controlled means a license was required; OA_Gold means the content as available as Open Access because an article processing charge was paid; OA_Delayed is for content that became open access after an embargo period… Note that OA_Delayed will not be introduced until some future date.
- #24 Access Method was introduced to track regular usage separately from usage for the purpose of text and data mining. The latter may results in massive amounts of content being accessed and it can skew the stats. Separating this activity allow TDM usage to be measured and still be kept separate from regular usage.
- #25 And, Year of Publication is captured as an attribute to allow more flexible reporting that what was offered in Journal Report 5.
- #26 Lets talk about R5s simplified report formats
- #27 In R4 Journal Report 1, HTML and PDF usage is broken out, but only as totals… the SUSHI version has these figures broken out by month.
- #28 The headers for all reports would have the same exact format; and, this same information would appear in the SUSHI version. Yes, there are more rows, but this makes the report clearer and easier to process. Plus a blank row was added before the body of the report to make it easy add filtering and sorting in Excel and Google Sheets.
- #29 The details of the report are consistent across reports. While not all reports will have all the same column headings, when they do, the labels and column order will be consistent across reports.
- #30 The terminology used in reports is the same across reports and between the tabular and SUSHI version.
- #31 In release 5, the next version of SUSHI will be supported -- one which adopts a RESTful interface returning JSON-formatted usage. This is in line with modern web development; using approaches that are familiar to most web developers. And it offers a microservice approach that allows usage to be embedded in other applications.
- #32 Here is an example of a URL for the JUSP SUSHI Server for Release 5.
- #33 And here is the response.
- #34 You will notice familiar terms in the header.
- #35 Familiar details for the title
- #36 And familiar metric types… Essentially, COUNTER_SUSHI is retrieving the same report information, just in a different format… a format that is easy for developers of web applications to work with.
- #37 In this next section we will discuss some of the changes that were made to the initial draft of the R5 of the CoP. We received a lot of valuable feedback from all stakeholders. There were definitely some issues with the initial draft that would have made R5 very difficult to implement – we made several simplifications to address these issues.
- #39 Unique_item_requests attribute compared to total_item_requests accounts for the interface effect so you can see both together for comparison Unique_title metrics were introduced in R5 to help normalize eBook metrics. Since eBooks can be downloaded as an entire book in a single PDF or as separate chapters, the counts for R4’s BR1 (book downloads) and BR2 (section downloads) are not comparable. With the unique_title metrics, the book title’s unique_title metrics are only increased by one no matter how many chapters, sections or times they were accessed in a given user session. Unique_title metrics provide comparable eBook metrics regardless of the nature of the platform and how eBook content is delivered.
- #43 We started work early last year. We have developed the draft and are now well into the consultation phase. The goal is to incorporate feedback during the April through June timeframe, publish the final version this July and give content providers 18 months to implement. If all goes according to plan, Release 5 would go live in January 2019.
- #44 Here is a link to a site where you can get access to the draft code of practice. Update: COUNTER are currently writing friendly guides for release 5 – starting with the guide for content providers and a technical friendly guide. The library guide will follow. We have contracted a technical writer to ensure that the web presentation of R5 is easily navigable and usable by lots of different users of the COP. Also, we are implementing dated logos for COUNTER compliance which makes it really easy to know whether content providers are compliant and have been audited THERE IS A WEBINAR ON JUNE 15 WHICH COVERS THIS CONTENT FOR COLLEAGUES WHO HAVE NOT BEEN ABLE TO ATTEND – LINK TO WEBSITE Q&A - Including library use scenarios feedback