Attachment J3_ CGPM DiscoverGov Func-Reqs Appd_A.pdf

U.S. Government Publishing Office

CGPM-DiscoverGov Functional Requirements

Revision 4 2-2-2026

U.S. Government Publishing Office Integrated Library System Functional Requirements 02/02/26

Integrated Library System Functional Requirements Documentation

Contents Introduction

Background

Objective

Acronyms, Initialisms, and Names

Integrated Library System Components

Glossary

DiscoverGov Integrated Library System Functional Requirements

Introduction The U.S. Government Publishing Office (GPO), through its Library Services & Content Management division (Superintendent of Documents), is gathering information on acquiring, implementing, maintaining, and supporting a high-performance integrated library system. The existing ExLibris Aleph Integrated Library System (ILS) is essential for GPO’s Library Services & Content Management to achieve their mission of improving services for Federal Depository Libraries and the public. To enhance these efforts, we are aiming to modernize and upgrade our library system, which supports the Catalog of U.S. Government Publications (CGP).

This information overview outlines the fundamental functional requirements for a replacement system designed to meet both current and future workflow needs. It also ensures continued support for the mission of Library Services & Content Management.

Background Library Services & Content Management (LSCM) aims to inform the American public by managing four mandated programs that support federal information lifecycle management across various formats:

Federal Depository Library Program Cataloging and Indexing Program International Exchange Service By-Law distribution services

To improve access to federal information, the Government Publishing Office (GPO) is seeking a modern Integrated Library System (ILS) or Library Platform Service (LPS). The current ILS supports online services for federal libraries and the public, enabling distribution and preservation of government publications for all federal branches. GPO centralizes production and provides publications free through the Federal Depository Library Program.

The ILS enhances public access with features like a web-based catalog, timely publication updates, replacement of manual catalog production, and MARC record creation in partnership with OCLC.

The system is built on Ex-Libris software and hosted on a FedRAMP-certified platform, supporting about 500 simultaneous users and maintained via Cloudflare security.

Aleph software integrates with Oracle database servers across test, production, and disaster recovery environments on Red Hat Enterprise Linux. GPO staff manage data using a Windows-based client; current Aleph tools lack browser-based access for metadata staff. The ILS holds over one million records updated daily.

The Catalog of U.S. Government Publications (CGP) serves as the main tool for finding electronic and print publications from all government branches, hosting descriptive records dating back to the late 1800s and providing direct links to online materials.

CGP Scope:

- Bibliographic information for new and historic Government Publications dating back to the late 1800s

- Over one million bibliographic records generated since July 1976

- Over 275,000 links to official full-text electronic titles

- Updated daily

CGP Features:

The staff at GPO are committed to providing access to government documents while ensuring the intellectual integrity of the materials. Some of the features provided by the CGP are:

Direct links to the official digital version of a publication when available via PURLs (Persistent Uniform Resource Locators)

A robust search engine with extensive search features including:

o Multiple search types: Basic, Advanced, Browse, or Expert

Boolean Quoted Truncated Parenthetical Common Command Language (CCL) o Instructions for maximizing the effectiveness of each search type Catalogs to Search: curated subsets such as the Congressional Serial Set and Electronic

Titles New Titles with dedicated Dynamic Searches and Monthly Archive Reports An integrated email feature that enables sending up to 20 records at a time for future use Federal Depository Library Coordinators have access to Z39.50, CGP logged in features such as special views, special services such Selective Dissemination of Information (SDI), saving and managing records, as well as others.

GPO PURLs:

Since March 1998, the U.S. Government Publishing Office (GPO) has used Persistent Uniform Resource Locators (PURLs) to provide stable links to online Federal resources. If a user clicks on a PURL, the request will be routed to the Federal publication. GPO staff modify PURL entries as the location of the Federal information changes, and GPO’s PURL server will route traffic to the appropriate Web site. GPO staff in our Office of Archival Management (OAM) and Library Technical Services (LTS) performs routine maintenance on PURLs and their bibliographic records.

GPO Metadata Standards:

GPO is the authoritative source for descriptive and subject cataloging for Federal Government documents. GPO’s Library Technical Services (LTS) creates bibliographic records that adhere to the national and international standards, as well as local GPO guidelines and practices:

- Resource Description and Access (RDA)

- Library of Congress-Program for Cooperative Cataloging Policy Statements (LC-PCC PS)

- Library of Congress Subject Headings Manual

- MARC 21 Format for Bibliographic Data

- MARC 21 Format for Authority Data

- ANSI/NISO Z39.71-2006 (R2011) Holdings Statements for Bibliographic Items

- MARC 21 Format for Holdings Data

- OCLC Bibliographic Formats and Standards

- Program for Cooperative Cataloging (PCC) guidelines (including BIBCO, CONSER, NACO, and SACO)

- GPO Cataloging Guidelines

- Other standards as appropriate

- Also working towards using BIBFRAME

In October 2017, GPO started posting cataloging records on its GitHub repository. The CGP on GitHub is a location where users may freely download record sets extracted from the CGP. MARC record files are offered in UTF-8, MARC-8, and MARCXML formats.

Through 2021, the ILS integrated with our Federal Depository Library Directory (FDLD), which was managed as a service of the CGP as an independent MySQL database that interfaces with the CGP to create and maintain accounts for the over 1,000 FDLs. It also, provided the ability to Locate Libraries via an integrated link contained within the bibliographic record which opens a search interface that imports the title and GPO Item Number from the bibliographic record allowing the user to search by City or State to locate their nearest FDL. The "Locate a Library" feature within each record allowed users to find a nearby Federal depository where a particular publication or expert assistance could be found.

