NISO Update June 2014 SUSHI


Published on

The NISO Update provides the latest news about NISO's current efforts, including standards, recommended practices and community meetings covering many areas of interest to the library community. Working group members will provide updates on projects newly underway or recently completed

Published in: Education, Technology, Design
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • New fresh look that is focused on the “standard” and what it is and how to use it. Previously the web site was more oriented to the process of creating SUSHI.
  • A new logo…
  • The standard and the implementation profile are front and center!
  • The side-menu is focused on using the standard
  • And the SUSHI registry, formally a Google Site is now integrated. Both COUNTER 3.0 and COUNTER 4.0 will be represented. Consider this a call to all content providers to register their COUNTER R4 implementation…
  • Speaking of COUNTER Release 4… it became the official code of practice as of January of this year. We won’t go into details on what changed with Release 4 (if your are interested, there are some articles published on the topic and the introduction of the CoP provides a good overview as does the COUNTER SUSHI Implementation Profile.)… Anyway, Release 4 included some new reports and metric types so new schemas were released to support these. We also updated the COUNTER SUSHI implementation profile which provides developers with valuable guidance on implementing a SUSHI Server for COUNTER Release 4.
  • Now on to some interesting new work that is being done. SUSHI was release with a very simple “filter” mechanism… in the request the client application was able to specify a customer, a report and a date range and that is it. While this is sufficient for the basic needs of pulling COUNTER reports, looking to the future, additional filters options seem appropriate. Lets show you with examples.
  • Some organizations, like JUSP has SUSHI servers that can deliver usage for a variety of Platforms; therefore, a “Platform” filter makes sense. You see the XML showing the filter as a “Filter” element with a name and value.
  • COUNTER requires publishers to include all zero-usage titles. This can result in very large reports. What if you don’t want them? An “ExcludeZeroUsage” filter would allow these to be excluded making the report smaller and faster to process.
  • Here we have a few variations on a theme – limiting the usage to a department, or sub-account or IPRange…
  • Now, before you get too excited and start adding filters to your requests… At this point this is new and Filters are optional. It is up to the client and server to be agree on the filters and their meaning before they are used. Having said that, a controlled list of filter names and definitions will be maintained on the SUSHI web site to set some standards. Over time I would envision that the “community” would agree to make certain filters mandatory. The SUSHI Filters work is about creating that infrastructure to allow that to happen… Because this is a change to the SUSHI standard itself, it will need to be voted on… all of that should happen later this year. Oh, and the goal is to implement Filters in such a way that it does not break previous implementations.
  • The SUSHI committee also working on a project called “SUSHI Lite”. The deliverables from this project will be a technical report and one or more proof of concepts that explore the evolution of SUSHI into a light-weight protocol suitable for exchanging snippets of usage… We will talk more about the why in a minute, but first lets get the technical details out of the way…
  • The idea is to use the HTTP REST approach for requests vs the existing SOAP protocol. This turns SUSHI into an up-to-date web service where requesting COUNTER usage via SUSHI could be as simple as submitting a URL. Here is an example of a request for a JR1 report for the first three months of this year for just ONE journal… (that is where the snippet concept comes in).
  • The response will come back as JSON or JSONP with XML also being offered as an option. Most modern programming languages handle the parsing of JSON automatically, making it easy to work with the exchanged data.
  • This is how JSON looks…
  • So what are the potential uses of SUSHI Lite? <review the above>
  • And here is who are involved.
  • This work is progressing… <review above>
  • NISO Update June 2014 SUSHI

    1. 1. NISO Update SUSHI Standing Committee
    2. 2. Activities of the past year • Updates made to the NISO SUSHI Web Site • Addressed changes that came with introduction of Release 4 of the COUNTER CoP • Expanded “SUSHI Filters” are being added to the standard • Experimentation on “SUSHI Lite” is underway
    3. 3. SUSHI Web Site • Updated look • New logo • Improved usability – clearer explanations and easier navigation • SUSHI Server Registry now integrated and accommodated R3 and R4 support
    4. 4. Changes resulting from COUNTER R4 • COUNTER R4 introduced new reports and new metric types impacting schemas for: – COUNTER – COUNTER Elements – COUNTER_SUSHI • Updates to the COUNTER SUSHI Implementation Profile (offers a guide to the changes in R4 and how to implement them)
    5. 5. SUSHI Filters • SUSHI was introduced with only the ability to specify a date range as a filter in the request. • A more flexible mechanism is needed to include other filter options on the request.
    6. 6. Filter examples Limit report to just usage from a particular platform. This would apply to a service, such as JUSP, that can provide usage for multiple platforms. <Filter Name=“Platform”>ScienceDirect</Filter>
    7. 7. Filter examples Allows a usage consolidation program to receive and process a smaller report from large content providers Exclude zero-usage items from the COUNTER report. <Filter Name=“ExcludeZeroUsage”>True</Filter>
    8. 8. Filter examples Offers a mechanism to select department or location-level usage reports. Provide usage for a specific department, IP range or other organizational unit. <Filter Name=“Department”>Engineering</Filter> <Filter Name=“Account”>1234</Filter> <Filter Name=“IPRange”></Filter>
    9. 9. Filter Implementation • Completely optional and requires prior understanding between client and server • SUSHI Web Site will create a controlled vocabulary that lists recommended filter names • Requires a new release of the SUSHI standard • Distribution for review and voting later this calendar year
    10. 10. SUSHI Lite A Technical Report and technical proofs of concept that explores evolving SUSHI into a light-weight protocol suitable for exchanging snippets of usage.
    11. 11. SUSHI Lite Request will use the HTTP REST approach common in most current web services. Report=JR1& issn=1084-5453& Begin=2014-01& End=2014-03
    12. 12. SUSHI Lite Response formats supported would be JSON, JSONP or XML with element names and organization based on COUNTER schema.
    13. 13. SUSHI Lite Response formats supported would be JSON, JSONP or XML with element names and organization based on COUNTER schema. <include example> { "Request": { "Report": "JR1", "RequestorID": "test", "CustomerID": "test", "Filters": { "DateRange": "2014-01/2014-03", "ItemID": "issn:1084-5453" }, "Created": "2014-06-26 14:48:34+01:00" }, "Report": { "Vendor": "Oxford University Press", "Platform": "Highwire", "ReportItems": [ { "Identifiers": { "Print_ISSN": "1084-5453", "Online_ISSN": "1930-8892" }, "Publisher": "Oxford University Press", "Type": "Journal", "Name": "Environmental History", "Performance": { "2014-01": {"ft_total": "0"}, "2014-02": {"ft_total": "4"}, "2014-03": {"ft_total": "2"}, } } ] } }
    14. 14. SUSHI Lite Uses: • An alternative metrics site requesting article-level usage for all articles written by an author (oh, did we mention, it will support article level usage) • Discovery service retrieving article-level usage in real- time to show on detailed page • Catalog, journal listing service or acquisitions tool, requesting usage for one journal to show usage in context of the workflow • A publisher retrieving article-level usage from institutional repositories or aggregators for a specific publisher in support of the Journal: Usage Factor
    15. 15. SUSHI Lite Working Group Roster: Alan Stiles The Open University James van Mil University of Cincinnati Libraries Mike Buschman Plum Analytics Miriam Lorenz “Freelancer for Fraunhofer-Gesellschaft e.V. for usage statistics” Oliver Pesch EBSCO Information Services (co-chair) Paul Needham Cranfield University (co-chair) Guy Marjew Elsevier
    16. 16. SUSHI Lite Progress: • Technical report draft is underway – Coordinating the “Filter” list with SUSHI Filters effort • Extensions to the COUNTER XML schema to support article data are being drafted • A working prototype is being developed • Plan to publish results late 2014