360 Counter: Cost-Per-Use Metric
- Product: 360 Counter
How is the cost-per-use metric calculated in our 360 Counter Consolidated Reports?
This document provides a detailed explanation of which data from the Client Center are used to calculate the cost-per-use-metric in the 360 Counter Consolidated Reports.
There are six sections of information; four sections are in this document and two sections are in other Support Center answers. Click one of the following items to jump to that section:
Date (other Answer)
Adding Payments to Database Level and Title Level
Include Payment in Total for Fiscal Year (other Answer)
Payment Amount (Local Currency)
Adding Payments to Database Level and Title Level
Include Payment in Total for Fiscal Year (other Answer)
Payment Amount (Local Currency)
Adding Payments to Database Level and Title Level
Payment information can be entered at each level of the resource hierarchy -- collection, provider, database, and journal -- for a fiscal year. However, 360 Counter consolidated reports only include database- and title-level data; payments entered for collections and providers will be ignored by 360 Counter. The only costs that matter for the purposes of 360 Counter Consolidated Reports are database and title costs.
Payment Amount (Local Currency)
For payments entered at either the Database or Title level, the Cost per Fiscal Year calculation is based on the Payment Amount (Local Currency) on the Payment Details page. Payment Amount (Transaction Currency) is not used to calculate costs in Consolidated Reports:
Calculating Costs for Use in Database Reports
The calculations 360 Counter uses to determine the effective database total for a year depends on whether the Use Itemized Total box is checked on the General Cost page.
If the Use Itemized Total box is not checked, then 360 Counter will calculate database costs for use in Consolidated Database Reports (DB1 and DB2) by using the sum of payments entered at the database level for a given fiscal year:
If the Use Itemized Total box is checked, then 360 Counter will calculate database costs for use in Consolidated Database Reports (DB1 and DB2) by using the sum of payments entered at the title level within the database for a given fiscal year:
Calculating Costs for Use in Title (Journal) Reports
360 Counter supports journal reports JR1, JR2, and JR3, and book reports BR1, BR2, and BR3.
360 Counter only displays costs associated with normalized titles. Normalization is the process of bringing all instances of a title in 360 KB together to align metadata contained in those instances with the metadata contained in the authority record. Title fields in a MARC Record, along with the ISSN, are used to create this alignment. Normalization is what allows 360 Counter to generate reports that show journal usage across providers.
Because of this, and because we are still adding normalization information to e-book titles, any e-book usage data in 360 Counter may not be as complete as your e-journal usage.
Because of this, and because we are still adding normalization information to e-book titles, any e-book usage data in 360 Counter may not be as complete as your e-journal usage.
If the Use Itemized Total box is checked, then a cost entered at the database level is ignored and each title's cost is whatever is entered specifically for that title. If the title has no cost associated with it, then it will have no cost in the Consolidated Reports.
If the Use Itemized Total box is not checked, there are no relevant title-level costs within the database, and you subscribe to all the titles in the database (it is not "selectable"), then the cost entered at the database level will be spread out evenly across the tracked titles in the database. If there are title-level costs within the database, then the cost entered at the database level will be spread out evenly across only those titles that do not have a cost associated with them. Additional details are in the Hybrid Cost Model section below.
Hybrid Cost Model
Occasionally you may have a subscription in which you pay one cost for the Database package of titles and then an additional cost for individual titles in the same Fiscal Year (year 2014 in the example below). This is known as a Hybrid Cost Model.
For the Hybrid Cost Model above, a payment for the Database in the amount of $20,000 was made in 2014, along with an additional $5,000 for individual itemized title costs ($1,000 each for 5 individual titles).
Also note above that the Use Itemized Total checkbox is not selected, which means the Database cost (not the itemized title costs) is used to calculate Cost-per-Use. When you run a DB1 report in Intota Assessment you will see that the Database Cost is $20,000. In order to view the correct Cost-per-Use in your Counter (JR) consolidated reports, Intota Assessment does a couple things:
Also note above that the Use Itemized Total checkbox is not selected, which means the Database cost (not the itemized title costs) is used to calculate Cost-per-Use. When you run a DB1 report in Intota Assessment you will see that the Database Cost is $20,000. In order to view the correct Cost-per-Use in your Counter (JR) consolidated reports, Intota Assessment does a couple things:
- First, it will apply the individual title costs to those titles and you will see that cost reflected in your JR reports. Cost-per-Use for those titles will be based on the $1,000 for each of the individual titles:
- Second, the $20,000 database cost will be applied to the remaining number of subscribed titles in the database. In our example, the remaining titles (a sample of titles are shown below) have a Cost of $192.31 which is used in calculating the Cost per Use:
- Date Created: 9-Feb-2014
- Last Edited Date: 16-Oct-2015
- Old Article Number: 7168