Objective This procurement seeks a modern, sustainable technical solution to upgrade the library system, supporting GPO’s goals of improved processes, enhanced security, and legacy system elimination in a cost-effective way.

The required system is an online, real-time platform with a graphical interface for catalog access to all print and digital materials, including external electronic databases. It Should be interoperable with other systems, hosted on a FedRAMP-certified platform or SaaS, offer geographically separated backups, and support Test, Development, Production, and Disaster Recovery environments.

Acronyms, Initialisms, and Names

AACR Anglo-American Cataloging Rules

AACR2 Anglo-American Cataloging Rules, Second Edition

ACSIS Acquisitions Classification and Shipping Information System

API Application Programming Interface

ASCII American Standard Code for Information Exchange

BIBCO [monographic] Bibliographic Record Cooperative Program

BIBFRAME Bibliographic Framework

C&I Cataloging and Indexing program

CCL Common Command Language

CCO Cataloging Cultural Objects

CD-ROM Compact Disc Read-Only Memory

CGI Common Gateway Interface

CGP Catalog of U.S. Government Publications

COTS Commercial Off-the-Shelf

CIP Cataloging in Publication

CONSER Cooperative Online Serials Program

COOP Continuity of Operations

CRDP Cataloging Record Distribution Project

CGP Catalog of U.S. Government Publications

CSV Comma Separated Value (file extension .csv)

DC Dublin Core

DDC Dewey Decimal Classification

DR Disaster Recovery

DSIMS Depository Management System

EAD Encoded Archival Description

ECIP Electronic Cataloging in Publication

EL Electronic (often used at GPO to refer to Electronic records)

FDL Federal Depository Library

FDLD Federal Depository Library Directory

FDLP Federal Depository Library Program

FedRAMP Federal Risk and Authorization Management Program

FIPNet Federal Information Preservation Network

FTP File Transfer Protocol

FISMA Federal Information Security Management Act

FRBR Functional Requirements for Bibliographic Records

GPO U.S. Government Publishing Office (formerly U.S. Government Printing Office)

GUI Graphical User Interface

IES International Exchange Service

ILS Integrated Library System

ISBN International Standard Book Number

ISO International Organization for Standardization (name not an acronym)

ISSN International Standard Serial Number

JCP Joint Committee on Printing

JSON JavaScript Object Notation

LC Library of Congress

LCC Library of Congress Classification

LCGFT Library of Congress Genre/Form Terms

LCRI Library of Congress Rule Interpretations (interprets AACR/2/ and RDA cataloging standards)

LCSH Library of Congress Subject Headings

LoC List of Classes

LOE Level of Effort

LSCM Library Services and Content Management

LSP Library Service Platform

LSS Library Services System

MADS Metadata Authority Description Schema

MARC Machine-Readable Cataloging

MARC 21 Machine-Readable Cataloging (current MARC standard name)

MARCXML Machine-Readable Cataloging extendible Markup Language

MeSH Medical Subject Heading

METS Metadata Encoding and Transmission Standard

MoCat Monthly Catalog of U.S. Government Publications

MODS Metadata Object Description Schema

MRC Machine Readable Cataloging format (file extension .mrc)

NACO Name Authority Cooperative Program

NARA National Archive and Records Administration

NASA National Aeronautics and Space Administration

N&O Needs and Offers

NET New Electronic Titles

OAI-PMH Open Archives Initiative Protocol for Metadata Harvesting

OAIS Open Archival Information System Reference Model

OCLC (Name no longer initialization; formerly: Online Computer Library Center, etc.)

OPAC Online Public Access Catalog

ONIX Online Information eXchange

PCC Program for Cooperative Cataloging (umbrella for BIBCO, CONSER, NACO, and SACO)

PDF Portable Document Format

POD Print on Demand

PPA Permanent Public Access

PREMIS Preservation Metadata: Implementation Strategies

PURL Persistent Uniform Resource Locator

RD Requirements Document

RDA Resource Description and Access

RDA 3R Resource Description and Access Toolkit Restructure and Redesign Project

RDF Resource Description Framework

RFI Request for Information

RFP Request for Proposal

RHEL Red Hat Enterprise Linux

SACO Subject Authority Cooperative Program

SF1 Standard Form 1

SOW Statement of Work

SuDoc Superintendent of Documents (implies classification number)

SuDocs Superintendent of Documents

TCP/IP Transmission Control Protocol/Internet Protocol

TDR Trustworthy Digital Repository

UAT User Acceptance Testing

UTF-8 Unicode Transformation Format – 8-bit

URI Uniform Resource Identifier

URL Uniform Resource Locator

URN Uniform Resource Name

USC/U.S.C. United States Code

USMARC Machine-Readable Cataloging (previous MARC standard name)

VIAF® Virtual International Authority File

WTN WebTech Notes

XML extendible Markup Language

XSL extendible Stylesheet Language

Integrated Library System Components

1.0 Major Components

General Area

1.0 General

Priority New

Feature/ Function

1.0.1 The system shall support 508 compliances across all

modules and interfaces

Should NF

1.0.2 The system shall support responsive design for use

on mobile devices such as cell phones or tablets

Should NF

1.0.3 The system shall support responsive design for use

on mobile devices such as cell phones or tablets across all data entry modules

Should NF

1.0.4 The system shall support responsive design for use

