3.1 COUNTER Reports for Libraries¶
Reports for R5 consist of four Master Reports that allow the librarian to filter and configure to create customized views of their usage data. R5 also specifies Standard Views (pre-set filters/configuration).
To achieve compliance, a content provider MUST offer the Master Reports and Standard Views that are applicable to their Host_Types, with the exception of Standard Views that always would be empty (e.g. an Access Denied Standard View if denials cannot occur). An independent audit is required for these reports.
Content providers may offer additional Master Reports and Standard Views not required for compliance or custom reports (see Section 11.2), according to the rules set for the reports by the Code of Practice. For these reports an audit isn’t required.
3.1.1 Master Reports¶
Master Reports include all relevant metrics and attributes; they are intended to be customizable through the application of filters and other configuration options, allowing librarians to create a report specific to their needs. The four Master Reports are shown in Table 3.a along with their Report_ID, Report_Name and Host_Types who are REQUIRED to provide these reports. See Section 3.3.1 below for details on Host_Types.
Table 3.a (below): Master Reports
Report_ID |
Report_Name |
Details |
Host_Types |
|---|---|---|---|
PR |
Platform Master Report |
A customizable report summarizing activity across a content provider’s platforms that allows the user to apply filters and select other configuration options. |
All Host_Types: |
DR |
Database Master Report |
A customizable report detailing activity by database that allows the user to apply filters and select other configuration options. |
A&I_Database |
TR |
Title Master Report |
A customizable report detailing activity at the title level (journal, book, etc.) that allows the user to apply filters and select other configuration options. |
Aggregated_Full_Content |
IR |
Item Master Report |
A granular, customizable report showing activity at the level of the item (article, chapter, media object, etc.) that allows the user to apply filters and select other configuration options. |
Data_Repository* |
* Data repositories may choose to conform to the Code of Practice Release 5 or, alternatively, may wish to work with the Code of Practice for Research Data.
Figure 3.a (below) provides an example of how the user interface could look. The user will be presented with an interface that allows them to select usage dates, one or more Metric_Types, Data_Types, Access_Types, etc. and indicate if the filter columns are to be included. Including the column will cause usage to be broken out by individual values for the selected filter, whereas not including the column will result in usage being summarized for the selected filter.
Figure 3.a: Example of a user interface
3.1.2 Standard Views¶
The goal of Standard Views is to provide a set of pre-filtered views of the Master Reports covering the most common set of library needs. Report_IDs for Standard Views are derived from the Report_ID of the Master Report that they are based on. The format is {Master Report_ID}_{View ID}.
3.1.2.1 Platform Usage Standard Views¶
The Platform Usage Standard Views are derived from the Platform Master Report and provide a summary of activity on a given platform to support the evaluation of platforms and to provide high-level statistical data to support surveys and reporting to funders.
Table 3.b (below): Platform Usage Standard Views
Report_ID |
Report_Name |
Details |
Host_Types |
|---|---|---|---|
PR_P1 |
Platform Usage |
Platform-level usage summarized by Metric_Type. |
All Host_Types: |
*Data repositories may choose to conform to the Code of Practice Release 5 or, alternatively, may wish to work with the Code of Practice for Research Data.
See Section 4.1 below for details on Platform Usage Reports.
3.1.2.2 Database Usage Standard Views¶
The Database Usage Standard Views support the evaluation of the value of a given database of resources (e.g. a full-text database, an A&I database, or a multimedia collection).
Table 3.c (below): Database Usage Standard Views
Report_ID |
Report_Name |
Details |
Host_Types |
|---|---|---|---|
DR_D1 |
Database Search and Item Usage |
Reports on key Searches, Investigations and Requests metrics needed to evaluate a database. |
A&I_Database |
DR_D2 |
Database Access Denied |
Reports on Access Denied activity for databases where users were denied access because simultaneous-use licenses were exceeded or their institution did not have a license for the database. |
A&I_Database |
See Section 4.2 below for details on Database Usage Reports.
3.1.2.3 Title Usage Standard Views¶
Title Usage Standard Views are used to support the evaluation of the value of a given serial (e.g. journal, magazine, or newspaper) or monograph (e.g. book, eBook, textbook, or reference work) title.
Table 3.d (below): Title Usage Standard Views
Report_ID |
Report_Name |
Details |
Host_Types |
|---|---|---|---|
TR_B1 |
Book Requests (Excluding OA_Gold) |
Reports on full-text activity for books, excluding Gold Open Access content, as Total_Item_Requests and Unique_Title_Requests. The Unique_Title_Requests provides comparable usage across book platforms. The Total_Item_Requests shows overall activity; however, numbers between sites will vary significantly based on how the content is delivered (e.g. delivered as a complete book or by chapter). |
Aggregated_Full_Content |
TR_B2 |
Book Access Denied |
Reports on Access Denied activity for books where users were denied access because simultaneous-use licenses were exceeded or their institution did not have a license for the book. |
Aggregated_Full_Content |
TR_B3 |
Book Usage by Access Type |
Reports on book usage showing all applicable Metric_Types broken down by Access_Type. |
Aggregated_Full_Content |
TR_J1 |
Journal Requests (Excluding OA_Gold) |
Reports on usage of journal content, excluding Gold Open Access content, as Total_Item_Requests and Unique_Item_Requests. The Unique_Item_Requests provides comparable usage across journal platforms by reducing the inflationary effect that occurs when an HTML full text automatically displays and the user then accesses the PDF version. The Total_Item_Requests shows overall activity. |
Aggregated_Full_Content |
TR_J2 |
Journal Access Denied |
Reports on Access Denied activity for journal content where users were denied access because simultaneous-use licenses were exceeded or their institution did not have a license for the title. |
Aggregated_Full_Content |
TR_J3 |
Journal Usage by Access Type |
Reports on usage of journal content for all Metric_Types broken down by Access_Type. |
Aggregated_Full_Content |
TR_J4 |
Journal Requests by YOP (Excluding OA_Gold) |
Breaks down the usage of journal content, excluding Gold Open Access content, by year of publication (YOP), providing counts for the Metric_Types Total_Item_Requests and Unique_Item_Requests. Provides the details necessary to analyze usage of content in backfiles or covered by perpetual access agreements. Note that COUNTER reports do not provide access model or perpetual access rights details. |
Aggregated_Full_Content |
See Section 4.3 below for details on Title Usage Standard Views.
3.1.2.4 Item Usage Standard Views¶
The Standard Views for item-level reporting are designed to support the most common reporting needs. The Standard View for repositories (Journal Article Requests) provides insight into the usage of individual journal articles. The Standard View for multimedia (Multimedia Item Requests) allows evaluation of multimedia at the title level.
Table 3.e (below): Item Usage Standard Views
Report_ID |
Report_Name |
Details |
Host_Types |
|---|---|---|---|
IR_A1 |
Journal Article Requests |
Reports on journal article requests at the article level. This report is limited to content with a Data_Type of Article, Parent_Data_Type of Journal, and Metric_Types of Total_Item_Requests and Unique_Item_Requests. This Standard View must be provided only if (a) it is clear for all articles in IR whether they are journal articles or not and (b) the parent item is known for all journal articles. |
Repository |
IR_M1 |
Multimedia Item Requests |
Reports on multimedia requests at the item level. |
Multimedia |
See Section 4.4 below for details on Item Usage Reports.