Draft SON NR-MA0000-21-00318.pdf

Library Services Platform and Discovery System Statement of Need

NR-MA000-21-00318

June 2021

1. BACKGROUND

The National Oceanic and Atmospheric Administration (NOAA) promotes science, service and stewardship via its mission to: understand and predict changes in climate, weather, oceans and coasts;

share that knowledge and information with others; and conserve and manage coastal and marine ecosystems and resources. From daily weather forecast, severe storm warnings, and climate monitoring to fisheries management, coastal restoration and supporting marine commerce, NOAA’s products and services support economic vitality and affect more than one-third of America’s gross domestic product.

The NOAA Central Library (NCL) is located at NOAA headquarters in Silver Spring, Maryland. It along with its three component libraries - the Atlantic Ocean Marine Laboratory (AOML) Library located in Miami, Florida; the Western Regional Center Library located in Seattle, Washington; and the National Hurricane Center Library located in Miami, Florida - comprise the NOAA Central and Regional Libraries (NCRL), which reports to NOAA’s Office of Oceanic and Atmospheric Research (OAR), Office of Science & Support (OSS). NCL is part of a network of 21 other NOAA Libraries located around the country who serve their local offices and laboratories and comprise the larger NOAA Library and Information Network. The NOAA Library Network is made up of a variety of library types from reading rooms, to solo librarian sites, to University run satellite campuses, to the multi-staffed HQ library in Silver Spring.

NCRL and the NOAA Library Network provide resources and research support to NOAA employees so they are better able to fulfill the mission of the agency. The collections include both print and electronic materials and cover subject areas related to aquaculture, cartography, coastal zone management, ecology, fisheries, hydrography, geophysics, GIS, global climate change, meteorology, ocean/atmosphere interactions, remote sensing, photogrammetry, and water resources.

For decades, the NCL has managed an Integrated Library System (ILS) that provides a collaborative online catalog for items held by the 21 network libraries. The unified collection contains approximately 276,511 items and currently uses SirsiDynix’s Symphony product. The current SirsiDynix ILS includes:

● 165,130 titles (records) that represent 276,511 total items (volumes);

● 12,195 serial records;

● 49,528 e-books;

● 4,632 unique e-journal titles;

● 18 databases;

● 25,000 NOAA Institutional Repository digital objects, hosted in Fedora-based Institutional

Repository.

Because of the variability of size, staffing and function of libraries within the NOAA Library Network, the current ILS has been utilized at different levels and capabilities across the network. This will continue with the new LSP. For example, the discovery layer will be used by some libraries like a traditional ILS to just find items held in one of the NOAA libraries, with others using it to also access NOAA-wide e-resources, and still others to provide access to both their local e-resources and those available NOAA-wide. Similarly, some libraries will utilize the circulation and cataloging functions, while many will not.

The NCRL provides system support personnel and oversight functions for the new LSP. It also has the largest collection of bibliographic records in the catalog, manages e-resources for the Silver Spring HQ staff and those available on a NOAA-wide basis, and will be the primary contact for migration and on-going maintenance of the LSP.

2. OBJECTIVE AND SCOPE

The NOAA Central Library is planning to replace its current legacy system with a cloud-based solution that offers flexibility and interoperability and includes a Library Services Platform (LSP), an Electronic Resources and License Management, and a Discovery Interface that showcases the Library’s print, electronic, digital collections, and a Fedora-based Institutional Repository.

This solution will include:

● An LSP to replace the existing ILS while continuing to support the NOAA Library and Information Network’s 21 library locations;

● An Electronic Resources and License Manager to store and manage electronic resource license terms and conditions; and

● A Discovery System to replace the existing online catalog.

3. REQUIREMENTS & DELIVERABLES

A. Vendor Capacity Requirements

● Demonstrated expertise in supporting similar services;

● Demonstrated history as a trusted partner to libraries and archives (a minimum of 10 years working with libraries);

● Demonstrated history as a trusted partner to mid-large size academic and special libraries.

B. General System and Support Requirements

Below are requirements that should be met by the solution as a whole.

B.1. Architecture, System Updates and Upgrades, and Reliability NOAA Central Library will not consider any client software-based solutions, and will only review cloud-based systems.