on mobile devices such as cell phones or tablets across internal interfaces

Should NF

1.0.5 The system shall support responsive design for use

on mobile devices such as cell phones or tablets across external interfaces

Should NF

1.0.6 The system shall support a mobile app with

customizable functions across data entry modules for multiple user classes

Should NF

1.0.7 The system shall support single sign-on across all

modules and interfaces based on user class

Should NF

1.0.8 The system shall support printing records from any

data entry module from user workstations

Should

1.0.9 The system shall support printing records from any

internal interface from user workstations

Should

1.0.10 The system shall support printing records from any

external interface from user workstations

Should

1.0.11 The system shall support printing reports from any

module or view from user workstations

Should

1.0.12 The system shall support the ability to make global

changes across all data entry modules

Should

1.0.13 The system shall support union catalog capabilities Should NF

1.0.14 The system shall support searching any data

element across all data entry modules Should

1.0.15 The system shall have full Boolean search capability

on all MARC fields across all data entry modules

Should

1.0.16 The system shall not restrict the number of

bibliographic, holdings, or item records that can be added to the system across all data entry modules

Should

1.0.17 The system shall not restrict the number of

bibliographic, holdings, or item records that can be viewed in the system across all data entry modules

Should NF

1.0.18 The system shall not restrict the number of

bibliographic, holdings, or item records that can be viewed in the system any internal interfaces

Should NF

1.0.19 The system shall not restrict the number of

bibliographic, holdings, or item records that can be viewed in the system any external interfaces

Should NF

1.0.20 The system shall allow for the migration of all data

elements including notes fields and local fields to future systems

Should

1.0.21 The system shall support allow for the migration of

the current "system number" as the unique identifier for bibliographic data system wide

Should NF

1.0.22 The system shall have equal functional capability if

accessed from either a client or web-based system

Should NF

1.0.23 The system components, record database, search

engine, client interface, and web interface shall be designed as an integrated system

Should

1.0.24 The system shall support the ability to have local

customized settings across all modules and interfaces

Should NF

1.0.25 The system shall support the ability to be updated

without or with minimal impact to local customized settings

Should

1.0.26 The system shall support the ability to retain local

customized settings after vendor updates

Should

1.0.27 The system shall support the ability to restore local

customized settings after vendor updates

Should

1.0.28 The system shall support the ability to enable users

to customize toolbars

Should NF

1.0.29 The system shall support the capability to manage

eresources, such as online databases

Should

1.0.30 The system shall log and maintain the date/time

stamp when new records are added across all data entry modules

Should

1.0.31 The system shall log and maintain the date/time

stamp when changes are made to the data across all data entry modules

1.0.32 The system shall log and maintain user information

when new records are added across all data entry modules

Should

1.0.33 The system shall log and maintain user information

when changes are made to data across all data entry modules

Should

1.0.34 The system shall provide the capability to search for

and retrieve content from the system

Should

1.0.35 The system shall provide the capability to search and

retrieve unstructured content such as text

Should

1.0.36 The system shall provide the capability to match

character strings such as search exact phrases

Should

1.0.37 The system shall provide the capability to search and

retrieve structured content such as fielded text/data

Should

1.0.38 The system shall provide the capability to search by

any indexed field

Should

1.0.39 The system shall provide the capability to search

across multiple internal content simultaneously and separately

Should

1.0.40 The system shall allow users to the ability to search

without any case sensitive operators

Should

1.0.41 The system shall provide a search interface that

allows users to submit queries to the system and receive results across all data entry modules

Should

1.0.42 The system shall provide a search interface that

allows users to submit queries to the system and receive results in all interfaces

Should

1.0.43 The system shall have the capability to receive and

record existing data from sources external to the system

Should

1.0.44 The system shall have the capability to automatically

record system data information about the actions performed by the system on content

Should

1.0.45 The system shall log all additions, deletions, and

changes to content within the system

Should

1.0.46 The system shall have the capability to perform

accessibility assessments

Should NF

1.0.47 The system shall have the capability to allow users to manually perform 508 accessibility assessments on content

Should NF

1.0.48 The system shall provide the capability to assign

deadlines for system jobs

Should

1.0.49 The system shall provide the capability to assign

deadlines for system activities

1.0.50 The system shall provide the capability to suspend

system activity/job instances

Should

1.0.51 The system shall provide the capability to resume

system activities/jobs

Should

1.0.52 The system shall provide the capability to cancel

system activities/jobs

Should

1.0.53 The system shall support the capability to change the

key parameters affecting the operation of the system without redesigning the system

Should

1.0.54 The system shall support the capability to

accommodate changes in hardware technologies without requiring major reengineering or design changes

Should

1.0.55 The system shall support the capability to

accommodate changes in processes without requiring major reengineering or design changes

Should

1.0.56 The system shall support the capability to

accommodate changes in policies without requiring major reengineering or design changes

Should

1.0.57 The system shall support the capability to

accommodate changes in personnel without requiring major reengineering or design changes

Should

1.0.58 The system shall support a staging area for metadata Should

1.0.59 The system shall allow for customizable notes across

all data entry modules Should

1.0.60 The system shall allow for customizable internal

notes across all data entry modules

Acquisitions Component Area

1.1 Acquisitions

Function

1.1.1 The system shall have an integrated acquisitions

data entry module

Should

1.1.2 The system shall allow for acquisitions processes Should

1.1.3 The system shall allow for acquisitions data Should

1.1.4 The system shall allow for Agencies as vendors Should

