FAQ

Using JUSP

  • I have logged in via my institution, but another login box pops up. How do I login to JUSP?

    Your institutional contact will have been provided with the login credentials for the pop-up box. In the event that they do not know them, please contact the helpdesk and we will supply you with a working username and password. You can also set up your Shibboleth account to bypass this step entirely. Please see: http://jusp.jisc.ac.uk/entitlements/siterep/ Further details about accessing JUSP are available on our joining JUSP page: http://jusp.jisc.ac.uk/join/uk-academic-libraries/

  • What does JUSP contain?

    JUSP contains JR1, JR1a and JR1 GOA COUNTER-compliant usage statistics and provides a single gateway for libraries to access statistics from participating publishers, gateways and host intermediaries. From March 2016 JUSP has developed an ebook service which includes data from the BR1, BR2 and BR3 reports. In summer 2016 we also added JR2 and JR5 reports for a number of publishers. Although the original and primary focus was on the NESLi2 publishers, JUSP now includes increasing numbers of other interested publishers. You can find a full list of participating publishers and the reports we're collecting on our Participants page. If there are any additional publishers you wish to see in JUSP then please submit them via a facility within the portal. We are only able to work with publishers who are fully COUNTER compliant and provide usage data using the SUSHI Protocol.

    Over 20 journal and book reports are available in JUSP, all derived from the JR1, JR1a, JR1 GOA, JR2, JR5, BR1, BR2 and BR3 reports. You can find a full list of the available journal reports on our Guides to the reports page and book reports on our Guides to book reports page.

  • Do JR1 reports include the breakdown of PDF/HTML?

    PDF/HTML breakdown figures are not provided in a consistent format by all publishers, so we don't include this information in our reports. JUSP presents the total usage figure for the specified time period.

  • How do I compare my usage with that of other institutions?

    Usage profiling reports are available for a number of publishers. These reports enable you to compare your usage for a particular publisher with an average for all libraries for which we hold data from that publisher in JUSP and that are in the same Jisc band and region, and in the groups (pre-1992, post-1992, RLUK, etc) to which their institution belongs. Reports can be run by calendar or academic year. We hope to add more publishers over time.

    Libraries can also perform their own internal comparisons through features such as the "Number of titles and requests in various usage ranges" report.

  • Can I download and export my own data?

    Yes you can. Report data are downloadable in CSV format and you can also download journal and book reports from JUSP via SUSHI machine-to-machine interaction. You can find more information about this in our Interoperability FAQs.

  • How do I ensure that all my HighWire data are visible in JUSP?

    Subscriptions on the HighWire platform can be associated with multiple accounts. Each of the publishers in HighWire assigns a unique account number to their subscribers, and provides that directly to them. However, HighWire offers the functionality to consolidate usage across the various publishers by associating all HighWire subscriptions with one account.

    We ask you to provide us with details of this HighWire account when you sign up for JUSP in order that we can gather your HighWire usage data. Please ensure that all your HighWire titles are associated with this account.

    When a new HighWire-hosted publisher joins JUSP, you will need to check that all the titles from that publisher are associated with this account. If they are not, please associate them, check to see that they are appearing in that account on the HighWire website and let us know via our helpdesk so that we can regather data for you if necessary.

    You can see a full list of HighWire publishers on our Participants page and further details on how to associate titles in HighWire can be found on its website.

  • Do you plan to include database reports?

    We have done some investigative work into the feasibility of including DB1 reports into JUSP, and this is a likely development in 2017.

  • Will there ever be a time when I can run a report for say, ProQuest or EBSCOhost, and it will give me a JR1 and BR2 for a particular full-text database?

    Usage for any publisher or aggregator is not supplied with clear division of packages, deals or products, we simply collect and process JR1, BR2 and other reports as supplied by the publisher and work with those. Data about which titles are included in a particular package or product are best explored by using KB+.