Mandatory system requirements are as follows:

• Be completely cloud-based with multitenant architecture-the only exception is for client software for digital asset ingests;

• Be proprietary and not open source;

• Act as a completely functional ILS in its own right, and not be tied to an underlying

ILS in order to function completely;

• Have all modules in full, operational release or, 1-2 minor modules in beta testing with production release planned within 3 months;

• System deliverables shall comply with Section 508 of the Rehabilitation Act of 1973

(29 U.S.C. 794d);

• For the LSP and Discovery systems, roll outs of all upgrades, feature enhancements, updates and fixes for the solution should happen quickly and easily and without intervention by the NOAA Central Library or NOAA IT staff;

• For any required client software, a straight-forward process for installation and upgrades; and

• Ability to provide a schedule of disruptions to services with ample time for the NOAA Central Library to prepare.

Desirable system requirements are as follows:

• Not including scheduled downtime for updates, have a system uptime of at least 99.75%.

B.2. Data Security and Access The system(s) must:

● Be FEDRAMP compliant/authorized, or be able to provide documentation that compliance is anticipated within one (1) calendar year;

● Follow all security and other protocols, and continuous monitoring, as required by FEDRAMP compliance; and

● Allow the Library full access to extracting/exporting its complete set of bibliographic, patron, other data, and digital assets at no additional cost, should the Library terminate its use of the system.

B.3. Integration and Extensibility

The proposed solution must seamlessly integrate the following functions:

● Acquisitions Management;

● Cataloging;

● Circulation;

● Discovery Layer;

● Electronic Resource and License Management;

● Holdings Management;

● Interlibrary Loan;

● Inventory Management;

● Link Resolver;

● Physical Processing;

● Serials Management; and

● Report Management.

B.4 Vendor Support

Training A comprehensive training plan for understanding and using all system functions is required.

This training must include but not be limited to:

● Onsite or webinar-based training on all back- and front-end (patron) system functions;

● Onsite or webinar-based training on both implementation and operation of all functions, tailored specifically to the NOAA Central Library;

● Complete system documentation and training materials (including print and videos) available online; and

● Continuous training after implementation (if webinar-based, available at no extra cost).

Desired training inclusions:

● Printed training and marketing materials for front-end (patron) systems;

● Access to training and marketing materials that the Library can customize and print with its own branding;

● Training materials available as context-based help within each system module.

Help Desk /Customer Support The vendor must:

● Provide support via email, phone, and online;

● Provide a Service Level Agreement that addresses possible responses to support requests;

● Provide an online user group and user group meetings.

Desired help desk support:

● Provide the same level of customer support to all customers, without additional charges for higher levels of support;

● Provide a user community for application programming interfaces (API) and other developments.

System Maintenance and Long-Term Management Requirements and considerations:

● Major and minor system releases must occur on a regular basis;

● Major and minor product updates releases must occur with no or extremely limited assistance from the NOAA’s Library or IT staff;

● Any customizations will be kept intact and unaltered by upgrades and releases;

● The system has long-term feasibility and relevance by tracking trends and technological advancements in the library and archives professions, and incorporating these advancements into the system’s long-range design;

● The solution should be implemented primarily at Academic and Special libraries to ensure that product development is in line with the needs of these library types

- solutions implemented primarily at public and school libraries will not be considered;

● Customers have a strong voice in determining and prioritizing new features and enhancements, and the vendor will solicit and integrate customer feedback and involvement in future system direction.

C. NOAA Central & Network Library Staff Functional Requirements

Staff functions and modules are those that are used exclusively by NOAA Library Staff and comprise Acquisitions Management, Cataloging, Circulation, Electronic Resource and License Management, Holdings Management, Interlibrary Loan, and Serials Management. All functions and modules must integrate seamlessly and be cloud-based.

C.1. Requirements Applicable to All Library Staff Functions

The following requirements are applicable to all back-end/Library Staff functions and the system(s) that handle those functions.

System Integration The system should consist of a single solution that integrates a seamless workflow between systems/functions.

The system must:

● Offer easy-to-implement, seamless, and easy-to-use interoperability between systems/functions;