1.1.5 The system shall allow for Bureaus as vendors Should

1.1.6 The system shall allow creation of vendor records Should

1.1.7 The system shall allow editing of vendor records Should

1.1.8 The system shall allow deleting of vendor records Should

1.1.9 The system shall allow viewing of vendor records Should

1.1.10 The system shall allow for monograph orders Should

1.1.11 The system shall allow for serials orders Should

1.1.12 The system shall allow for serials subscriptions Should

1.1.13 The system shall allow for the ability to change order types such as from monograph to serials Should

1.1.14 The system shall allow for the ability to get statistics for orders

Should

1.1.15 The system shall allow for the ability to get statistics for orders types

Should

1.1.16 The system shall allow for the ability to get statistics for subscriptions

Should

1.1.17 The system shall allow for the ability to display data types across all data entry modules

Should

1.1.18 The system shall allow for flexibility in relinking

orders to bibliographic records of any type such as monograph or serials

Should

1.1.19 The system shall allow for customizable open orders

report

Should

1.1.20 The system shall allow for customizable open orders

notifications

Should NF

1.1.21 The system shall allow claims to be set up Should

1.1.22 The system shall allow claims to be set up with the

ability to indicate frequency Should

1.1.23 The system shall have the ability to batch close

orders

Should

1.1.24 The system shall support the ability to check for

order receipts

Should

1.1.25 The system shall track arrivals of orders Should

1.1.26 The system shall search/report order arrival data Should

1.1.27 The system shall report open orders Should

1.1.28 The system shall report past due orders Should

1.1.29 The system shall support the ability to allow for

creation of special blanket orders Should

1.1.30 The system shall support the ability to allow for

editing of special blanket orders

Should

1.1.31 The system shall support the ability to create custom

reports with granular permissions based on user class

Should NF

1.1.32 The system shall allow for the ability to transfer

orders

Should

1.1.33 The system shall allow for the ability to allow for

creation of standing orders

1.1.34 The system shall allow for the ability to allow for

editing of standing orders

Should

1.1.35 The system shall allow for orders be grouped by

material format such as CD-ROM

Should NF

1.1.36 The system shall allow for the ability to change a

previous tangible order to a print on demand or digitized conversion order

Should NF

1.1.37 The system shall allow for the ability to create a

new/duplicate order for a different format

Should

1.1.38 The system shall allow for the creation of multiple

internal acquisitions notes

Should NF

1.1.39 The system shall allow for editing of internal

acquisitions notes

Should

1.1.40 The system shall allow for the ability to notify

internal user classes of specific notes

Should NF

1.1.41 The system shall allow for the ability to expand note

field view/window

Should NF

1.1.42 The system shall allow for the ability to configure

specific notes to trigger an alert to popup for applicable materials

Should NF

1.1.43 The system shall allow for the ability to configure

specific notes to trigger an alert to popup for applicable materials when viewing a record

Should NF

1.1.44 The system shall allow for the ability to configure

specific notes to trigger an alert to popup for applicable materials when editing a record

Should NF

1.1.45 The system shall allow for the ability to track serials order information

Should

1.1.46 The system shall allow for the ability to track serials order information including financial information

Should

1.1.47 The system shall allow for the ability to track

monograph order information

Should

1.1.48 The system shall allow for the ability to track

monograph order information including financial information

Should

1.1.49 The system shall allow for recording shipping list

data at item level

Should

1.1.50 The system shall allow for creation of Shipping Lists

customized reporting

Should NF

1.1.51 The system shall allow for customizable reports for

all items on a given shipping list to be generated (e.g., can generate customizable reports from the shipping list data field)

Should NF

1.1.52 The system shall allow for a customizable list of all

items on a given shipping list, including title, SuDoc, item number to be generated (e.g., will generate a shipping list from item-level data)

Should NF

1.1.53 The system shall allow for a list of libraries

subscribed to a specific item number to be generated

Should NF

1.1.54 The system shall allow for the ability to store

depository library account information

Should NF

1.1.55 The system shall allow for the ability to store library depository number

Should NF

1.1.56 The system shall allow for the ability to store library depository type

Should NF

1.1.57 The system shall allow for the ability to store

depository library name

Should NF

1.1.58 The system shall allow for the ability to store

depository library selection profile

Should NF

1.1.59 The system shall allow for the ability to store

depository library mailing address

Should NF

1.1.60 The system shall allow for notes about issues with

distribution

Should NF

1.1.61 The system shall allow for notes about issues with

distribution at the item level

Should NF

1.1.62 The system shall allow for customizable fields to

record distribution information

Should NF

1.1.63 The system shall allow for customizable fields to

record distribution information at the item level

Should NF

1.1.64 The system shall allow for the ability to record

distribution status

Should NF

1.1.65 The system shall allow for the ability to record

distribution date

Should NF

1.1.66 The system shall allow for the ability to record date

received

Should NF

1.1.67 The system shall allow for the ability to record copies received

Should NF

1.1.68 The system shall allow for the ability to record

cartons received

Should NF

1.1.69 The system shall allow for the ability to record

quantity of overage

Should NF

1.1.70 The system shall allow for the ability to record

quantity of shortage

Should NF

1.1.71 The system shall allow for the ability to generate

reports of distribution information

Should NF

1.1.72 The system shall allow for the ability to generate

custom reports of distribution information

1.1.73 The system shall allow for the ability to generate

statistics for distribution information

Should NF

1.1.74 The system shall allow for the ability to generate

custom statistics for distribution information

Should NF

