View
57
Download
1
Tags:
Embed Size (px)
Citation preview
Implementing SUSHI/COUNTER at Your Institution
Oliver PeschChief Product Strategist
EBSCO Information [email protected]
What we will cover…
• A short review of SUSHI and COUNTER• Definition of a Platform• Options for SUSHI clients• SUSHI client configuration basics• Different platforms have different set-up needs• View a test harvest• Using Excel to view COUNTER XML• Simple cost-per-use analysis• Timing for harvesting and other considerations
Project COUNTER
• Since 2002• Consistent, comparable, credible usage
statistics• For Journals, Books, Databases and
Multimedia• Code of practice covers processing,
formatting, and presenting usage statistics• Compliance enforced through a formal audit
SUSHI
• Standardized Usage Statistics Harvesting Initiative
• First became a standard in 2007• NISO standard Z39.93 (2014)• Enables the automation of the request and
retrieval of XML versions of COUNTER usage reports
Platform
The online host where content is accessed.• Examples:– EBSCOhost– Highwire – MIT Press– ScienceDirect– Taylor & Francis
Platform
COUNTER measures usage for the Platform• COUNTER reports total activity by journal,
book, database, multimedia collection for the overall “platform”
Platform
COUNTER measures usage for the Platform• COUNTER reports total activity by journal,
book, database, multimedia collection for the overall “platform”
• There are no COUNTER reports that provide journal or book usage by “package” or databases
Platform
If you want to track usage by publisher e-journal package you need limit the results of the
Platform-level JR1 to only those titles included in the package.
SUSHI Clients
• The SUSHI standard simply describes how two computer applications can exchange a COUNTER report – by itself it does nothing
SUSHI Clients
• The SUSHI standard simply describes how two computer applications can exchange a COUNTER report – by itself it does nothing
• To use SUSHI requires a client and a server
SUSHI Clients
• The SUSHI standard simply describes how two computer applications can exchange a COUNTER report – by itself it does nothing
• To use SUSHI requires a client and a server• Content providers provide the server
SUSHI Clients
• The SUSHI standard simply describes how two computer applications can exchange a COUNTER report – by itself it does nothing
• To use SUSHI requires a client and a server• Content providers provide the server• You need to provide the client
SUSHI Clients
• The SUSHI standard simply describes how two computer applications can exchange a COUNTER report – by itself it does nothing
• To use SUSHI requires a client and a server• Content providers provide the server• You need to provide the client• So where do you find a client?
Commercial Usage Applications
Offer comprehensive tools that help manage the usage workflow and assist with analysis. These applications usually have a built-in SUSHI client.
Commercial Usage Applications
• Examples include:– EBSCO Usage Consolidation– Ex Libris UStat– Innovative ERM– ProQuest 360 COUNTER– Etc.
Open Source Clients
Provided “as-is” and often limited to helping with the harvesting of COUNTER reports or to serve as a proof-of-concept or as a starting point for creating more comprehensive systems. They don’t offer any analysis capabilities.
Open Source Clients
• Examples include:– MISO (ProQuest)– Pycounter (The Health Sciences Library System of
the University of Pittsburgh)– SoapUI (a web service test tool by SmartBear)
NISOSUSHI Tools & Aids
http://www.niso.org/workrooms/sushi/tools/
SUSHI Configuration Basics
When a SUSHI client requests a report it needs to know:• The URL of the SUSHI Server
And it needs to tell the server:• Who is making the request• Which institution’s usage to return• What report it wants• For what date range
SUSHI Configuration Basics
When a SUSHI client requests a report it needs to know:• The URL of the SUSHI Server
And it needs to tell the server:• Who is making the request• Which institution’s usage to return• What report it wants• For what date range
Customer ID
Requestor ID
SUSHI Server URL
MISO Client: ConfigurationIn preparation for this I have already installed the MISO client from https://code.google.com/p/sushicounterclient/. The executable (MISO.exe file) is in my C:/MISO directory.
MISO Client: ConfigurationIn preparation for this I have already installed the MISO client from https://code.google.com/p/sushicounterclient/. The executable (MISO.exe file) is in my C:/MISO directory.
MISO Client: Configuration
MISO uses a comma separated text file for configuration. Multiple platforms can be represented in the file and multiple reports can be selected for each platform.
MISO Client: Configuration
MISO uses a comma separated text file for configuration. Multiple platforms can be represented in the file and multiple reports can be selected for each platform.
Note that MISO was created for an earlier version of COUNTER but will support retrieval of JR1 and DB1 in XML for COUNTER Release 4.
MISO Client: Configuration
The “Library Code” identifies the library usage is for and will be part of the name of the file MISO creates. This value is NOT sent to the server.
MISO Client: Configuration
The “Provider name” identifies the platform where usage will be harvested. It is also part of the name of the file MISO creates. This value is NOT sent to the server.
MISO Client: Configuration
Specifies the COUNTER “Release” number for the report being requested. At this point it should always be “4”. This is included in the SUSHI Request.
MISO Client: Configuration
The “URL” is the address of the SUSHI Server for this provider. This MUST be the URL of the server not the WSDL.
MISO Client: Configuration
The “Requestor ID” identifies organization making the request. This is assigned by the usage provider and is their way of identifying who is asking for the usage.
MISO Client: Configuration
The name of the organization making the request. This could be the library or the usage consolidation service provider. This is included in the request.
MISO Client: Configuration
The email for the requestor. This is sent as part of the request to give the usage provider a way to contact the requester if something goes wrong. Note that some usage providers use this field to send the library administrator password for their administration module (although this technique is not really considered compliant).
MISO Client: Configuration
This is the identifier for the library that the usage is being requested for. It is the identifier assigned by the content provider. All usage providers will require this field to contain the correct value and most will also require the Requestor to have been authorized to retrieve usage for the identified institution.
MISO Client: Configuration
The name of the institution that usage is being requested for. This is sent as part of the request but is informational.
MISO Client: Configuration
In this section, a “y” or “n” indicates if the corresponding reports should be retrieved. Note that only JR1 and DB1 apply for COUNTER R4.
SUSHI Client Configuration
• The information needed to configure the client for a platform comes from the content provider
SUSHI Client Configuration
• The information needed to configure the client for a platform comes from the content provider
• Many content providers require SUSHI to be activated before it can be used
SUSHI Client Configuration
• The information needed to configure the client for a platform comes from the content provider
• Many content providers require SUSHI to be activated before it can be used
• Engaging with the content provider’s customer service or their administrative/reporting website is often a requirement
SUSHI Client Configuration
• The information needed to configure the client for a platform comes from the content provider
• Many content providers require SUSHI to be activated before it can be used
• Engaging with the content provider’s customer service or their administrative/reporting website is often a requirement
• The process of “activating” a platform for SUSHI and getting the configuration details to add the client will vary by content provider
SUSHI Client Configuration
• The SUSHI Server Registry is a good place to start for instructions.
http://www.niso.org/workrooms/sushi/registry_server
Many Publishers Use 3rd Party Services for their Usage Reporting
Major Service Provider Approximate # of Publisher Platforms
Notes
Atypon 10 Access credentials from Usage Data page in Institutional administration section of publisher website
Highwire 35 Uses primary e-mail address and portal password in Customer ID
MPSInsight 10 Activated via the publisher’s usage web site.
ScholarlyIQ 10 Activated via the publisher’s usage web site.
SilverChair 10 Require password in Requestor email. Users of 3rd party services must contact for configuration assistance
Activating SUSHI for MPS InsightASTM Digital Libraryastm.orgEmerald Group Publishing Limitedhttp://www.computer.org/IEEE XploreIOPsciencenature.compalgrave-journals.comrsc.org…
Activating SUSHI for ScholarlyIQACM Digital LibraryAlexander Street Press PlatformAPA PsycNETAPSASAIngentaConnectJSAD
OSA PublishingOxford JournalsPPPScitationwww.internurse.com…
Harvesting Usage: MISO Client Demonstration
In this section we will:• Harvest usage for a single platforms for March
2015 on a commercial product• Harvest a set of platforms using the MISO
client• Look at one of the XML files
Next I type the MISO command line to ask for usage for March 2015.
Miso –d 201503 201503 –x
The “-d” specifies the date range in yyyymm format (if you leave it off it retrieves the prior month.) The “-x” tells MISO to save the XML version of the file.
Provider Name
Library Code
Dates Requested
Report
Remember how we said that some of the elements of the configuration file appear in the file name… here is what we were talking about.
Working with XML
COUNTER XML provides a great way to exchange usage data; however, it is not very user friendly.• Commercial usage consolidation product will
handle the transformation of the XML and do something meaningful with the data
• Users of Open Source SUSHI clients will probably need some help
Using Excel for COUNTER XML
• Open the file as XML in Excel• Excel with map each element to its own
column• Unwanted columns can be deleted or hidden• Filters can be used to limit the list to just the
resources and metric types desired (e.g. ft_total)
• At that point you have some usable results
First option is easiest, but if you use the third option you can select
which elements to show. We will pick the first.
Here I have selected all columns A..W and am
choosing to “hide”. You could also delete them if
you like.
This is a bit more like it.However, note that the columns X
and Y are empty – this is where the ISSN would normally go. This is one
of the issues with this “simple” approach.
This is a tool that will convert a COUNTER XML harvested with
MISO and turn it into well formatted JR1 (R4) in Excel
This is a tool that will convert a COUNTER XML harvested with
MISO and turn it into well formatted JR1 (R4) in Excel
Just click the button…
First step is to format the body of the report as a table. (This
isn’t required but I find it makes things easier).
First step is to format the body of the report as a table. (This
isn’t required but I find it makes things easier).
For ease of viewing I also freeze the panes so the header
and journals column stay on the screen.
We could type in the cost here, but in this example we will use the journal name to look-up in
our “Cost” worksheet.
I am using “VLOOKUP” to find the Journal on the Cost
worksheet and return the cost value (column 4).
The value is a simple calculation; however, if the
usage is zero we will substitute the actual cost.
The value is a simple calculation; however, if the
usage is zero we will substitute the actual cost.
Timing: When to harvest
• COUNTER allows usage providers up to 4 weeks to process and prepare their usage data; therefore, for some providers your April data may not be ready until May 28th.
Timing: When to harvest
• COUNTER allows usage providers up to 4 weeks to process and prepare their usage data; therefore, for some providers your April data may not be ready until May 28th.
• This varies by provider so you need to get to know your providers.
Timing: When to harvest
• COUNTER allows usage providers up to 4 weeks to process and prepare their usage data; therefore, for some providers your April data may not be ready until May 28th.
• This varies by provider so you need to get to know your providers.
• If you harvest too early the SUSHI client will receive an exception.
Key points…• SUSHI is a protocol that allows a computer
application to retrieve a COUNTER report • It needs a “client” application• Configuring the client often requires interaction with
the content provider or their website• SUSHI will return XML• If you don’t have a system that consumes COUNTER
XML, Excel can be used to produce analysis reports
Other Considerations
Lots of information is available on the NISO SUSHI Web Site, including a section “SUSHI for Librarians”.
http://www.niso.org/workrooms/sushi/librarians
Other Considerations
If you haven’t already looked at Usus please do, it is a community web site all about usage…
http://www.usus.org.uk
Other Considerations
The NISO SUSHI team is looking for volunteers to help create Open Source tools or enhance what is already available…. Consider this an open invitation!