The following list of FAQs is also available from the EBSCO Usage Consolidation interface.
On this page:
- Upon loading my usage file to Usage Consolidation, I receive an error. Why?
- Why aren't my Platform Details auto-populated by EBSCO?
- Where can I find information about configuring SUSHI for my platform(s)?
- What is the EBSCO SUSHI client's IP address?
- SUSHI has been harvesting data from my platforms, but no usage is showing upon generating a report. Why is this?
- In what file format do my usage reports need to be formatted in order to upload properly?
- When I select “Load Usage,” the system displays the message, “No results found.” Why?
- I attempted to save my Platform Details and got the error, “Sorry an error occurred while processing your request.” Why?
- When I look at the summary page for a usage file loaded, why is the number of records loaded so much higher than the number of titles?
- When I run a usage report and group by Publisher, I am not able to sort the report by any of the title elements, or the monthly usage. Why not?
- Does Usage Consolidation support COUNTER and SUSHI?
- Which content providers are SUSHI compliant?
- How does Usage Consolidation help me with collection management decisions?
- Can usage be estimated for future months or months where usage was missing?
- How do I know when the usage shown in a Usage Consolidation report has been estimated?
- Can I get cost-per-use information with Usage Consolidation?
- Can I integrate my usage in Usage Consolidation with EBSCONET Analytics in EBSCONET?
- Do I get additional analysis for e-packages I buy through EBSCO?
- What about the e-journals and e-packages I don't buy through EBSCO?
- Can Usage Consolidation capture usage for my individually subscribed e-journals?
- What if my staff and I don't have time to load usage?
- How do I locate the correct usage details for my platform?
- If I want to get the total usage for a title, do I need to run separate reports for "Full-text requests," "PDF requests," and "HTML full-text requests"?
- What is the role of "In My Collection" in Usage Reports?
- When more than one title appears to be a correct match as I'm working exceptions, does it matter which one I choose?
- Will Usage Consolidation show me a breakdown of full text downloads by database on full-text aggregator platforms?
- Where do I collect my usage statistics for Chicago Journals from University of Chicago Press?
- Where do I collect my Caliber usage statistics?
- How do I change a matched title to select a different match, or how do I match a title I have previously marked as "ignore"?
- Where do I find the usage statistics for my CSA Illumina and CSA Illustrata from before they migrated to the new ProQuest platform?
- How does the system match titles in a COUNTER report to the Knowledge Base?
- How can I undo a manual match?
- What happens in EBSCO Usage Consolidation when a title is removed from a platform in the EBSCO A-to-Z Knowledge Base?
Log in to Usage Consolidation and view the "Troubleshooting Platforms" section of Help.
The platform details your institution uses (Usage Statistics URL, Day of Month Reports Ready, Instructions, etc.) may be unique to your institution. Rather than populate default (possibly incorrect) information, EBSCO has provided you with this FAQ ("How do I locate the correct usage details for my platform?") for locating the proper usage information from each platform provider.
The SUSHI Server Registry, available from the National Information Standards Organization, lists a number of popular content providers offering SUSHI. This list also offers configuration information. If you need further information regarding configuring SUSHI, please contact your platform provider.
Some content providers have IP authentication for the SUSHI clients. Since EBSCO's SUSHI client is part of Usage Consolidation and runs on EBSCO's server, you must provide the IP address for EBSCO's client. The EBSCO SUSHI client's IP address is 18.104.22.168. Check the "SUSHI Authentication Method" on the Platform Reference List to see if a specific vendor requires this information.
SUSHI automates the retrieval of your usage statistics, but the data harvested needs to be reviewed and set to "Complete" before it is available for generating a report.
- Select the View History menu option.
- Locate the appropriate SUSHI File.
Note: SUSHI file names will begin with "SUSHI."
- Click the hyperlinked status.
- The Summary page displays for that file. Make any changes needed and then set the status to "Complete."
The data in the file will then be available for inclusion in generated reports.
In order to load usage statistics into Usage Consolidation, your file must be formatted as Microsoft® Excel, Comma Delimited (*.csv), or COUNTER XML file.
For more information, view Load Usage File Help (JSTOR) for additional details about formatting usage files.
Note: These instructions can be applied to other platforms besides JSTOR.
You have not yet configured the platforms for which you want to gather usage. Select “Configure Platforms,” then select the platform in question, add the relevant details (see Platform Details help for information about these fields), and then click Save. This platform will then display next time you visit Load Usage.
The system does not allow HTML to be included in any of the fields. If it sees a “<” character, it will assume there is HTML and displays the error. Remove any HTML coding, or if you have used the “<” character, remove that as well.
A COUNTER report may include many months of usage data for every row. Because EBSCO loads all of the months of data for a given title, the system counts each month as a separate record. If you have loaded 10 months of data on a report with 100 titles, then the summary will show 1,000 records and 100 titles.
This is because of the grouping and the ability to dynamically expand groups. If you want to sort by the more detailed information, choose the option to not group the report.
Yes. Usage Consolidation allows you to load key COUNTER reports from COUNTER-compliant content providers; it supports manual loading of Excel, comma delimited, or COUNTER XML usage reports, as well as automated harvesting and loading using SUSHI.
A list of SUSHI-compliant content providers is available at the SUSHI Server Registry: https://www.projectcounter.org/about/register/.
Thanks to a real-time connection with Usage Consolidation, usage data is directly integrated into your EBSCONET Subscription Management session, providing overall usage and cost-per-use details for subscriptions. Also in EBSCONET Subscription Management, you can instantly view your library’s EBSCO A-to-Z holdings information (including all locations of a title, in addition to specifics about coverage and embargoes). Knowing that a title is available in a database or through another package AND how much it is being used are valuable details to help you make well-informed collection development decisions.
Yes. “Estimate Missing Usage” is an option on all Usage Consolidation reports. When that option is checked, the system will supply estimates for the missing usage based on a rolling average of actual usage available for a title for the reporting period. For example, if you request a usage report for January through December 2013 and only January through October usage has been loaded, the system will estimate usage of November and December if you have selected the option to provide estimates.
Estimated values in the report will display as red italics on the screen and in the Excel download file. In addition, most of the Usage Consolidation reports include a Usage Status column, which will have a value of “Estimated” if some of the usage for that title has been estimated.
Yes, through EBSCONET Subscription Management. The role of Usage Consolidation is to collect and store usage data and enable other EBSCO tools, like EBSCONET Subscription Management, to use that usage to provide point-of-need analysis data, such as cost-per-use. You will find the cost-per-use details directly integrated into EBSCONET Subscription Management—the tool you use to manage renewals, work packages, consider new titles for subscription, etc.
Yes. EBSCONET Analytics integrates with Usage Consolidation and EBSCONET throughout your subscription workflow. Usage data are combined with key information captured within EBSCO’s order history to provide you with dashboards and on-the-spot analysis of the e-journals and packages you acquire through EBSCO. Decision support data is provided directly within your workflow. There is no charge for EBSCONET Analytics.
Yes. Since EBSCO knows the titles in your packages as well as the cost information, you are able to get usage and cost-per-use details directly in the E-Package Orders option within EBSCONET Subscription Management. There is no need to add cost data to another system or identify which titles are part of a package—this is all done for you.
Usage Consolidation allows you to load usage for any platform (content host), regardless of where you buy the resources. For those resources you buy through EBSCO, the cost-per-use analysis is available in EBSCONET Subscription Management. For your other resources, you can download your usage into a spreadsheet, then use Microsoft Excel to add the relevant cost details and calculate cost-per-use.
Yes. With Usage Consolidation, you can load COUNTER reports for the platforms (content hosts) where you access your content. Because usage is reported at the platform level, it does not matter if you subscribe to titles hosted on that platform as e-packages or as individual e-journals; the COUNTER report will list all titles available on that platform and include usage for each. Once the usage has been loaded into Usage Consolidation, usage data will be available to your EBSCONET Subscription Management account and will be displayed in the Subscription Usage Details Report, in hover-over displays, and in the Usage Details data panels for Orders and Titles. If you choose to load usage for your aggregated databases as well as your e-packages and individual e-journals, EBSCONET will show usage for All Platforms as well as for the Publisher’s Platform.
EBSCO knows that you and your staff may not be able to dedicate time to loading usage, so we can load usage on your behalf. We have established the EBSCO Usage Loading Service, a separate, highly skilled team that’s dedicated to helping Usage Consolidation customers manage usage statistics. This provides you with the option to outsource configuration, harvesting, and loading of usage data to EBSCO (a quote for this service can be provided upon request)—and allows you to focus on improving the quality of your collection.
No. The "Full-text requests" statistic already includes the totals for "PDF requests" and "HTML full-text requests." COUNTER included the format-specific metric types to allow librarians to see more of the details users were requesting. To get the total usage for a title, choose the Generate Report>Title Usage Reports>Title Usage Details screen, select Full-text requests as the metric type (along with any other criteria desired), and then choose Export Report to show the total number of uses for each title.
This indicates whether or not the item is in your EBSCO A-to-Z collection. When usage is loaded into Usage Consolidation, think of it as a multi-step process:
- Upload a usage file (or automatically import using SUSHI).
- Match the items in the usage file to the EBSCO Knowledge Base. (This step matches to the complete Knowledge Base without regard to your own A-to-Z collection.)
- Perform any manual matches to address reported exceptions.
- Change the status of the uploaded file to “Complete.”
- The usage loaded for the MATCHED items are moved to the reporting server.
When you run a report like the Title Usage Details report, the system reports on all titles for which you have loaded usage and uses the “In My Collection” column to indicate if that particular title is in your EBSCO A-to-Z collection.
No. As long as the title and ISSN match your resource, the system will be able to complete the match. Multiple titles may appear if the knowledge base contains more than one instance of the same title on the platform.
No. COUNTER reports journal usage at the Platform level and there is no breakdown by database. Note that release 4 of the COUNTER Code of Practice introduces two new database metrics—Result Clicks and Record Views by Database—that will offer a better measure of activity for databases. A “Record View” is essentially when the user clicks to look at the detailed view of a record in the database. A “Result Click” is when the user clicks on a link in the initial result list to get more information about the result from that database, including linking to the detail record, looking at references, linking to an external source like a Link Resolver, etc. These new metric types, which apply to both full-text and A&I databases, provide a much truer measure of the value end users get from the databases than the searches and sessions.
Journals from University of Chicago Press are hosted by JSTOR. Therefore, the usage will be included within the usage reports that you load for the JSTOR platform.
The journals from Caliber (University of California Press) are hosted by JSTOR. Therefore, the usage will be included within the usage reports that you load for the JSTOR platform.
To change a matched title:
1. Click the View History link.
2. Under the Status column, click the link for the corresponding previously loaded report.
Note: The report status must be either “Pending Review” or “Review In Progress” in order to allow for changes. If you have already marked the file “Complete,” you can select the option to reprocess the usage report to allow for changes.
3. From the Load Usage: Summary screen, click the View Matched link to locate the desired title.
4. Click the title link and then click the Browse button next to the “Title in Knowledge Base” row. Click the title link you would like to match to.
Note: To select a different title match, you can edit the search terms and click Search, if needed, and select a different title by clicking the desired title from the “Titles to Manually Match” section.
5. Click OK when prompted to save your changes. The status will now be displayed as Matched (overridden).
To manually match a title previously marked as “ignore”:
1. Follow Steps 1-2 above.
2. In Step 3, from the Load Usage: Summary screen, click the View Ignored link to locate the desired title. Follow the rest of the steps noted above to change the title from ignored to matched.
To change an ignored title back to an unmatched title:
1. Follow Steps 1-2 ("To change a matched title") above.
2. In Step 3, from the Load Usage: Summary screen, click the View Ignored link to locate the desired title.
3. Click the title link and then click the Remove Title from Ignore List button below the “Status: Ignored" row.
4. Click OK when prompted to save your changes. The status will now be displayed as Unmatched.
Statistics for 2012 and later can be found in your ProQuest usage report at http://admin.proquest.com/.
If you are no longer able to access your Legacy Usage Platform, you can request it directly from the ProQuest Customer Service Department at email@example.com.
Match-points are based on a point system where points are given for matches in ISSN, Title, and Publisher. The more pieces that match, the stronger the match. If there is one strong match, the automatic match happens; if there are two or more strong matches, then the “Unmatched (ambiguous)" status is set; and, if there are no strong matches, the status is set to “Unmatched.” The match is also limited to titles mapped to resources associated with the Platform in question.
Pull up the “View Matched” list, where you will see the status of “Manual Match.” This tells you what title has been manually matched. You can select a title that looks wrong and match it to something else. To set a manual match to “unmatched,” click the title name to open the Title Details page. Click the Remove Manual Match button and select OK when prompted to save your changes so you can then match it to another title later.
When a title changes vendors or is removed from a Platform, the usage loaded remains in the system and available for reporting under the Platform for which it was originally loaded.