1.1.75 The system shall allow for order creation date Should

1.1.76 The system shall allow for order sending date Should

1.1.77 The system shall allow for order updated date Should

1.1.78 The system shall allow for the ability to record

verification of quantity Should

1.1.79 The system shall allow for the ability to generate

reports of archival disposition information

Should NF

1.1.80 The system shall allow for the ability to batch mark

all items on a shipping list as distributed

Should NF

1.1.81 The system shall allow for the ability to batch mark

all items on a shipping list as distributed at the item level

Should NF

1.1.82 The system shall have a serial issue check in screen Should

1.1.83 The system shall have a serial issue check in screen

that displays the expected quantity Should

1.1.84 The system shall have a serial issue check in screen

allows the user to enter the quantity received

Should

1.1.85 The system shall have a serial issue check in screen

that allows the user to enter other check in information such as arrival dates

Should

1.1.86 The system shall have a serial issue check in screen

that allows for custom note fields

Cataloging Component Area

1.2 Cataloging

Function

1.2.1 The system shall have an integrated cataloging data

entry module

1.2.2 MARC21

Function

1.2.2.1 The system shall support MARC21 formatted data Should

1.2.2.2 The system shall support

https://www.loc.gov/marc/bibliographic/bd245.html:

Second Indicator - Nonfiling characters: 0 - No nonfiling characters: “Diacritical marks or special characters at the beginning of a title field that does not begin with an initial article are not counted as nonfiling characters.”

1.2.2.3 The system shall support corrections to the 245 2nd

indicator according to the presence or absence of initial articles and/or diacritical marks or special characters

Should

1.2.2.4 The system shall support corrections to the 245 1st

indicator depending on whether or not a 1XX field is present in the same record

Should

1.2.2.5 The system shall support generation of reports of

initial articles (a, the, an) in the 246 field

Should

1.2.2.6 The system shall support corrections according to

MARC 21 punctuation and spacing

Should

1.2.2.7 The system shall support corrections according to

MARC 21 punctuation and spacing by allow for adding or deleting terminal periods to various fields

Should

1.2.2.8 The system shall support corrections according to

MARC 21 punctuation and spacing by allow for correcting punctuation between subfields of various fields

Should

1.2.# Cataloging Continued…

Priority New Feature/ Function

1.2.3 The system shall support BIBFRAME (Bibliographic

Framework)

Should NF

1.2.4 The system shall support multiple character

encoding levels

Should

1.2.5 The system shall support ISO 8859-1 (Roman

character sets)

Should

1.2.6 The system shall support Unicode (non-Roman

character sets)

Should

1.2.7 The system shall support UTF-8 (non-Roman

character sets)

Should

1.2.8 The system shall support ASCII characters Should

1.2.9 The system shall allow creation of bibliographic

records Should

1.2.10 The system shall allow editing of bibliographic

records

Should

1.2.11 The system shall allow importing of bibliographic

records

Should

1.2.12 The system shall allow importing of bibliographic

records from OCLC

1.2.13 The system shall allow exporting of bibliographic

records

Should

1.2.14 The system shall allow exporting of bibliographic

records to OCLC

Should

1.2.15 The system shall allow for customization of match

points when importing records from OCLC

Should

1.2.16 The system shall allow for matching points with

OCLC number fields 035 and 019

Should

1.2.17 The system shall allow viewing of bibliographic

records

Should

1.2.18 The system shall allow spell check of bibliographic

data

Should NF

1.2.19 The system shall allow spell check of bibliographic

data of designated fields

Should NF

1.2.20 The system shall allow for macro creation Should NF

1.2.21 The system shall allow for macro editing Should NF

1.2.22 The system shall allow for constant data template

editing Should

1.2.23 The system shall support the Z39.50 protocol to

access GPO's bibliographic data

Should

1.2.24 The system shall allow for access to other libraries

data via Z39.50

Should

1.2.25 The system shall allow for selection of SuDoc

number as the primary/default Classification Number for bibliographic records

Should

1.2.26 The system shall allow for multiple library

collections

Should

1.2.27 The system shall allow for multiple library

collections with no limitation on the number that can be created

Should NF

1.2.28 The system shall allow for multiple library branches Should

1.2.29 The system shall allow for multiple library branches

with no limitation on the number that can be created Should NF

1.2.30 The system shall allow for shipping list data Should

1.2.31 The system shall allow for shipping list data at the

Item Record level Should

1.2.32 The system shall allow for customizable Item Record

data fields

Should

1.2.33 The system shall allow for customizable display Should NF

1.2.34 The system shall allow for customizable display font

size

1.2.35 The system shall have accessibility tools for vision Should NF

1.2.36 The system shall support the most current Resource

Description & Access (RDA) format

Should

1.2.37 The system shall support RDA Tool Kit Should NF

1.2.38 The system shall integrate local cataloging

documentation into data entry interface Should NF

1.2.39 The system shall support bibliographic field help

data

Should

1.2.40 The system shall support standard copy and paste

functions

Should

1.2.41 The system shall support standard copy and paste

functions for entire fields

Should

1.2.42 The system shall support standard copy and paste

functions for specific subfields

Should

1.2.43 The system shall allow for validation of subscription

data

Should NF

1.2.44 The system shall allow for synchronization of

subscription data with bibliographic record and holdings data

Should NF

1.2.45 The system shall allow process for record deletion Should

1.2.46 The system shall allow process for record deletion

with review and recovery options Should

1.2.47 The system shall allow records deleted to be held for

review