● Allow staff to move materials easily through the library pipeline, including, but not limited to, selecting, acquiring, cataloging, and circulating;

● Provide workflow automation such as dashboards, reminders, e-mails, and alerts;

and

● Allow library staff to toggle easily between circulation and other staff modules, such as cataloging, acquisitions, and circulations.

Desired system requirements:

● Allow library staff to use modules concurrently, without losing current work data when toggling between modules.

Data Handling The system must:

● Support global changes to entire fields and subfields, and specific strings within fields and subfields in all record types including, but not limited to, order, vendor, bibliographic, circulation, and authority records.

● Include validation routines for order, bibliographic, holdings, item, and authority records;

● Include standard database maintenance reports of the system, including, but not limited to, subject headings, data duplication, etc.;

● Include current and future linked data capabilities; and

● Make data available through documented web services and APIs, including supported data operations (read, write, update, delete, etc.).

C.2. Requirements Applicable to Specific Back End/Library Staff Functions

Acquisitions Management The system must include:

● Basic acquisitions management features such as ordering, receiving, cataloging, etc.

● Integration with book vendors, including the ability to find items for purchase from multiple vendors, and the ability to import complete Machine-Readable Cataloging (MARC) records for ordered items prior to receipt.

Desired system inclusions:

● Capabilities such as library-level budgeting, ability to place, store, and report on orders, financial reporting, vendor records, and a desiderata file;

● In your proposal, please describe how the system complies with this requirement or explain why it does not comply;

● Support for storing and sharing vendor data and the ability to use it in different functional areas;

● The ability to create a brief bibliographic record for ordering purposes, if there is no bibliographic record available; and

● The ability to mark items as “on order” in the bibliographic record.

Cataloging General Cataloging Requirements The solution must provide:

● Support for multiple metadata standards, including MARC, Dublin Core, Metadata Object Description Schema (MODS), and Resource Description & Access (RDA);

● Support for the Library Linked Data model, including the Resource Description Framework (RDF) and BIBFRAME;

● Conversion tools or utilities within the system(s) that translate one metadata schema to another;

● Ability to add local fields to imported records, including, but not limited to, holdings information, shelf location, multiple notes fields, and other proprietary fields;

● Ability to tag items as non-circulating;

● Compatibility with the character unicode transformation formatUTF-8 set;

● Capability of batch addition/deletion/modification of bibliographic and/or item records;

● Ability to create cataloging templates that include only specified MARC fields;

● Include robust search functions for catalog and patrons records:

o Ability to search most data fields.

● Ability to have bibliographic changes (modifications to existing records or new records) visible in the Discovery system within several hours.

Desired solution inclusions:

● Encoding of all bibliographic records in MARC 21 Format for Bibliographic

Data without limitation on record length;

● Full screen MARC editing rather than line by line editing;

● A display of all MARC content designators (field tags, subfield codes, indicators) in the cataloging module, but allow for suppression display of certain designators in Online Public Access Catalog (OPAC)/Discovery module;

● Ability to import and export bibliographic records in MARC 21 with full preservation of all content designators;

● Ability to display and edit diacritics, special characters, and vernacular characters in the appropriate script;

● Ability to batch import and export non-MARC bibliographic records;

● Capability to edit records individually and globally with ability to make those edits within the cataloging module, without having to use any external resources to make global edits;

● Ability to designate a temporary shelf location that automatically reverts to a permanent shelf location after a specified amount of time;

● A link checker to locate/update broken links;

● E-book integration that enables customers to discover and download e-books with minimal clicks;

● Ability to add/delete MARC fields without using a drop box selection item;

● Capability to display all subject subdivisions in subject fields uniformly;

● Ability to move MARC fields up and down within records to change their order of appearance;

● Ability to create cataloging templates that include pre-populated data, including shelf locations and other fields.

● Ability to support keyboard shortcuts in metadata editor;

● Ability to connect to RDA Toolkit within metadata editor;

● Ability to display multiple records in metadata editor;

● Ability to share catalog records between LSP user base members;

● Ability to have multiple location levels per item;

● Ability to tag items for routing to specific patrons when they are received and processed;

● Ability for library staff to view and revert to prior versions of bibliographic records;