Using JUSP for ebooks

  • Why can't I see any data for the BR1 (or BR2)?

    The BR1 report is to be provided only when an entire book is provided as a single file; otherwise Book Report 2 must be used (COUNTER). Most publishers supply the BR2 and not the BR1 though some do provide both. The table on our Participants page will show which reports each publisher provides.

  • Where can I find out what ebook data are available?

    You can view which reports publishers provide on our Participants page. You can see which months have been gathered for your institution by viewing "Your data" on the welcome page in the portal.

  • Are you planning to add more book publishers?

    Yes! We are actively working with around a dozen ebook publishers and aggregators; in many cases we have identified issues with their COUNTER reports which have been passed back to the publisher to fix. JUSP requires data to be supplied using the SUSHI protocol and some vendors do not currently offer this - until they do, we are unable to work with them. When you are logged into the JUSP ebook portal, you can see the current situation for various publishers and aggregators.

  • What does "section request" mean?

    The meaning of section request varies between publishers. The COUNTER definition is "the first level of subdivision of a book or reference work." For example, this may be a chapter or an encyclopaedia entry. We are looking into providing a community-based approach to compile a list of publishers' use of section.

  • How do I compare BR1 and BR2?

    The BR1 and BR2 are not directly comparable. For the SCONUL return, SCONUL suggests you apply a multiplier. If you have any other suggestions of ways to deal with this, please let us know and we can share it via our community page.

  • I access ebook content through aggregator services and they are able to supply usage reports. When will I be able to access this content in JUSP?

    There is significant interest from JUSP libraries in being able to access usage data from ebook aggregator services. Unfortunately the majority of these aggregator services do not currently support the SUSHI protocol. Members of the JUSP team and Jisc Collections have been in contact with the main aggregator services to discuss this, but we have no timescale for development. When you are logged into the JUSP ebook portal, you can see the current situation for various publishers and aggregators.

    As JUSP relies on the COUNTER standard and machine based SUSHI services to provide a cost efficient and effective service it will be necessary for these vendors to offer SUSHI support before JUSP can harvest data. We encourage JUSP libraries to contact ebook aggregator vendors to lobby for conformance.

  • What does "metric_type" mean?

    The metric type defines what is actually being counted in the report. For example, in the case of the JR2 and BR3 the metric type can be 'turnaway', 'no_license' or 'other', which are all types of access denied. Please refer to the Glossary for more detail on each type.

  • Can I mark-up e-book titles by purchase type?

    No. JUSP does not currently have this functionality. We are looking into adding the function to mark "key titles" and will be consulting the community about the best ways to achieve this. KB+ does not include ebooks at the moment and so we cannot use the same approach as with journals.