Should

1.2.48 The system shall allow records deleted to be held for

review with option to restore

Should

1.2.49 The system shall allow for users to save records in

data entry modules

Should

1.2.50 The system shall allow for users to save searches in

data entry modules

Should

1.2.51 The system shall allow for customized searching

within data entry modules

Should

1.2.52 The system shall allow for the ability to expand item

information into bibliographic record when exporting records (expand routines)

Should

1.2.53 The system shall allow for error reporting Should NF

1.2.54 The system shall allow for error reporting with

customized parameters Should NF

1.2.55 The system shall allow for error reporting for records without 086

Should

1.2.56 The system shall allow for error reporting for records without 086 standard formatting

Should

1.2.57 The system shall allow for error reporting for records with a comma in 086

1.2.58 The system shall allow for error reporting for records without 074 based on custom parameters

Should

1.2.59 The system shall allow for error reporting for records with EL data missing 85640 $u

Should

1.2.60 The system shall allow for error reporting for records with 85640 missing $u

Should

1.2.61 The system shall allow for error reporting for records with 85640 $u that do not contain GPO standard PURLs

Should

1.2.62 The system shall allow for error reporting for records with 85640 $u that contain GPO standard PURLs starting with http rather than https

Should

1.2.63 The system shall allow for error reporting for records recently created with 85641

Should

1.2.64 The system shall allow for error reporting for records with duplicate 086 fields in monograph records

Should

1.2.65 The system shall allow for error reporting for records where the 086 and Item/Holding SuDoc Numbers do not match for monographs

Should

1.2.66 The system shall allow for error reporting for records where the 086 and Item/Holding SuDoc Number stems do not match for serials

Should

1.2.67 The system shall allow for error reports to contain

system numbers, error, 955 $a codes, last date updated

Should

1.2.68 The system shall allow for custom error reports Should

1.2.69 The system shall allow for error report notifications

to be sent to specific user classes

Authority and Authority Control Component Area

1.3 Authority/Authority

Control

Function

1.3.1 The system shall support Library of Congress

Subject Headings (LCSH)

Should

1.3.2 The system shall support Medical Subject (MeSH)

Headings

Should

1.3.3 The system shall support NASA Headings Should

1.3.4 SuDoc Authority

Function

1.3.4.1 The system shall support SuDoc Authority Should NF

1.3.4.2 The system shall support SuDoc Authority validation

against bibliographic record data

Should NF

1.3.4.3 The system shall support SuDoc Authority validation

against bibliographic record data to indicate duplicate SuDoc Numbers

Should NF

1.3.4.4 The system shall support SuDoc Authority validation

against bibliographic record data to indicate duplicate SuDoc Numbers including record type

Should NF

1.3.4.5 The system shall support SuDoc Authority validation

against bibliographic record data to indicate duplicate SuDoc Numbers including record number(s)

Should NF

1.3.4.6 The system shall not validate SuDoc numbers

containing commas

Should NF

1.3.4.7 The system shall provide in a popup window the

precise reason why validation has failed

Should

1.3.4.8 The system shall allow any failed validation to be

overridden

Should

1.3.4.9 The system shall allow any failed validation to be

overridden based on user class

Should

1.3.4.10 The system shall support Item Number Authority Should NF

1.3.4.11 The system shall support Library of Congress Call

Number Should

1.3.4.12 The system shall support Dewey Decimal Class

Number

Should

1.3.4.13 The system shall support standard MARC Language

Codes

Should

1.3.4.14 The system shall support standard MARC Country

Codes

Should

1.3.4.15 The system shall support standard MARC

Geographic Codes

Should

1.3.4.16 The system shall support Library of Congress

Genre/Form Headings

Should

1.3.4.17 The system shall support Library of Congress Name

Headings

Should

1.3.4.18 The system shall support Library of Congress

Geographic Headings

Should

1.3.4.19 The system shall support FAST headings Should

1.3.5 Validation-

Internal

Function

1.3.5.1 The system shall support validation against all

authority data

1.3.5.2 The system shall support validation against all

heading classes

Should NF

1.3.5.3 The system shall support synchronization of

bibliographic headings with authority file headings with options to protect local fields

Should NF

1.3.5.4 The system shall support synchronization of

bibliographic headings with authority file headings during off hours as a chron job

Should NF

1.3.5.5 The system shall support synchronization of

bibliographic headings with authority file headings during off hours as a chron job after any updates from external authority files updates

Should NF

1.3.5.6 The system shall support the ability to reflect

changes in authority record headings in all associated bibliographic records having that access point

Should NF

1.3.5.7 The system shall not allow unauthorized

[unvalidated] access points against the authority data to be added to bibliographic records automatically during validation

Should NF

1.3.5.8 The system shall not add to any bibliographic record

an access point which corresponds to a name authority record coded 008/12 = c

Should NF

1.3.6 Validation-

External

Priority New Feature/ Function

1.3.6.1 The system shall support validation against

externally accessible authority files

Should NF

1.3.6.2 The system shall support validation against

https://id.loc.gov/

Should NF

1.3.6.3 The system shall support validation against

externally accessible authority tools

Should NF

1.3.6.4 The system shall search authority records Should

1.3.6.5 The system shall search all fields within authority

records including access points and supplementary data fields

Should NF

1.3.6.6 The system shall search all fields Should

1.3.6.7 The system shall browse authority records Should

1.3.6.8 The system shall support multi-lingual text in

authority records Should

1.3.6.9 The system shall support Roman characters in