● Ability to have holdings changes visible in WorldCat within several hours;

● Include robust search functions for catalog and patrons records:

o Advanced autocomplete and auto suggest functionality;

o Autocorrect and “Did you mean…?” functionality.

Cataloging Authority Control The solution must:

● Allow for the management and maintenance of shared authority files.

Desired solution inclusions:

● Allow seamless access to authority record editing from within the cataloging module;

● Allow for both default authority control practices and the ability to customize these practices;

● Support proprietary authority files of the library’s own creation, and allow for those files to have controlled vocabularies;

● Provide for the editing of authority records individually and globally; and

● Generate SEE and SEE ALSO references from authority records and display them in the Discovery system.

Cataloging Statistics and Reporting The solution must have the:

● Ability to create and save report templates;

● Ability to run reports at various frequencies: monthly, weekly, daily, hourly, on the quarter hour;

● Ability for report to output in multiple formats: tab delimited files, graphs, Excel, HTML, PDF, XML, TXT, and RTF; and

● Ability to produce lists of items by:

o Subject heading;

o Item ID;

o Title;

o Series;

o Additional MARC fields (please list);

o Shelf location;

o Call number or call number range;

o Date cataloged;

o Date published;

o Date last inventoried;

o Item type;

o Call number or call number range;

o Records added over a specific timeframe;

o Records deleted over a specific timeframe;

o Records with broken links;

o Records worked on by specific library staff member(s); and o Records added over a specific timeframe.

Physical Processing The solution must support:

● The processing of physical materials including support for spine-label printing through the solution itself and third party label printing software.

● Barcodes, and integrate with barcode scanners.

Desired solution inclusions:

● The processing of regularly-scheduled and special issues of serials, including receiving, item generation, labeling, and routing.

Serials Management The serials module of the system must:

● Allow for check-in to be based on title or ISSN.

It is desirable that the serials module of the system:

● Have a prediction algorithm for serials;

● Allow for serial record customization for special issues or exceptions;

● Generate statistics from serial records (number of active subscriptions, number of pieces received, etc.);

● Allow for the check-in of multiple instances of a given title; such as a subscription that includes individual issues, bound volumes, pocket parts, pamphlet supplements, etc.; and

● Electronic claims of missing/damaged issues.

Holdings Management The serials module of the system must:

● Have multiple fields available for documenting local holdings in MARC and other cataloging formats;

● Ability to display the Library’s local holdings for items in union catalogs, such as WorldCat or others;

● Support the linking of bibliographic records to other bibliographic records in the catalog.

Circulation and Interlibrary Loan General Circulation Functions The circulation module must include the ability to:

● Create lending rules (by item format, patron group, library location, etc.) and determine levels of access for viewing and manipulating those rules;

● Set due dates, due times, renewal, and hold policies across the system;

● Provide checkout/circulation for “in-house use”, such as for books that are used within the library but not physically checked out - these checkouts simply record use, but do not change any attributes of the record;

● At point of service, retrieve borrower records via specific fields, including borrower name, borrower unique identifier, barcode, etc.;

● Override non-circulating status of items;

● Override circulation policies/time limits at point of checkout or later;

● Change an item’s status without first checking it in (such as marking it

“damaged”);

● Send overdue and other notices multiple times, at intervals that can be customized for different patron and item types.

It is desirable that the circulation module include the ability to:

● Share resources across campuses and allow campus/branch/location to opt out;

● Circulate e-books and other electronic resources, especially those that require proprietary software;

● Provide for automatic renewals of checkouts, unless there is a hold on the item;

● Provide for automated recall notices for books with holds;

● Generate automated staff notifications via e-mail regarding holds, overdue books, and other circulation-related issues using e-mail (for example, when a patron places an ILL or hold request, an e-mail notification is sent to Library staff);

● Suppress overdue notices for specific patrons or items;

● Suppress fine collection feature;

● Provide self-checkout functionality;

● Provide circulation function based on campus/branch/location.

Patron Records, Communications, and Notifications The circulation system(s) must:

● Provide batch import, editing, and deletion of borrower/patron records;

● For patron pin number/library account password, ability to accept alphanumeric sequences of between 4 and 16 characters in length;

