Download to read offline
NISO Standards and Best Practices: Standardized Usage Statistics Harvesting Initiative (SUSHI)
This document discusses the Standardized Usage Statistics Harvesting Initiative (SUSHI), which was developed through NISO to allow automated retrieval of COUNTER usage reports. It describes how SUSHI was created to address the problems of downloading many Excel reports, and how NISO provided a neutral forum and processes to develop the SUSHI standard. The standard was successfully implemented and adopted, and NISO continues to support SUSHI through maintenance, infrastructure, and promoting interoperability.
More Related Content
Similar to NISO Standards and Best Practices: Standardized Usage Statistics Harvesting Initiative (SUSHI)
More from National Information Standards Organization (NISO)
NISO Standards and Best Practices: Standardized Usage Statistics Harvesting Initiative (SUSHI)
- 1. NISO Standards andBest Practices: Standardized Usage Statistics Harvesting Initiative (SUSHI) Oliver Pesch Chief Strategist, e-Resources EBSCO Information Services opesch@ebsco.com April 4, 2012 1
- 2. Standardized Usage Statistics HarvestingInitiative (SUSHI) • One of the first standards initiatives to use NISO’s more agile standards development process • Focus on solving the core problem • Allow the standard to evolve through ongoing maintenance 2
- 3. The problem… • It’s2005… – ERM systems are new and – COUNTER allows for standard usage reports – Very promising for managing usage of “e”! • But… – Excel-based reports were not really standard – Downloading dozens/hundreds of usage reports not really scalable 3
- 4. What happened next… •Tim Jewell, Adam Chandler, Ted Fons and Oliver Pesch met at ALA in the summer of 2005 • The vision was to create an automated mechanism for retrieving reports • Success of this initiative hinged on having the support of a larger organization 4
- 5. Why take theproblem to NISO… • NISO is about information standards • Synergy with the ERMI/DLF work of which this problem was an off-shoot • NISO offered the processes, the infrastructure and the support • NISO offered the neutral ground where interested parties could work collaboratively 5
- 6. What was achievedthrough NISO… • Committee formed in late 2005 • Work began in early 2006 • Draft standard published in 2007 • Final standard approved in 2008 6
- 7. The result… • Arequest/response protocol that allows automated retrieval of COUNTER reports • SUSHI has been a success – It’s central to virtually all usage consolidation applications – Adopted by approximately 40 content providers – SUSHI support is now a requirement for COUNTER compliance 7
- 8. Why it worked… •NISO offered a neutral forum for collaboration and exchange of ideas 8
- 9. Why it worked… •SUSHI was established as a continual maintenance standard – A standing committee was formed and meets monthly – Respond to feedback from the community – If necessary, adjustments can be made to the standard 9
- 10. Why it worked… •NISO SUSHI Standing Committee serves as maintenance agency for COUNTER XML Schema – COUNTER XML is integral to SUSHI – COUNTER recognized the need for formal and controlled maintenance of their schema – COUNTER sees NISO as a trusted partner 10
- 11. Why it worked… •NISO provided the infrastructure and support for ongoing maintenance and advocacy – NISO SUSHI website – SUSHI developers listserv – Hosting site for official schemas – Communication channels through NISO Newsline and ISQ 11
- 12. And the workcontinues… • Promoting interoperability – Providing developer tools and FAQs through the NISO web site – Published the SUSHI Server Test Mode recommended practice – Working on a SUSHI Server Status Report 12
- 13. And the workcontinues… • Preparing for Release 4 of the COUNTER Code of Practice – Adjusting the COUNTER Schemas to support new reports and metric types – Updating support material on the SUSHI web site (report registries, controlled vocabularies, “what’s new” documents, FAQs, etc) – Publishing the COUNTER SUSHI Implementation Profile 13
- 14. Conclusion… • SUSHI hasbeen a success but needs ongoing support, maintenance and advocacy • NISO provides the credibility, processes and infrastructure necessary for standards like SUSHI to succeed 14
- 15.
Editor's Notes
- #3 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #4 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #5 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #6 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #7 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #8 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #9 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #10 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #11 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #12 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #13 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #14 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to
- #15 SUSHI…The problem being solvedCOUNTER usage reports came about in the early days of ERM systemsOpportunity to use COUNTER to integrate usage with ERMDidn’t work! Not “standard”… Not scalealeWho was involvedTed and Adam started… meeting with me and Ted Koppell (Ex Libris)…Why was it brought to NISONeeded a neutral place to work through details… required cooperation between competitive ERM systems and content providers also needed to work together.What was NISO able to accomplishVery successful… the committee was able to focus on the root problem (did not get distracted with non-essential details and future gold plating)Developers at EBSCO, Innovative, Serials Solutions, Project Euclid built prototype technology – proved it could workFast track through NISO – one of the fastest initiatives from concept to trial useCOUNTER reports are the foundation… NISO’s structure and organization allowed COUNTER to trust NISO to act as the maintenance agency for the COUNTER XML schemasWhere has it gone from here – why is NISO important in care and feeding…Like the first release of almost everything, issues came to the forefront as implementations happened.It turned out that the SUSHI standard is not so much the issue as the how it is being implemented. Flexibility (vagueness) in the standardSince it relies on COUNTER reports, NISO was able to