authority records

Should

1.3.6.10 The system shall support non-Roman characters in

authority records

1.3.6.11 The system shall have the ability for internal users to retrieve customized statistics/metrics

Should NF

1.3.6.12 The system shall have the ability for internal users to retrieve customized reports

Should NF

1.3.6.13 The system shall have the ability for internal users to retrieve tailored customized statistics/metrics

Should NF

1.3.6.14 The system shall have the ability for internal users to retrieve tailored customized reports

Should NF

1.3.6.15 The system shall have the ability to provide reports for unmatched headings following synchronization

Should NF

1.3.6.16 The system shall have the ability to provide reports for partially matched headings following synchronization

Should NF

1.3.6.17 The system shall have the ability to provide reports for changed authority headings following synchronization

Should NF

1.3.6.18 The system shall have the ability to provide reports for changed bibliographic headings following synchronization

Should NF

1.3.6.19 The system shall allow for linking from bibliographic records to authority records for internal staff

Should

1.3.6.20 The system shall allow for linking from bibliographic records to authority records for external users

Should

1.3.6.21 The system shall allow for display of entire Authority record

Should

1.3.6.22 The system shall allow for display of tailored views of Authority records based on user class

Should NF

1.3.6.23 The system shall allow for seamless interfiling of

authority access points (1XX, 4XX, 5XX) with bibliographic access points, referring users from references (4XX, 5XX) to authorized headings (1XX)

Should NF

1.3.6.24 The system shall display when an access point in a

search result or browse display is from a 4XX field

Should

1.3.6.25 The system shall whenever a user is redirected from

a reference (4XX, 5XX) to an authorized heading (1XX), by clicking on the See ____ reference, that user is next placed in the browse index that corresponds with the 1XX heading

Should NF

1.3.6.26 The system shall allow for indexing of all authority access points

Should

1.3.6.27 The system shall allow for searching of all authority access points

1.3.6.28 The system shall allow for indexing of all authority record access points: 1XX, 4XX, 5XX, including name/title combinations that include subfield $t

Should

1.3.6.29 The system shall allow for searching of all authority record access points: 1XX, 4XX, 5XX, including name/title combinations that include subfield $t

Should

1.3.6.30 The system shall allow for browsing of all authority record access points: 1XX, 4XX, 5XX, including name/title combinations that include subfield $t

Should

1.3.6.31 The system shall allow for display of all authority

record access points: 1XX, 4XX, 5XX, including name/title combinations that include subfield $t

Should

1.3.6.32 The system shall search MARC tag for corporate

name = X10

Should

1.3.6.33 The system shall browse by MARC tag for corporate

name = X10

Should

1.3.6.34 The system shall search by MARC tag for conference

name = X11

Should

1.3.6.35 The system shall browse by MARC tag for conference

name = X11

Should

1.3.6.36 The system shall search MARC tag for geographic

name = X51 or $z

Should

1.3.6.37 The system shall browse by MARC tag for geographic

name = X51 or $z

Should

1.3.6.38 The system shall search MARC tag for title = X30 or

$t

Should

1.3.6.39 The system shall browse by MARC tag for title = X30

or $t

Should

1.3.6.40 The system shall search MARC tag for personal name

= X00

Should

1.3.6.41 The system shall browse by MARC tag for personal

name = X00

Should

1.3.6.42 The system shall search MARC tag for topical term =

X50 or $x

Should

1.3.6.43 The system shall browse by MARC tag for topical

term = X50

Should

1.3.6.44 The system shall search MARC tag for genre/form

term = X55

Should

1.3.6.45 The system shall browse by MARC tag for genre/form

term = X55

Should

1.3.6.46 The system shall search MARC tag for topical

subdivision = 180 or $x

Should

1.3.6.47 The system shall browse by MARC tag for topical

subdivision = 180 or $x

1.3.6.48 The system shall search MARC tag for chronological

subdivision = 182 or $y

Should

1.3.6.49 The system shall browse by MARC tag for

chronological subdivision = 182 or $y

Should

1.3.6.50 The system shall search MARC tag for form

subdivision = 185 or $v

Should

1.3.6.51 The system shall browse by MARC tag for form

subdivision = 185 or $v

Should

1.3.6.52 The system shall search MARC tag for cataloger code

= 955

Should

1.3.6.53 The system shall search by MARC tag for name/title

combinations = XXO + $t

Should

1.3.6.54 The system shall browse by MARC tag for name/title

combinations = XXO + $t

Should

1.3.6.55 The system shall provide a search link from an

authority record 1XX to retrieve bibliographic records which contain that heading for internal staff

Should

1.3.6.56 The system shall provide a search link from an

authority record 1XX to retrieve bibliographic records which contain that heading for external users

Should

1.3.6.57 The system shall allow for linking from authority

records to related authority records (via 5XX field) for internal staff

Should

1.3.6.58 The system shall allow for linking from authority

records to related authority records (via 5XX field) for external users

Should

1.3.6.59 The system shall allow for the ability to undo certain changes

Serials/Continuing Resources Component Area

1.4 Serials

Should New

Function

1.4.1 The system shall have an integrated

serials/continuing resource data entry module

Should

1.4.2 The system shall support summary statements Should

1.4.3 The system shall support managing bibliographic

records Should

1.4.4 The system shall support managing Item records Should

1.4.5 The system shall support managing Holding records Should

1.4.6 The system shall support moving Item Records

between bibliographic records with a drag and drop function

Should

1.4.7 The system shall support MARC holding records Should