● Generate automated patron notifications regarding holds, overdue books, and other circulation-related issues using e-mail;

● Allow for the customization of the language and design of patron notifications.

It is desirable that the circulation system(s) be able to:

● Customize borrower/patron record fields, such as code, name, length and number of fields.

Interlibrary Loan The Interlibrary Loan system must:

● Integrate interlibrary loan directly into circulation workflow by including processing of incoming and outgoing interlibrary loan items within the system such as OCLC ILL;

● Allow ILL from campus/branch/location with ability to locally route, process and receive ILL items at each of the requesting campus/ branch/location (explain how patrons can identify and request items held by other libraries);

● Generate automated patron notifications regarding overdue items, and other ILL-related issues using e-mail;

● Create ILL deflection policies, allowing for certain ILL requests to be immediately rejected without staff intervention based on e-resource license and other policies (explain how patrons can identify and request items held by other libraries)

It is desirable that the Interlibrary Loan system:

● Allow library patrons to identify items of interest outside of the Library’s collections and to initiate ILL requests for those items directly from the Discovery interface (explain how patrons can identify and request items held by other libraries);

● Allow library staff to differentiate between books checked out to local patrons and books checked out for ILL.

Circulation Statistics and Reporting The system must have the ability to:

● Generate the majority of reports within 10 minutes (or some other quantitative measure) (describe how long it takes to view/download different types of reports after running them - differentiate between pre-designed/off-the-shelf reports and custom-designed reports);

● Retain transaction-oriented information indefinitely for statistical reporting purposes, even if the associated item or patron has been removed from the system;

● Toggle on and off the retention of individual book checkout histories, both in aggregate and also at the individual patron level;

● Toggle on and off the retention of individual patron circulation histories;

● Generate ad hoc reports on:

o Number of times an item was circulated;

o Number of times all items/copies in a record were circulated, at an aggregate level, without having to manually aggregate the total circulation of all items/copies in a record;

o Date that an item was last circulated;

o Total number of items circulated in a given time period;

o Circulation activity per patron account;

o Patron checkout history, with ability to toggle this feature on or off;

o Number of items circulated by collection or shelf location;

o Number of items circulated by item type or media;

o Number of interlibrary loan requests and loans;

o Most frequently circulated items;

o Most checked out items;

o Most checked out items, excluding renewals;

o Current books checked out;

o Overdue books; and o Holds.

It is desirable that the system have the ability to:

● Generate borrower/patron reports by any field in the borrower record and by items linked to those records, including user location, office, etc.

● In your proposal, please describe how the system complies with this requirement or explain why it does not comply;

● Automatically alert Library Staff of any transaction errors.

Electronic Resource & License Management and Reporting The system must include:

● Workflow management of electronic resources, such as reminders for renewal or the ability to track new resources from trials through to rollout;

● The ability to manage e-resources via ERM workflows from multiple campuses/branches/locations using a Single Discovery Layer instance, where e-resources licenses vary from library to library

● The ability to manage the following types of administrative information:

(required) o Vendor description;

o Vendor contact information;

o License and contract details, including which fields are available for license and contract terms and how can these be exported and integrated into other areas of the solution;

o Full text of license and contract agreements in their original formats;

o Administrator site URL and credentials for library staff.

(desired) o Track specific license terms and conditions such as allowable use, ILL, and scholarly sharing with information integrated so that it populates the user and/or staff interface;

o User statistics for individual electronic resources, including the ability to automatically pull database usage information from COUNTER-compliant vendors using protocols such as Standardized Usage Statistics Harvesting Initiative(SUSHI);

o Database URL(s) for patrons.

It is desirable that the system include:

● The ability to output electronic resource records for integration into library websites and Discovery systems.

D. Patron-Facing Functional Requirements Patron-facing parts of the solution must:

• Provide a Discovery interface that will be patrons’ primary point of entry into NOAA Central &

Network Libraries print, electronic, and digital collections that are cataloged, where applicable, stored, in the back end;

• Provide a single patron account that includes both Library and Discovery functionality under a single set of authentication credentials including support for SAML 2.0;

• Integrate with authentication account management applications such as EZProzy, OpenAthens, etc.;

