UKSG Conference 2017 Breakout - Release 5 of the COUNTER Code of Practice - Tasha Mellins-Cohen and Lorraine Estelle
•Download as PPTX, PDF•
1 like•562 views
Release 5 of the COUNTER Code of Practice aims to simplify usage reporting standards through consistency, clarity, simplification, and continuous maintenance. It seeks to address evolving needs while reducing complexity. Key changes in Release 5 include reducing metric types, simplifying reports and attributes, implementing a RESTful API, and addressing community feedback. Release 5 is currently in draft form and public comment is encouraged.
Recommended
Recommended
More Related Content
Similar to UKSG Conference 2017 Breakout - Release 5 of the COUNTER Code of Practice - Tasha Mellins-Cohen and Lorraine Estelle
Similar to UKSG Conference 2017 Breakout - Release 5 of the COUNTER Code of Practice - Tasha Mellins-Cohen and Lorraine Estelle (20)
More from UKSG: connecting the knowledge community
More from UKSG: connecting the knowledge community (20)
Recently uploaded
Recently uploaded (20)
UKSG Conference 2017 Breakout - Release 5 of the COUNTER Code of Practice - Tasha Mellins-Cohen and Lorraine Estelle
- 1. Release 5 “consistency, clarity, simplification and continuous maintenance”
- 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
- 3. Release 5 Objective for Release 5 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
- 4. Release 5 COUNTER Release 5: Proposed List of Reports PLATFORM TITLE ITEM Platform Report 1 Usage by Month and Platform Expanded Platform Report Activity by Month and Platform Database Report 1 Usage by Month and Database Database Report 2 Access Denied by Month and Database Expanded Database Report Activity by Month and Database Journal Title Report 1 Usage by Month and Journal Title Journal Title Report 2 Access Denied by Month and Journal Book Title Report 1 Usage by Month and Book Title Book Title Report 2 Access Denied by Month and Book Expanded Title Report Activity by Month and Title Expanded Item Report Activity by Month and Item DATABASE
- 5. Release 5 R5’s Simplified Metric Types & Related Attributes Simplicity and Clarity
- 6. Release 5 COUNTER Release 5: 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
- 7. Release 5 COUNTER Release 5: 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
- 8. Release 5 Additional Attributes • Data Type • Section Type • Access Type • Access Method • Is_Archive • Year of Publication • Metric Type These can be used in combination to break out usage details
- 9. Release 5 COUNTER Release 5: Data Types Data_Type • Book • Database • Dataset • Journal • Multimedia • Platform • Repository Item Data_Type identifies the general type of content being accessed or for which usage is being reported. This attribute is used when defining Book Reports and Journal Reports and is an optional parameter for the Expanded Title Reports and can be used to generate summaries in an Expanded Database Report or an Expanded Platform Report.
- 10. Release 5 COUNTER Release 5: Section Types Section_Type • Article • Book • Chapter • 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 Expanded Title Reports.
- 11. Release 5 COUNTER Release 5: 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 appears in Journal Title Report 1 and allows usage of open access content to be separated from content that requires a license. OA_Delayed is access to content that became open access after an embargo period had expired. * Separate values of “OA_Gold_APC” and “OA_Gold_Non_APC” in original proposal have been simplified to just “OA_Gold” due to complexity required to implement the separate values.
- 12. Release 5 COUNTER Release 5: 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 in the Expanded Title Report. TDM usage is excluded from the standard Journal and Book reports.
- 13. Release 5 COUNTER Release 5: Year of Publication Is_Archive • 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 the print will be used. This attribute appears as an attribute in Journal Title Report 2 as well as both Book Reports and as an optional parameter in the Expanded Title Report.
- 14. Release 5 R5’s Simplified Report Formats Simplicity and Clarity
- 15. Release 5 COUNTER Release 4: 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
- 16. Release 5 COUNTER Release 5: Report Formats
- 17. Release 5 COUNTER Release 5: Report Formats
- 18. Release 5 COUNTER Release 5: Report Formats
- 19. Release 5 COUNTER_SUSHI for Release 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
- 20. Release 5 Addressing Community Feedback
- 21. Release 5 Amendments to remove implementation challenges • Is_Archive will be eliminated • OA_Gold_Non_APC will be eliminated • Other_Free_To_Read will not apply to publishers (only IRs). • OA_Delayed will be included in R5 but designated as "reserved for future use " and to be introduced at some future time given the complexity for implementation • Reports will be longer. We are looking how to limit standard views (reports) to just those metric types and attributes need for the intended purpose. This will keep the row count lower.
- 22. Release 5 Noting where clarification and guidance is required • The new metrics Investigations and Requests are not yet well understood • Concern about HTML and PDF • Creating examples with real data on how unique item requests may impact cost per use analysis. • The example data will be to inform both librarians and publishers on the effects of these new metrics. • The COUNTER requirement of keeping R4 reports available through the first year of will provide ability to compare results and get used to the change in metrics.
- 23. Release 5 Things we cannot directly address • Sessions • modern interfaces make sessions hard to capture • Can the report header on a separate tab? • Larger reports downloaded as TSV, there are no tabs • Excel and Google Sheets allows users to “Freeze” the header row
- 24. Release 5 New approaches • Concerns about 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 • Journal Title Report 5 considered as critical for library decision-making • Year of Publication allows libraries interpret the data for packages
- 25. Release 5 New approaches • Consortium Reports • Due to size, creating and consuming Release 4 consortium reports was not always possible • COUNTER is committed to Open Source tools that can fetch all member usage through a single call
- 26. Release 5 Project timeline Support Guide Encourage Jul 2017 – 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
- 27. Release 5 We want your feedback The Draft Code of Practice is available online at: https://www.projectcounter.org/counter-release-5-code-practice/ http://www.usus.org.uk/counter-release-5-draft-code-of-practice-is-live/ Please review the Code of Practice, complete the survey and provide any feedback by Easter! We will use your feedback to inform the final version of Release 5 and to help develop opportunities for education and communication More information can be found on the COUNTER website https://www.projectcounter.org/ and the Usus website http://www.usus.org.uk/
Editor's Notes
- 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.
- 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.
- Note that at the time of this presentation the list of reports is under review with the potential of adding one or two more “Title Reports” to meet specific reporting needs. The working groups is also considering more descriptive names for the reports to better articulate what they represent…
- Lets talk about metric types and related attributes
- 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.
- 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.
- 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.
- Data types are captured to reflect the nature of the material being used.
- Section type helps with measuring book usage by indicating if the unit of content delivered as an article, chapter, section or the entire book.
- 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…
- 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.
- And, Year of Publication is captured as an attribute to allow more flexible reporting that what was offered in Journal Report 5.
- Lets talk about metric types and related attributes
- I Journal Report 1, HTML and PDF usage is broken out, but only as totals… the SUSHI version has these figures broken out by month.
- 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 esier 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.
- The details of the report are consistent across reports.
- The terminology used in reports is the same across reports and between the spreadsheet and SUSHI version.
- 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.
- Lets talk about metric types and related attributes
- 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.
- Here is a link to a site where you can get access to the draft code of practice as well as a survey for providing feedback. Please review, and please provide feedback – hearing from the community that creates and uses COUNTER reports is important.