250 likes | 263 Views
Explore the foundation of COUNTER R5 reports standard and how metric types like Investigations & Requests can drive strategic decisions. Learn about Total Item Investigations, Unique Item Investigations, and more for effective decision-making.
E N D
Using Release 5 Usage Reports for strategic decision making UKSG 42nd Annual Conference Telford | 8-10 April 2019 Irene Barbers, Forschungszentrum Jülich
Four Master Reports are the Foundation of COUNTER R5 Reports
COUNTER Release 5: Metric Types Investigations & Requests Investigations report user actions related to a content item or title. Actions on part of an item or information about an item or the item itself are reported. Total_Item_Investigations the total number of times a content item or information related to a content item was accessed. Unique_Item_Investigations the number of unique content items investigated by a user in a session. Unique_Title _Investigations the number of unique titles investigated by a user in a session (only applies to Books).
COUNTER Release 5: Metric Types Investigations & Requests requests report user requests for a content item or chapter of a book. A request is specifically related to viewing or downloading the full content item. Total_Item_requests the total number of times the full text of a content item was downloaded or viewed. Unique_Item_requests the number of unique content items requested by a user in a session. Unique_Title _requests the number of unique titles requested by a user in a session (only applies to Books)
View abstract Link to Link Resolver Metric Types: Investigations vs Requests View cited references Link to ILL form Investigations View HTML full text Requests View PDF View content… View article preview
Title Reports TR_J1 vs JR 1 - Example 1 Release 5 Limited toControlledusageonly Twometrics per journal No HTML or PDF metrics Journal withzerousageexcluded No total for all journalsline 1 2 4 Release 4 3 5
Title Reports TR_J1 vs JR 1 – Example 1 Release 5: TR_J1 • Release 5 TR_J1 reportshowslowerusagecounts due to the exclusion of Gold OA usage • TR_J1 Usage = JR1 Usage – JR1 GOA Release 4: JR1 Release 4: JR1 GOA
Title Reports TR_J1 vs JR 1 – Example 1 Release 5: TR_J1 • Total Item Requestsvs Reporting period total (excludingOA_Gold) • Unique Item Request vs PDF + HTML Release 4: JR1 Release 4: JR1 GOA
Title Reports TR_J1 vs JR 1 – Example 2 Release 5: TR_J1 • Total Item Requestsvs Reporting period total (excludingOA_Gold) • Unique Item Request vs PDF + HTML Release 4: JR1 Release 4: JR1GOA
Title Reports TR_J3 vs JR 1/JR1 GOA Release 5 Shows usage by access type Shows all Investigations and Requestsmetrics No HTML or PDF metrics 1 2 Release 4 3
Title Reports TR_J4 vs JR 5 Release 5 1 Limited toControlledUsageonly Twometricsforeachjournal Noyeargroupingforolderyears Usageisshown per month 5 4 2 Release 4 3
Title Reports TR_B1 vs BR 2 Release 5 Publication Year isshownforeachbook Twometrictypes per book Unique Title Requestsas a consistentmetricfor all bookproviders 2 1 3 Release 4
Title Reports TR_B3 vs BR 2 Release 5 Usagesplit out by access type All applicablemetrictypes 1 2 Release 4
Platform Report PR_P1 vs Platform Report Release 5 Regular Searches and SearchesFederatedrolled up in SearchesPlatform Unique Item Requestscoversbothbook and journalusage Total Item RequestsequalsRecordviews 1 2 Release 4 3
Database Report DR_D1 vs Platform Report Release 5 SearchesFederated and Automatedaresplit in two separate metrics Result Click metrichasbeenreplaced by newmetric Total Item Investigations 1 Release 4 2
COUNTER Release 5: Metric Types Searches There are four different types of search metrics in Release 5. Searches_Regular the number of times a user searches a database, where they have actively chosen that database from a list of options OR there is only one database available to search. Metric captured at the database level. Searches_Automated the number of times a user searches a database, where they have not actively chosen that database from a list of options. Metric captured at the database level. Searches_Federated the number of times a search is run through Federated Search Service/Engine. Metric captured at the database level Searches_Platform the number of times a user performs a search on the platform, regardless of the number of databases involved in the search. Metric captured at the platform level.
COUNTER Release 5: Implementation and Compliance • Organisationsworkingtowards Release 5 compliance: https://www.projectcounter.org/about/organisations-working-towards-release-5-compliance/ • Providers thatarealreadysuccessfullyaudited on Release 5
Contact to COUNTER: lorraine.estelle@counterusage.org Additional Informationen: https://www.projectcounter.org i.barbers@fz-juelich.de ORCID: 0003-2011-7444 Twitter: @irene_barbers