• Provide immediate, seamless transfer of item and patron data from the LSP to the Discovery interface, without the need to run reports manually or take any other action to update the Discovery Interface.

D.1 Web Integration and Customization The Discovery system must:

● Be content neutral and allow library staff to designate the order in which vendor-supplied content appears in search results;

● Have a proprietary central index that includes content from a wide variety of vendors (include a list of all vendors/databases that are centrally indexed);

● Allow for indexing of non-MARC data via the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) protocol, including digital objects from the NOAA Institutional Repository (describe how this functionality works, including OAI-PMH requirements for indexing);

● Allow for relevancy ranking of search results, and the ability for the library to customize that ranking;

● Supply APIs, widgets, and other embedded code that allow for the integration of Discovery search forms, canned searches, and other web applications into third party interfaces;

● Provide customization options, including the ability to set default options such as which databases and/or collections are searched (describe which specific fields/sections are customizable directly by Library staff, and which fields/sections can be set with default options);

● Provide branding and styling options (describe any support for branding and styling through CSS, Javascript, and any other web design tools or languages);

● Keep any customizations intact and unaltered by upgrades;

● Provide permanent/persistent links to items;

● Include an OpenURL resolver (describe the OpenURL resolver functionality);

● Provide a responsive mobile application version of the online catalog. The mobile version should have full Discovery functionality.

It is desirable that the Discovery system:

● Provide a test environment/sandbox for customization and upgrades.

D.2 Search

Search Capabilities The following content must be indexed and searchable by the Discovery system:

● Library’s own catalog;

● External OAI-PMH data streams;

● 3rd Party Content Providers, indexed through the Discovery system’s central index, with the ability to toggle on/off specific databases within each vendor database family:

(required) o American Association for the Advancement of Science;

o American Meteorological Society;

o BioOne Complete;

o Cambridge University Press;

o Elsevier ScienceDirect;

o EconLit Full-text;

o JSTOR;

o Nature (Nature, Nature Communications, Nature Climate Change, Nature

Geoscience);

o Oxford University Press;

o ProQuest E-book Central (DDA account);

o SpringerLink;

o Taylor & Francis Online;

o Wiley Online Library (e-books and journals including American Geophysical

Union journals);

