CR2 Blog the knowledge blog
  • scissors
    November 26th, 2008LISWire aggregatorLISWire

    The Information Use Management
    & Policy Institute
    at Florida State University has been awarded a grant
    to examine how libraries, responders and communities have united to better
    prepare for and recover from hurricanes. 
    Public libraries can play an important role in each phase of hurricane
    season’s lifecycle.  One way of dividing
    the hurricane lifecycle is offered by the Federal Emergency Management Agency (FEMA)
    in a guide entitled “Producing
    Emergency Plans
    The guide identifies
    four primary phases of the emergency management as: mitigation, planning, response, and recovery.  To provide
    librarians with a better appreciation of the scope of activities which could
    surround a comprehensive hurricane preparedness program, each of those phases are
    briefly explained.

    Hurricane preparedness is not a single event. It is a set of interrelated activities, which extends from the initial design of the library structure, through the recovery and rebuilding efforts to reestablish the library as a fully functional community asset. Activities within this emergency management chain of events include:

    Mitigation – Mitigation refers to reducing the impacts a hurricane will have on library collections, services and on the communities the library serves. Recent studies, as “The 2004 and 2005 Gulf Coast Hurricanes: Evolving Roles and Lessons Learned for Public Libraries in Disaster Preparedness and Community Services”, indicate that during hurricane events, libraries may become rescue and recovery centers. Public libraries may provide vital community services, supporting the public’s need for information, communication, internet connectivity, and also assists in the coordination of recovery operations in the local area. In order to offer hurricane continuity of service and meet emergency demands, public libraries’ service and facilities infrastructure need to be carefully planned to resist the impact of hurricanes. The Disaster Mitigation Planning Assistance Website provides a wealth of information for cultural institutions, including libraries, museums, historical societies and archives, providing recommendations that will help mitigate damage to collections in the event of a disaster.

    Planning – Planning is essential to assuring a high level of readiness and in addressing the crises conditions that surround an emergency event, such as a hurricane. Public libraries need to be at the table as local emergency responders develop and refine disaster plans. Within the public library, the preparation of informative documents, policies, online and web based services/resources, and operational plans that identify the emergency procedures are critically important. Such plans allow an organized and efficient reaction during a time of crisis. Such internal planning also helps librarians communicate and coordinate with responders at the local, state, and national levels. Librarians may wish to check out the disaster response plans and other emergency planning materials offered on the California Preservation Program website.

    Response – This segment of the chain begins with the notification that a hurricane strike is imminent and continues through the event, until the end of the emergency. During this period of time, the library’s exterior and interior assets must be secured and protected from the impending danger. The library may be transformed to enable emergency service provision. This means securing necessary resources, reallocation of staff and increased flexibility. The public library will become an active emergency organized to meet the high demand for communications, services, and support activities required by the emergency response teams and the public’s need for crisis information. A good example of a Library Disaster Response Plan is provided by the Cornell University Library.

    Recovery – Recovery is the period after the hurricane event where the library and community begins to react to the aftermath of the events and takes initial steps to return to normal operations and services. Library damages must be identified, assessed, and repaired. The library must assist the community to do the same with homes and business repairs. The Disaster Recovery for Public Records Custodians, Archives and Libraries website offered by the State Library of Florida provides many recovery related resources in the areas of records recovery, storage, media repair, and provides general conservation advice. SOLINET offers classes and training for library staff, preservation services, consulting, and recovery related electronic resources and library products. The SOLINET corporate brochure provides an overview of what SOLINET can offer you and your library.

    As we learn from these experiences, the knowledge gained must be used to improve how the library can better prepare for future emergencies. A formal assessment of how the library and staff survived the disaster can help identify how the library can better serve the community in the future should a similar disaster occur.

    How You Can Help: Do you and your public library have experience assisting your community prepare for and recover from a hurricane? How do these above phases compare to your experiences? Please send an email to Project Manager, Joe Ryan with any thoughts you may have. By offering and describing your preparedness and response efforts, and related experiences, you will help to identify a set of best practices that will help all libraries and communities more effectively work together during emergencies situations. See our project summary, article, or radio interview for further information.

  • scissors
    November 26th, 2008LISWire aggregatorLISWire

    The SUSHI (Standardized Usage Statistics Harvesting Initiative) standard (ANSI/NISO Z39.93 - 2007) defines an automated request and response model for the harvesting of electronic resource usage data, utilizing a Web services framework. Designed as a generalized protocol extensible to a variety of usage reports, it also contains an extension designed specifically to work with COUNTER usage reports. COUNTER reports have become a mainstay of collection analysis for many libraries; SUSHI serves to automate the time consuming and error prone process of manually running, retrieving and loading these reports.

    NISO's SUSHI Standard Advisory Committee, formed last summer to maintain the standard, has used community feedback to identify additional needs for implementation and to examine the standard for areas that may need updating or improving. In addition to addressing the needs of the schemas, the Committee's charge also includes the goal of making SUSHI easier for implementers to understand and work with. As part of that effort, the schemas have been annotated with descriptions and examples for key elements, and the website (
    ) now includes clear graphical representations of the schemas. In addition, the FAQs on the site are being updated and include sections specifically for librarians and for developers. Further documentation on the site includes material covered in NISO's SUSHI webinar on October 2, a list of clients (ERM and Usage Consolidation services) supporting SUSHI, and a list of SUSHI compliant content providers, and other supporting information.

    Also on the site is a link to the draft, "How to Start Building a SUSHI Service." This work in progress by Thomas Barker, Software Engineer, IT and Digital Development at the University of Pennsylvania Library, is a valuable tool for those interested in getting started with building a client.

    /Background and Technical Details/
    Launched in 2002, COUNTER is designed to help librarians and publishers in the recording and exchange of usage statistics for electronic resources. By following COUNTER's Code of Practice, vendors can provide libraries with data using standardized formats and data elements. The SUSHI protocol is a SOAP (Simple Object Access Protocol) request/response Web services "wrapper" for the XML version of COUNTER reports.

    In the protocol, a transaction begins when a client service running as part of an application developed by a library or running as part of a usage data consolidation service or ILS/ERM identifies itself, identifies the customer whose statistics are being requested, and specifies the desired report to the SUSHI server service running at a data provider. In response, the server provides the report in XML format, along with the requestor and customer information or an appropriate error message. The SUSHI developers envision a system in which the client system is programmed to retrieve reports automatically for all the COUNTER-compliant vendors with which the library does business.