How JUSP processes usage data

  • How many years' worth of usage data do you hold and how often is this updated?

    We collect journal data from January 2009 and book data from January 2014 (where available) for all participating institutions and update the data continually. We make data available when the publisher releases them, so this could be at any point during the month. JR2 and JR5 reports are available from January 2015 onwards.

  • Do you make any changes to the data?

    No. We take the data as provided in the publishers' SUSHI feeds and do not change or manipulate them unless the file fails one of our checking procedures and there's an obvious fix, for example a missing ISSN. The totals figures are never changed.

  • What checks do you carry out before you upload the data?

    We can't check every file for every publisher and institution by eye as this would leave no time to do anything else! But over 99.9% of the data are collected with no problems and it is only in a very tiny minority of cases that errors occur.

    Data go through several stages before they are accepted into the database.

    1. We carry out a visual check of the size and format of the publisher files to ensure it's a correct file. Files are almost always of a certain file size, so any that differ wildly are likely to be false downloads and in those cases we gather them again.
    2. We run a program over the files, which performs around a dozen sanity checks to ensure that the files are formatted correctly, that identifiers are present, that titles are not incomplete or missing, and that the XML structure in the file is correct.
    3. We generate a load file for each corresponding SUSHI file. Once loaded, we randomly pick a selection of institutions and check that the figures look correct.

  • What types of errors does JUSP find during these checks and how are they resolved?

    Although 99.9% of files work straight away, we do sometimes encounter problems both in the SUSHI data collection and in the file processing.

    Occasionally files may timeout on download, or only include partial data - this is why we perform a visual check of the file sizes. The checking can then throw up a wide range of errors, which can include: wrongly formatted or missing identifiers; problems with non-ASCII characters (we correct these); incorrect XML; carriage returns or other spacing errors in the files; titles appearing which aren't in the JUSP database (we then add them before reprocessing); missing total counts (very rare); all total counts being 0 (genuine in some cases, but in others obviously a mistake); and many more. When we find a recurring issue, we contact the publisher and this is usually fixed at source.

  • What happens to any errors that are not identified during these checks?

    One of the benefits of being part of the JUSP user community is that if our participants notice any data anomalies, we can investigate them, resolve them (with help from the publisher where necessary) and make any corrections to the data. This benefits not just the initial enquirer but also all JUSP libraries. We also sometimes receive notification from publishers of issues with their data, such as restatement of a particular month's data, and we can also resolve these to benefit all JUSP libraries.

    Let us know if you spot any potential data anomalies and we will investigate.

  • How does JUSP handle usage data from journals' databases or aggregated sets of publisher data such as Project Muse?

    We provide a JR1 report for Project Muse as a whole (as supplied) rather than breaking the usage down by any individual publishers that form part of that report.

  • How does JUSP handle usage data from JSTOR?

    We provide JR1 reports for JSTOR in the same way as for any other participating publisher.

    Where a title in JSTOR also has usage directly from the publisher or via a gateway / intermediary, the individual journal search and usage report and the title click-through functionality in many of the reports will enable you to see the total usage of a title, split into usage via publisher and gateways, and usage via JSTOR.

  • How does JUSP handle usage data from gateways and intermediaries such as EBSCOhost or IngentaConnect?

    From these gateways and host intermediaries, we only extract the usage data for those publishers that have signed the JUSP participation agreement. The data are added to direct publisher usage in reports such as "JR1 reports including gateways and host intermediaries" and "Annual summary use of gateways and host intermediaries", as well as many summary-level reports.

    We do not process data for publishers that are not signed up to JUSP and therefore we cannot display or provide a "complete" JR1 for SwetsWise, Ebsco EJS, EBSCOhost, ProQuest or IngentaConnect at this time. When any new publisher formally joins JUSP, we reprocess all the host/intermediary files and extract any available usage back to January 2009 (where possible) for that publisher as well as collecting the direct publisher usage in the usual way via download from the publisher's SUSHI service.

    Please note that Ebsco EJS provided usage statistics up to July 2014; after that date usage of all titles accessed via Ebsco EJS comes directly from the publisher. SwetsWise ceased operations in late 2014 and usage data from them are available in JUSP up until November 2014.

  • What happens when a journal changes publisher?

    If the new publisher is a JUSP participant, we will collect data from that publisher as they start to appear in their JR1, JR1a, JR1 GOA, JR2 and JR5 reports. You may however also continue to see usage from the previous publisher if articles from earlier volumes from that publisher continue to be available to you. When you use the individual journal search and usage report and the title click-through functionality in many of the reports you will see usage details for all publishers of the selected journal title.

    If the new publisher is not a JUSP participant, feel free to suggest them as a new participant via the wishlist facility within the JUSP portal itself.