o E&E News products (E&E News, E&E Daily, Greenwire, E&E News PM, Climate WIre, Energy Wire) o American Chemical Society o Earth, Atmospheric & Aquatic Science Collection (Aquatic Sciences and

Fisheries Abstracts (ASFA), Meteorological & Geoastrophysical Abstracts

(MGA)

o EBSCO Host (Business Source Premier, Academic Search Complete, EconLit with Full Text, Environment Complete, Computer Source, Newspaper Source, Regional Business News) o HeinOnline;

o Lexis Advance;

o Westlaw;

o Web of Science.

The following content is desirable to be indexed and searchable by the Discovery system:

● Extended catalog (such as holdings from a union catalog, the LSP’s customer base, the Library of Congress).

Search Functionality The search functionality of the Discovery system must:

● Allow for the customization of the number of fields that can be searched and limits that can be set on each field.

● Include both a single search box, and an Advanced Search that allows user to search by:

(required) o Abstract;

o Author;

o Collection (for digital repositories or special collections);

o Date Range and discrete dates;

o Format;

o ISBN/ISSN;

o Journal Name/Publication Title;

o Keyword;

o Language;

o Location;

o Shelf Location;

o Subject;

o Title of Item;

o Title of Publication.

o Availability (real time);

o Call number;

o Full Text Availability;

o Publisher;

o Other customizable fields (list).

● Include expert searching features, such as Boolean logic, for researchers who require more control in formulating search statements;

● Include advanced autocomplete and auto suggest functionality.

It is desirable that the search functionality of the Discovery system:

● Include autocorrect and “Did you mean…?” functionality.

Search Results Display and Limiting When displaying and limiting search results, the Discovery system must:

● Allow for certain bibliographic records to be suppressed in the Discovery system, but visible to library staff in the LSP;

● Provide de-duplication of redundant search results;

● System should be compatible with the UTF-8 character set.

● Display a results list page that shows the following information per item/record:

o Author/Contributor;

o Availability and holdings (state if the results display included items from libraries outside of the library’s system);

o Brief summary/description;

o Book jacket art (small or thumbnail size);

o Call number;

o Date published;

o Links to various editions/formats of the item;

o Links to full text, digital object record, or an external URL from the 856 field;

o Location;

o Media type;

o Title.

● Allow user to limit/refine search results by the following facets/filters:

o Author (Personal and Corporate);

o Collection(s), including digital repositories and special collections;

o Content type: news articles, book reviews, reports, etc.;

o Database(s);

o Date, including ability to limit by date range or specific integrals (6 months, 1 year, 5 years, etc.);

o Format, including the ability to limit by print book or e-book;

o Full Text;

o Journal Name;

o Language;

o Series;

o Shelf Location;

o Subject/Topic;

o Other customizable fields (describe any additional fields that can act as search limits and the Library’s ability to configure which fields are used as limits).

● Display an item description page that shows the following information per result:

(required) o Add to personalized list functionality;

o Author;

o Availability and holdings;

o Book jacket art (displayed at a larger size than in the results list);

o Call number;

o Description;

o For articles, link(s) to full text;

o Links to all editions/formats/versions;

o Media type;

o Permalink;

o Print/cite/send options;

o Title.

(desired) o Book reviews (both professional and user-generated);

o For periodicals, the latest issue received;

o Recommended reading;

o Sample context, such as the first chapter of a book;

o Table of contents;

o User-created subject tags;

o User-created lists.

● Allow users to sort results by relevancy, publication date, title, author, or collection;

● Near seamless e-book integration (the user clicks on the e-book title, and gets directly to the full-text e-book within 1-2 clicks) including Demand Driven Acquisition Packages.

When displaying and limiting search results, it is desired that the Discovery system:

● Display diacritics, special characters, and vernacular characters in the appropriate script;

● Group different manifestations of the same record together in a single grouping of records;

● Allow user to conduct a virtual browse with “view nearby items on shelf” type functionality;

● Allow library staff to view a MARC record for the item within the Discovery layer;

● Integrate with Springshare’s LibGuides and LibCal products (describe all available integrations, and any actions the library must take to enable these integrations).

D.3 User Personalization and Interaction

User Discovery Accounts Patron/end user Discovery system accounts must:

● Allow patrons to create their own Discovery accounts, but allow Library staff to toggle this feature on/off;

● Include an “I forgot my password” email reset feature

● Allow for combined patron Discovery and Library accounts

● Give Library Staff the ability to pull periodic reports of new self-registrants

● Allow patrons to create and save, print, share, or export single items or lists of items to citation management, word processing or other productivity software.

It is desired that Patron/end user Discovery system accounts:

● Limit patron account creation format to a specific alphanumeric length and style;

● Offer the capability of creating and retaining customized queries/search strategies when logged into the system - for example, patrons can create folders for frequent searches.

● In your proposal, please describe how the system complies with this requirement or explain why it does not comply;

● Alert authenticated patrons to newly cataloged items via RSS or e-mail alerts.

● In your proposal, please describe how the system complies with this requirement or explain why it does not comply;

● Allow authenticated patrons to create personal booklists with the option to share them.

User Library Accounts Patron/end user Library accounts must:

● Provide authenticated patron access to accounts in order to view, renew, and track requested or checked out items;

● Allow patrons to place holds on items;

● Enable patrons to borrow or request tangible items from the NOAA Central &

Network Library’s collections;

● Allow patrons to initiate requests for items from other libraries directly through the Discovery Interface;

● Allow patrons to see hold/request queue for both in-house and ILL items;

● Allow patrons to receive e-mail notifications about the status of held items and allow library staff to customize the language of these notifications;

● Allow library staff to disable Fine/Fee information from patron view.

E. Implementation Requirements / Deliverables

A detailed timeline, plan, and recommendations for migration of data (bibliographic, patron, and circulation records for approximately 165,130 titles/records representing 276,511 items (volumes) from the Library’s current Sirsi Symphony system into the new LSP will be requested when the requirement is solicited. The NOAA Central & Network Libraries currently have 21 library locations and approximately 42 shelving locations.

E. Implementation Requirements / Deliverables