1.4.8 The system shall support collapsing [binding] Item

Records for serial/continuing resources Should

1.4.9 The system shall support unlimited number of item

records

Should NF

1.4.10 The system shall support unlimited number of

holding records

Should NF

1.4.11 The system shall support display of unlimited

number of holding records

Should NF

1.4.12 The system shall support display of unlimited

number of item records

Should NF

1.4.13 The system shall support collapsing [binding] of

records

Should

1.4.14 The system shall support warning before creating a

duplicate holding record

Should NF

1.4.15 The system shall require approval before creating a

duplicate holding record

Should NF

1.4.16 The system shall allow for custom label printing Should

1.4.17 The system shall allow for custom label printing in

multiple formats for standards label Should

1.4.18 The system shall allow for bulk of data record editing for volume of item records

Should NF

1.4.19 The system shall allow for macro or autofill text Should NF

1.4.20 The system shall link 78X fields [linked to series of

records] Should

1.4.21 The system shall allow for prediction pattern making

option

Should

1.4.22 The system shall allow for linking and relinking

holdings/items to bibliographic records across bibliographic records formats (serials, monograph, etc.)

Should NF

1.4.23 The system shall auto-populate summary holdings

statement from item record enumeration/chronology data

Should

1.4.24 The system shall allow for selection of SuDoc

number as the primary/default Classification Number in Item/Holding Records

Should

1.4.25 The system shall allow for ordinal support for

pattern prediction. So all the "th" and "rd" show up

Should

1.4.27 The system shall allow for the capture multiple

SuDocs and populate them in holdings record

1.4.28 The system shall allow for linking of the 852 holding

field and 086 bibliographic record field

Should

1.4.29 The system shall allow for validation of the 852

holding field and 086 bibliographic record field

Should NF

1.4.30 The system shall allow for synchronization of the

852 holding field and 086 bibliographic record field

Should NF

1.4.31 The system shall regardless of which was created

first synchronize the classification information [from the bibliographic record 086 $a to the holding record 852 $h and Item Record]

Should NF

1.4.32 The system shall regardless of which was created

first synchronize the classification information [from the bibliographic record 086 $a to the holding record 852 $h and Item Record] with notification to approve action

Should NF

1.4.33 The system shall have the ability to determine when

seasonal issues season begins (such as Winter versus Spring)

Should NF

1.4.34 The system shall support the ability to collapse

bound issues values

Should

1.4.35 The system shall support the ability to collapse

bound issues values with the ability to edit

Should

1.4.36 The system shall support customizable public note

fields

Should

1.4.37 The system shall support customizable internal note

fields

Should

1.4.38 The system shall support the ability to customize

location data

Should

1.4.39 The system shall support gap analysis Should

1.4.40 The system shall support gap analysis reporting Should

1.4.41 The system shall support processing electronic only

titles Should

1.4.42 The system shall support processing tangible titles Should

1.4.43 The system shall support notifications for items

created with no tangible item checked in Should

1.4.44 The system shall support reporting of items created

with no tangible item checked in

Should

1.4.45 The system shall support the ability to create pattern templates

Should

1.4.46 The system shall support the ability to create

prediction patterns with multiple parts

Should

1.4.47 The system shall support the ability to create

patterns issues with multiple subissues

1.4.48 The system shall support the ability to suppress

individual items from public display

Should

1.4.49 The system shall support the ability to suppress

individual items from public display for individual titles

Should

1.4.50 The system shall support the ability to suppress all

items for a specific bibliographic record from public display

Should

1.4.51 The system shall support the ability to suppress all

items with a certain item status such as "not received" from public display

Should

1.4.52 The system shall support the ability to suppress

holding data from public display

Should

1.4.53 The system shall support the ability to create custom

reports from item data

Should

1.4.54 The system shall support the ability to create custom

reports from holding data

Should

1.4.55 The system shall support the ability to create custom

reports from location data

Should

1.4.56 The system shall allow auto-population of content

for some fields such as location, collection, call number type, type, etc., when manually creating items with the ability to edit that content

Should NF

1.4.57 The system shall allow the ability to create item

records automatically when exporting data from

OCLC

Should

1.4.58 The system shall allow the ability to create holdings

records automatically when exporting data from

OCLC

Preservation and Collection Management Component Area

1.5 Preservation/Collection Management

Function

1.5.1 The system shall have integrated collection

development and management functionality

Should

1.5.2 The system shall have a reporting feature to facilitate Preservation and Collection Management user classes to view the results of reports within the system

Should NF

1.5.3 The system shall have a reporting feature to facilitate Preservation and Collection Management user classes to manipulate the results of reports within the system

1.5.4 The system shall support the downloading of the

results of those search queries as a file to staff workstations

Should NF

1.5.5 The system shall allow for the ability to trigger the

creation of items and holdings records

Should

1.5.6 The system shall support special collections/branch

libraries

Should

1.5.7 The system shall support the display of partner

libraries [Preservation Stewards]

Should

1.5.14 Collection

Development Analytics

Function

1.5.14.1 The system shall have fully integrated collection

development analytics tools

Should NF

1.5.14.2 The system shall support analytics for collection

development

Should NF

1.5.14.3 The system shall support collection analysis Should NF

1.5.14.4 The system shall support identification of trends Should NF

1.5.14.5 The system shall support identification of collection weak points (holes) Should NF

1.5.14.6 The system shall support identification of collection gaps

Should NF

1.5.14.7 The system shall support identification of overlap

between electronic and…