Interoperability

  • What is JUSP interoperable with?

    JUSP is interoperable with UStat, 360 Counter, Millennium and EBSCONET Usage Consolidation and we are exploring the possibility of interoperability with other usage statistics products. A JUSP API is available to support wider projects and services such as KB+ and RAPTOR-JUse. Please contact our helpdesk if you would like more information about this.

    Further information about using the JUSP SUSHI server to gather usage data from JUSP and import it into other usage statistics products can be found on the SUSHI server administration/ authorisation pages accessible from your JUSP portal welcome page. You will also find there a list of a list of the SUSHI parameters that you will need (CustomerReferenceID, CustomerReferenceName) for those publishers for which we hold your data in JUSP.

  • How do I access JUSP data via UStat?

    Go to the SUSHI server administration/ authorisation pages via the link from your JUSP portal welcome page and check the "Authorize 3rd party access" for UStat box.

    See our video which demonstrates the stages required to set JUSP up in your UStat account. You will need to set up an entry in UStat for each publisher participating in JUSP.

  • How do I access JUSP data via Millennium?

    Go to the SUSHI server administration / authorisation pages via the link from your JUSP portal welcome page and enter Millennium's IP address in one of the IP boxes.

    Check the Innovative online customer support website (CSDirect) if you're an ERM customer and need help setting up SUSHI harvesting from JUSP.

    You will need to set up an entry in Millennium for each publisher participating in JUSP as shown here:

    1 > Access Provider         elsev
    2 > Customer ID             1
    3 > Consortium Affiliation
    4 > Day of Month            29
    5 > From (# of months back) 5
    6 > To (# of months back)   2
    7 > WSDL URL                http://jusp.jisc.ac.uk/sushiserver/?wsdl
    8 > Requestor ID            exe
    9 > SUSHI Release           1.6
    

    The JUSP server requires the correct version of SUSHI software to be added to the Millennium SUSHI configuration. If line 9 is blank, users will get an error message.

  • How do I access JUSP data via 360 Counter?

    Go to the SUSHI server administration/ authorisation pages via the link from your JUSP portal welcome page and check the "Authorize 3rd party access" for 360 COUNTER box.

  • How do I access JUSP data via EBSCONET Usage Consolidation?

    Go to the SUSHI server administration/ authorisation pages via the link from your JUSP portal welcome page and check the "Authorize 3rd party access" for EBSCONET Usage Consolidation box.

  • What should we do if our usage statistics products isn't listed

    We have worked with a number of providers to develop interoperability with their products, and these products are listed above, and in the SUSHI server admin and authorisation section of the Journal and Book Portals. If the statistics tool you use is not listed, you can authorise access by entering their IP address in the box as described in the JUSP Journals SUSHI Service User Guide and the JUSP Book SUSHI Service User Guide (available within the respective Portals).

    If you would like to see the product added as an authorised third party service, we will need to work with the vendor in order to set this up, so you will need to contact the vendor and ask them to approach us about working with them. You can also view a template email in the SUSHI server admin pages of the logged in Portals.

  • What is the JUSP SUSHI server?

    SUSHI is a PHP-based system that allows participating institutions and third parties such as UStat and Millennium to download usage data directly from JUSP. By downloading data this way, you can save time by interacting with a single SUSHI server as opposed to multiple publisher servers. And you can also be certain that the data has been rigorously checked as we quality check at the point of aggregation.

  • How do I access the SUSHI server?

    You'll need a SUSHI client that can send and receive SOAP messages conforming to the SUSHI 1.6 standard, and you'll also need to register for SUSHI access with JUSP and provide the Requestor ID, Customer Reference ID and other required information when you use your SUSHI client to make a SUSHI request. You can find further details about this and a user guide on the welcome screen that you see when you login to the JUSP portal.

  • What reports can I download via SUSHI and when?

    You can download all core reports (JR1, JR1a, JR1 GOA, JR2, JR5, BR1, BR2 and BR3) via SUSHI.

    Data from individual publishers are released at different times during the month. If you only intend to gather data using the JUSP SUSHI server once a month, we recommend doing this at the end of the month. If you want to gather data for an individual publisher, check your JUSP portal welcome page to ensure that the data you require are available in JUSP.

  • How does JUSP work with KB+

    JUSP works to share data with KB+ in 3 important ways. Firstly, almost all title lists in JUSP are taken from the KB+ public exports facility, enabling us to download quality assured and checked title lists rather than finding them from numerous sources on the Internet. Secondly we work with KB+ to supply them with headline journal usage figures for inclusion on the KB+ service. These are exported from JUSP into KB+ using our API. Finally we now have a shared core titles facility, which is maintained at KB+ and imported / updated on JUSP regularly.

  • How often are core titles updated?

    Users maintain their own lists of core titles on the KB+ service alone (previously this was done in separate ways on both services, hence the need to rationalise). JUSP then imports the updated data regularly (usually weekly, but we can do this more frequently on request). When core titles are included in JUSP reports, they are denoted with a small yellow star next to the title in the relevant report.

Publisher participation

  • What is required for publisher usage data to appear in JUSP?

    For data to appear in JUSP, a publisher must meet the following criteria:

    • They have been requested to join by JUSP participating libraries
    • They supply at least one of the JR1, JR1a, JR1 GOA, JR2, JR5, BR1, BR2 and BR3 COUNTER-compliant usage statistics reports via the Standardized Usage Statistics Harvesting Initiative (SUSHI) protocol (http://www.niso.org/workrooms/sushi)
    • They return a signed Publisher Participation Agreement
  • What is the role of the JUSP team in getting a publisher to participate in JUSP?

    Jisc Collections, a JUSP consortium partner, contact publishers requested by libraries. They provide them with background information about JUSP, and respond to any questions or concerns they may have, and arrange meetings and demonstrations as required. The team also promote JUSP more generally in the publisher community through events to raise the profile of JUSP. Once the publisher has signed up to JUSP, we can also work with them to test their SUSHI service and COUNTER reports.

  • How can libraries help encourage publishers to join JUSP?

    A common response from publishers is that they aren't aware of demand from libraries for them to join, so it is important that publishers hear about JUSP from you as well. If you are meeting a publisher representative or contacting them about usage statistics, ask them whether they have heard of JUSP and if they will participate.

    We have written a template letter which you can access from the publisher wishlist section within the logged in Portal. If you are involved in a publisher library advisory group and that publisher is not a member of JUSP, please ask them to join.