20180621_Appendix_C_Functional_Requirements.xlsx

XLSX spreadsheet 326 KB Posted Jun 28, 2018

Attached to: RFI ArmyU Library Services Platform
Solicitation number: PANMCC18P0000093732
Issued by: Department of the Army Materiel Command Mission and Installation Contracting Command Fort Leavenworth

About this file

From the source

Appendix C

View the file

Other files

File	Type	Posted
20180621_Appendix_B_Operating_Environment_Of_TRADOC_Libraries_June18.pdf	PDF	Jun 28, 2018
20180621_LSP_RFI_06June18.docx	DOCX document	Jun 28, 2018
20180621_Appendix_A_Library_Services_Platform_Components.PPTX	PPTX presentation	Jun 28, 2018

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

A. Acquisitions

	Sub Categories	Acquisitions
1	A.1 Acquisitions Management	Describe how the ILS enables cooperative collection development within the Consortium. Describe how member libraries can compare collections, orders, and check-in records. Describe how member libraries can see what other libraries are acquiring or cancelling.
2	A.1 Acquisitions Management	Describe how each institution will manage local information, such as binding information, or processing notes, in a shared environment.
3	A.1 Acquisitions Management	Describe how the ILS manages public and private donor information within a library and across a shared environment.
4	A.1 Acquisitions Management	Describe how order data is stored in relationship to each of the following: bibliographic data, item data, and electronic resource management data.
5	A.1 Acquisitions Management	Describe how theILS distinguishes between print titles and e-resource titles when the same title is imported, either from the same vendor or from different vendors.
6	A.1 Acquisitions Management	Describe how bibliographic records can be imported from a vendor, including the automatic creation of order, invoice, and/or item records from data supplied by the individual institution.
7	A.1 Acquisitions Management	Describe how bibliographic records can be created when full records are unavailable. Describe what templates are currently available to assist with this process and how these templates can be customized. Describe the process for overlaying such records.
8	A.1 Acquisitions Management	Describe how the ILS alerts staff when duplicate copies are ordered within a library.
9	A.1 Acquisitions Management	Describe support for manual and electronic selection, ordering, invoicing, and claiming. Describe what electronic submission protocols are supported.
10	A.1 Acquisitions Management	Describe how the ILS integrates interlibrary loan, course reserves, and the public catalog with a variety of acquisitions models, such as purchase-on-demand programs, patron driven acquisitions, etc.
11	A.1 Acquisitions Management	Describe how the ILS accommodates audit standards and variable retention/ removal policies and schedules.
12	A.1 Acquisitions Management	Describe how digital copies of invoices can be stored within the ILS and linked to order records or license records, and in what formats these files are supported.
13	A.1 Acquisitions Management	Describe how the ILS supports the suppression of individual items from public view and how items may be omitted from harvesting, such as reports or other forms of data extraction.
14	A.1 Acquisitions Management	Describe how the ILS alerts users to orders that do not have sufficient funds remaining for that fiscal year.
15	A.1 Acquisitions Management	Describe how budget allocations for the next fiscal year can be set automatically to advance according to variable inflation schedules, per order, or per groups of orders.
16	A.1 Acquisitions Management	Describe the functionality for fiscal year rollover, including opening, closing, and using multiple years simultaneously. Describe how the ILS accommodates a variety of independent fiscal year rollover calendars. Describe how orders not yet received are rolled over into the next fiscal year. Describe how the ILS alerts users to orders that do not have sufficient funds remaining for that fiscal year.
17	A.1 Acquisitions Management	Describe the architecture for storing vendor data. Describe how vendor information is shared, differentiated, and updated. Describe how multiple accounts for a vendor at a single institution would function.
18	A.1 Acquisitions Management	Describe any delays in the generation of reports, i.e lag time from when the report is initated to result displayed. Describe any data elements that will not be reported in real time.
19	A.1 Acquisitions Management	Describe the standard reports for collection, budget, and acquisitions analysis at the individual library, subgroup of libraries, and consortium levels. Describe how these reports can be customized. Describe any limitations to how collection, budget, or acquisitions data can be combined with data from other functional areas of ILS for the purpose of reporting.
20	A.1 Acquisitions Management	Describe the ability to send emails at the selection stage and throughout the acquisitions/processing/cataloging workflow -- for the following: requesting user, acquisitions vendor, selection, ordering, receiving, pre-processing, cataloging, post-processing, and OPAC.
21	A.2 Acquisitions - Workflow Management	Describe the integrated workflow, including steps such as material selection, purchase orders, acquisition, circulation, access provision, or de-selection.
22	A.2 Acquisitions - Workflow Management	Describe how automated workflows support the flow of materials through the entire technical services process, from acquisition through bibliographic description, physical processing, circulation, inventory and withdrawing an item. Explain the process of hand-offs when multiple staff persons perform steps of a task.
23	A.2 Acquisitions - Workflow Management	Describe how data entry can be integrated and differentiated across institutions to avoid repetitive data management (e.g., contact, license, etc.) without constraining local practice or imposing centralized terms on individual libraries.
24	A.2 Acquisitions - Workflow Management	Describe the overall workflow notification tools, such as automated reminders or dashboard conveniences. These might include reminders to pay, to renew, to send items to the bindery, to close trials, to set up access, or to close records upon the completion of subscription periods.
25	A.2 Acquisitions - Workflow Management	Describe the local and individual options to personalize workflows.
26	A.2 Acquisitions - Workflow Management	Describe how the ILS helps manage collection development record-keeping, such as wish-lists based on previous reviews, records of decisions not to add, records of decisions to cancel, etc.
27	A.2 Acquisitions - Workflow Management	Describe how the ILS enables on-screen display and printing for integrated workflow for any given record or a list of records (e.g., ability to print the bib, item, order and circulation of a given title(s)).
28	A.2 Acquisitions - Workflow Management	Describe how the ILS automatically updates all public and staff displays of the resource, including holdings records, upon deselection of a resource.
29	A.2 Acquisitions - Workflow Management	Describe the standard reports for managing and tracking acquisitions workflow. Describe how these reports can be customized.
30	A.2 Acquisitions - Workflow Management	Describe how the ILS accommodates customizations at the individual library, subgroup of libraries, and at the Consortium levels.

AU-LES Library Management System Functional Requirements, &"-,Bold"Section A&"-,Regular" &"-,Bold"Category: Acquisitions

B. Cataloging

	Sub Categories	Cataloging
1	B.1. Authority Control	How does the ILS prevents duplication of authority data? Describe how it enables the removal of duplicate authority data. Describe how it identifies and reports headings which do not correspond to an authorized form.
2	B.1. Authority Control	Describe how the ILS manages the import and export of authority data with one or more authority vendors.
3	B.1. Authority Control	Describe authority control functionality, including how the ILS identifies which data can be controlled. Describe the default authority control practices and the ability to customize these practices.
4	B.1. Authority Control	Describe how the ILS supports current standards for authority data and allows all relevant bibliographic data to be authority controlled without intervention by the ILS vendor.
5	B.1. Authority Control	Describe how your system handles orphaned/blind authority records
6	B.2 Bibliographic Description	Describe any crosswalk tools or utilities that will convert from one metadata schema to another.
7	B.2 Bibliographic Description	Describe how the ILS manages multiple classification systems within a single member library, a group of libraries, and across the Consortium (e.g., Library of Congress, Superintendent of Documents, Dewey, locally-developed schema).
8	B.2 Bibliographic Description	Describe any limits to the size of bibliographic and holdings records.
9	B.2 Bibliographic Description	Explain how the ILS provides access to library-specific local data and practices and how local data will be accommodated in a consortial environment.
10	B.2 Bibliographic Description	Describe capability and limitations of the ILS for importing, exporting, editing and overlaying bibliographic, holding, and authority records in MARC 21 format and future formats from OCLC Connexion and other sources of bibliographic data.
11	B.2 Bibliographic Description	Explain the process to maintain the index, including frequency of maintenance and effects on service.
12	B.2 Bibliographic Description	Describe how indexes are created and maintained. Describe options for customizing indexing at the Consortium and individual institution level.
13	B.2 Bibliographic Description	Describe how the ILS incorporates templates or constant data, drop down menus, and contextual help such as field/element descriptions.
14	B.2 Bibliographic Description	Describe any shortcuts for commonly executed commands.
15	B.2 Bibliographic Description	Describe any limitations on batch processing
16	B.2 Bibliographic Description	Describe how the ILS supports global changes across different types of records regardless of item status within a single member library, within a group of libraries, or across the Consortium
17	B.2 Bibliographic Description	Explain how the ILS interfaces with batch editing tools such as MarcEdit.
18	B.2 Bibliographic Description	Describe the permission controls to manage who has what global change access.
19	B.2 Bibliographic Description	Describe system capabilities for editing data, both for individual records and batch updates and deletions of a selected group of records.
20	B.2 Bibliographic Description	Describe both search and export options at the level of MARC 21 fields and subfields, including leader and control fields.
21	B.2 Bibliographic Description	Does the ILS provide the ability to merge similar bibliographic records without loss of locally-created data? Describe the process.
22	B.2 Bibliographic Description	Does the ILS have the ability to display content from providers of enriched content such as covers, sample chapters, reviews and digital shelf browsing from vendors such as Syndetics and LibraryThing for Libraries, and stack-mapping services, including custom stack-mapping applications?
23	B.2 Bibliographic Description	Describe how the system handles input and support of characters in non-roman scripts, bidirectional scripts (e.g., Chinese, Japanese, Cyrillic, Arabic, Hebrew). Describe how diacritics are stored, displayed, input and indexed. Include any specific requirements for peripheral hardware or software to ensure this support.
24	B.2 Bibliographic Description	Does the ILS provide the ability to create, edit, store, publish and enable the discoverability of archival metadata records (e.g., Dublin Core, EAD, MODS, METS) and to integrate with digital object and metadata repositories? Describe the system's ability to adapt to emerging metadata standards in the future, such as BIBFRAME.
25	B.2 Bibliographic Description	Describe how the system manages multiple classification schema and subject vocabularies, including, but not limited to, Library of Congress Classification and Subject Headings, Dewey Decimal Classification, SuDoc classification numbers, local classification schema, National Library of Medicine Subject Headings, etc.
26	B.2 Bibliographic Description	Describe how bibliographic records can be created when full records are unavailable. Describe what templates are currently available to assist with this process and how these templates can be customized. Describe the process for overlaying such records
27	B.3 Holdings Management / Items	Describe how the ILS handles linked records. For example, describe how the ILS handles a single item linked to separate holding locations on multiple bibliographic records such as bound-withs. Provide an example of how linked items display in the public and staff views.
28	B.5 Quality Control/Batch Updates	Describe how the automated quality control routines, such as validation tables, are kept current with updates to national and international data standards. Include how the ILS ensures that the coding, data, and text strings in bibliographic, holdings, authority, and item records loaded into it conforms to published national and international data standards such as MARC21 and ANSI/NISO Z39.71-2006 (R2011).
29	B.5 Quality Control/Batch Updates	Describe how the system performs real-time download with Z39.50 targets
30	B.5 Quality Control/Batch Updates	Describe the quality control/batch updating functionality of the ILS including how the ILS prevents records for items that are currently at some stage of the acquisition, technical services, or circulation process from being improperly modified, deleted, or duplicated
31	B.6 Reports and Statistics	Describe any cataloging specific reports and statistics that are available.
32	B.7 Workflows	Describe procedures for automatically ingesting records from bibliographic updating services (e.g., OCLC WorldCat MARC Updates, WorldCat Cataloging Partners, Serials Solutions MARC Delivery). Describe the capacity of the system for batch loading records and the options for using or creating APIs for ingesting records.
33	B.7 Workflows	Describe how the ILS handles workflow hand-offs e.g. when different staff users perform steps or components of a task, explain how workflows support the hand-offs through queuing and/or notification. Explain how information about specific records, (e.g., bibliographic records, orders, invoices, etc.) is shared among staff.
34	B.7 Workflows	Describe how the ILS will provide staff workflows that can be integrated across institutions to avoid repetitive data management. Must also provide local options for customizing the integration of workflows (i.e. Can the system support multiple cataloging queues? Can the solution support multiple labeling queues?

AU-LES Library Management System Functional Requirements, &"-,Bold"Section B&"-,Regular" &"-,Bold"Category: Cataloging

C. Circulation

	Sub Categories	Circulation
1	C.1 Billing and Payments	Describe how the ILS manually and automatically generates bills and fees and how those are subsequently processed and that information retained and made available for reporting. Include information about customization and sending batch or individual notices and/or bills and the formats available (paper, email, SMS, ets.) as well as staff functions to process payment. Address applicable laws regarding payments and confidentiality and integration with multiple financial information systems.
2	C.1 Billing and Payments	Explain how the ILS can facilitate billing between consortium libraries.
3	C.1 Billing and Payments	Describe workflows for specialized loan and billing functions, including, but not limited to, items claimed to be returned, returned items after declared lost, and creation of temporary item records.
4	C.2 Collection Management	Describe how the ILS provides the capability to set up floating collections.
5	C.2 Collection Management	Describe the workflow for performing an inventory of a collection, including the simultaneous inventory of multiple collections.
6	C.2 Collection Management	Identify inventory and collection management tools available in the ILS and any specific notification and reporting tools associated. Include information about integration with third party collection management and course reserves tools.
7	C.2.a Collection Management-Reports	Describe system methods for exporting and/or downloading reports making the data universally accessible (ex. csv file) to facilitate data manipulation, transfer and sharing.
8	C.2.a Collection Management-Reports	Does the system support the capability to export via FTP?
9	C.2.a Collection Management-Reports	Describe how reports are scoped to the collections or activities of a specific library or, within the data security parameters outlined elsewhere, for a subgroup of libraries or the Consortium as a whole.
10	C.2.a Collection Management-Reports	Describe how collection trends and activity can be exposed to the public in real time--showing, for example, trending search topics, usage by collection, media type, or subject.
11	C.2.a Collection Management-Reports	Describe the standard reports for electronic resources management at the individual library, subgroup of libraries, and consortium levels. Describe how these reports can be customized. Describe the overlap analysis reports.
12	C.2.a Collection Management-Reports	Does the ILS provide reports of library holdings dropped from databases or packages?
13	C.2.a Collection Management-Reports	Describe the usage statistics reporting functionality at the individual library, subgroup of libraries, and consortium levels
14	C.2.a Collection Management-Reports	Describe how the ILS enables automatic vendor usage statistics harvesting, as well as manual input of usage statistics at the individual library, subgroup of libraries, and consortium levels. Describe how these reports can be customized.
15	C.2.a Collection Management-Reports	Describe any limits to how usage statistics elements can be related to other data elements for the purpose of reporting, such as acquisitions data elements. Does the system provide the capability to product cost-per-use analyses? Include a description of the steps involved in producing this report.
16	C.2.a Collection Management-Reports	Describe how the ILS tracks and reports system usage, ex. click-throughs or circulation, and describe how these system usage statistics can be reported in combination with vendor usage statistics or other data elements managed by the ILS, as above.
17	C.2.a Collection Management-Reports	Does the system provide a report generator which allows users to easily query the database by combinations of user-selected fields and criteria but DOES NOT require any specialized SQL experience?
18	C.2.a Collection Management-Reports	Please describe and/or provide screenshots of the high-level reporting capabilities available in your system. Does the system offer SQL (or equivalent) access into the data set to produce more complicated reports?
19	C.2.a Collection Management-Reports	Describe how the system provides a method for automating the creation of regular, daily, weekly, and monthly reports (e.g. circulation, overview, collection snapshot, acquisitions activities, etc.). Can these generated reports (custom or canned) be saved, printed, or exported as a PDF or Excel file?
20	C.2.a Collection Management-Reports	Describe how the ILS delivers customizable, aggregated, multi-dimensional relational views of data from multiple modules or external sources (such as COUNTER usage data). Include information about what data are available through these views, whether the views are read-only or provide update capabilities, and any export or scripting capabilities. Describe how these views might include data from multiple record types (e.g., bibliographic data and order data).
21	C.2.a Collection Management-Reports	Describe any limitations that exist on combining data elements from multiple record types for reporting or updating
22	C.2.a Collection Management-Reports	Describe which external reporting tools, such as Microsoft Access, can be used with the ILS. Describe the limitations of the data made available to external reporting tools.
23	C.2.a Collection Management-Reports	Describe how customized report templates can be stored for repeated use and shared among all members of the Consortium.

24	C.2.a Collection Management-Reports	Describe how the ILS provides statistical reports for resource sharing requests at the system-wide, individual unit, and delivery location levels. List data elements that appear in statistical reports.
25	C.2.a Collection Management-Reports	Describe how the ILS provides reports that track copyright compliance and support payment of royalties. Provide examples.
26	C.2.a Collection Management-Reports	Provide examples of resource sharing reports that the ILS includes in its standard reporting package.
27	C.3 Communications and Notifications	Explain how the ILS provides the option to suppress notices by type or form or patron type. For instance, no notices sent to staff or only email notices to staff.
28	C.3 Communications and Notifications	Does the System automatically stop sending email notices to a patron once an email has been bounced back or returned to the library? Will the emails be flagged as bounced back?
29	C.3 Communications and Notifications	Describe the system's support for automated reminders, ticklers or alerts, for workflow tracking, renewal reminders, claims, system outages, bindings, etc.
30	C.3 Communications and Notifications	Explain how the ILS notifies a patron who has a HOLD that the item has become unavailable due to defined parameters such as lost or missing.
31	C.3 Communications and Notifications	Describe how the system provides the ability for staff to create NOTES on item records (page 20 torn) or patron records (misbehavior)
32	C.3 Communications and Notifications	Does the system provide automated sending as well as customization options, for example, the ability to produce a single return receipt for multiple items returned at a single time.
33	C.3 Communications and Notifications	What types of notices does the system provide (e.g., receipts, paging slips/lists, book bands, hold shelf tags, pick up and overdue notices)?
34	C.3 Communications and Notifications	Types and methods of automated and staff-initiated patron notifications the system provides (e-mail, SMS, instant messaging, mail, telephone, etc.). How would this work for hourly checkouts?
35	C.3 Communications and Notifications	Describe how notice language can be controlled by library/group of libraries.
36	C.3 Communications and Notifications	Does the system provide the ability to customize, design and brand print and electronic notices?
37	C.3 Communications and Notifications	Describe the system's notification functionality. For example, can the system automatically email staff or patrons when an item is received (print materials) or activated (electronic materials)?
38	C.3 Communications and Notifications	Describe the types and formats of internal staff use and external patron notices and print products that the ILS provides and how the notifications are produced and customized. Include information about notifications or alerts that are displayed to staff about individual transactions.
39	C.4 Course Reserves	Describe Course reserves functionality (print, electronic and streaming media) at an institutional level, including the ability to link reserve items to multiple courses and suppress temporary items, as well as any reporting features related to reserves.
40	C.4 Course Reserves	Explain how the ILS provides ability to assign course reserves to one or more instructors and course numbers at the item/copy level.
41	C.4 Course Reserves	Describe how the ILS provides the ability to manage materials that alternate locations between "general circulation" and "course reserves" while maintaining individual and separate statistics for these items (for example, general circulation vs reserve circulation).
42	C.4 Course Reserves	Describe how the ILS provides the ability to activate and suppress course reserves on a quarterly basis while retaining information and statistics from prior quarters.
43	C.4 Course Reserves	Explain how the ILS provides ability to batch process reserve items.
44	C.5 Loan Management	Explain how the ILS provides offline circulation capability in the case of cloud or network outage (this includes the ability to batch upload into the system once cloud or network outage is resolved).
45	C.5 Loan Management	Describe how the ILS supports the ability for staff to charge and renew multiple items in a single session without the need to enter an "override" for each item in the same session.
46	C.5 Loan Management	Describe how the ILS supports the ability for staff to manually change an item's status to lost or missing and to reverse that status when the item is found.
47	C.5 Loan Management	Describe how the ILS creates temporary bibliographic and item records "on-the-fly".
48	C.5 Loan Management	Describe how the ILS manages multiple calendars. Explain how the ILS manages 24 hour operations.
49	C.5 Loan Management	Describe Hold/hold shelf management capabilities and configuration options of the ILS, including holds on large numbers of items and across multiple institutions.
50	C.5 Loan Management	Explain how the ILS supports the coexistence of local and consortial lending rules including the capability to customize lending rules.
51	C.5 Loan Management	Explain how the ILS supports the ability to determine/provide loan periods and renewal policies when dealing with consortial lending without interfering with local loan, renewal and hold policies.
52	C.5 Loan Management	Explain how the ILS provides ability to assign different loan periods at the copy level to individual titles that have multiple copies.
53	C.5 Loan Management	Describe how the ILS accommodates and manages item loans at an individual library, subgroup of libraries and for the Consortium as a whole. The response should include how multiple sets of lending rules are created and managed and how they affect users with multiple affiliations and loans across libraries. Include information about exceptions.
54	B.6 Patron Management	Describe how the system supports online patron account creation and management.
55	B.6 Patron Management	Describe the functionality of a patron's "My Account" feature to place holds, renew, and view regardless of format.
56	C.6 Patron Management	Describe Patron self-service capabilities.
57	C.6 Patron Management	Describe how the ILS allows management of patron access locally, regionally and consortially at multiple locations. Include information regarding patron record structure and how those records are created, maintained, blocked and removed, and how data privacy principles are maintained during the process. Address how patrons access services at multiple locations while maintaining a primary affiliation.
58	C.6 Patron Management	How does the ILS handle bulk importing of patron records from an external source?
59	C.6 Patron Management	Does the ILS support the ability to retain digital forms (i.e. DA 7745) with a sponsor record?
60	C.6 Patron Management	Describe the fixed and variable fields available in the patron record. Does the system support the ability of a single library to have custom fields? What patron fields are indexed?
61	C.6 Patron Management	If the library could define specific fields in the patron record, how would those fields be available through the report generator provided by your system through the staff modules?
62	C.6 Patron Management	How does the ILS support patron record templates at the consortial and local level?
63	C.6 Patron Management	How does the ILS performs duplicate checks on current patrons to validate that a patron is not already in the system?
64	C.6 Patron Management	Describe how the system supports patron record loading and field protection in existing patron records. Is there an interface for mediating/translating patron data as it is ingested from a student information system? If so, what are the supported options and is scripting functionality (e.g., regular expressions, Perl) provided for more advanced manipulation of incoming data?
65	C.6 Patron Management	Describe how the system allows automatic and manual blocks of patrons from borrowing and other services both at the consortial and local level.
66	C.6 Patron Management	Describe how the system accommodates multiple patrons statuses (staff that is also a student, etc.). Does the system allow specification of a hierarchy of privileges of multiple simultaneous statuses when there may be a conflict?
67	C.6 Patron Management	Describe how the ILS supports user privileges and proxy user assignment and privileges.
68	C.6 Patron Management	Describe how the ILS makes allowances for the management of patrons who have local privileges but not consortial privileges.
69	C.6 Patron Management	Describe how the system allows a patron to access services at multiple ArmyU Enterprise libraries while maintaining a primary affiliation.
70	C.6 Patron Management	Describe how patrons can use the public interface of the ILS to track and manage all of their library activity, including their resource sharing requests.
71	C.7 Scheduling	Describe how the ILS provides for the booking of equipment, materials, resources and rooms, as well as how the ILS is used to book appointments with librarians and other staff by library personnel or directly by the patron. Address how the ILS supports varying time blocks and how it t interacts with open/closed hours, as well as any exceptions and modifications.
72	C.7 Scheduling	Describe how the ILS provides the ability to create, edit, delete events.
73	C.8 Holds	Describe how the ILS can turn off/on the capability to place holds on specific items/copies at the bibliographic record or item level.
74	C.8 Holds	Describe the capability of the ILS to set priority holds within a consortial environment.
75	C.8 Holds	Describe how the ILS can support the ability to place requests for a single title for multiple patrons in one operation, without placing individual multiple holds.
76	C.8 Holds	Describe how the ILS can support the ability for patrons to view the position on the hold request(s) in the holds queue.
77	C.8 Holds	Describe how the ILS can support the ability of the staff to place notes on the hold request that will be printed on the hold slip.
78	C.8 Holds	Describe how the ILS can support the ability to designate an expiration or “not needed after” date when a hold is placed.
79	C.8 Holds	Describe how the ILS can support the ability to stop or allow a check-out of an item if it will fill a hold request on the system.
80	C.8 Holds	Describe how the ILS can support alert staff when a hold is placed against a title with no items.
81	C.8 Holds	Describe how the ILS can support the ability for patrons to say the order they want hold titles to arrive (volume one first, then volume two, etc.).

Functional Requirements, &"-,Bold"Section C&"-,Regular" &"-,Bold"CATEGORY: Circulation

Page

D. Discovery

	Sub Categories	Discovery
1	D.1 Authentication	Describe how the Discovery provides support for standard authentication protocols, such as IP address, LDAP, Kerberos. Describe any support for single sign-on or pass-through authentication.
2	D.1 Authentication	Many Consortium institutions have significantly invested in the development and management of existing identity-related data stores using authentication protocols (e.g., LDAP and Kerberos). Describe how the Discovery can leverage these identity stores, both for staff and patron accounts and how such capabilities can co-exist alongside identities natively managed within the Discovery.
3	D.1 Authentication	What types of authentication methods are supported?
4	D.1 Authentication	Describe how the Discovery provides the ability to opt in or out of available resources such as but not limited to Open Access eBooks (such as the HathiTrust), journals, and textbooks.
5	D.2 Branding	Describe how the Discovery supports branding. Explain other customization options that are available to individual libraries within the Consortium, including customizing display, results prioritization, output styles, search refinements, default options, ability to insert widgets and custom code, etc.
6	D.3 Indexing	Explain how the Discovery makes available institutional repository content for indexing via commercial search engines and how the Discovery enables discoverability from outside the discovery layer.
7	D.3 Indexing	Explain how the Discovery provides ability to create customizable controlled vocabularies used throughout site to filter content.
8	D.4 Multi-level Management	Explain how Discovery structure allows for locally managed resources to be administered at the Consortium level, along with the ability to configure individual library instances. Include the strategy for accommodating Consortial subscriptions and the varied needs of the member libraries.
9	D.5 Search Experience	Describe how patrons are able to customize their search experience.
10	D.5 Search Experience	Identify whether/not your system provides federated search capabilities for online public discovery and at a minimum access via:

a) Functional Requirements for Bibliographic Records (FRBR)

b) Faceted Searching

c) Spelling and search suggestion

d) Z39.50 11 D.5 Search Experience Identify whether/not your system provides citation tools:

a) Email

b) Print

c) Export to RefWorks citation manager as well as other citation manager software, such as Zotero, EndNote, or Mendeley.

12	D.5 Search Experience	Describe options provided for managing search results display, including sorting by relevance, date, author, title, etc. Address refinement of search results and output options including export to a citation manager. List actions that are available from the results display. Address how the Discovery avoids dead ends and describe how it handles null results. Explain how linked data is incorporated to improve retrieval results.
13	D.5 Search Experience	Describe the scoping options of the discovery service, including the ability to display the collections of a single library, subgroup of libraries, or the Consortium as a whole. Describe how the user navigates between the scopes. Describe the options for promoting results relevant to the user’s affiliation and location. Include any information related specifically to Open Access ebooks, journals, and textbooks and their scopability
14	D.5 Search Experience	Does the Discovery provide a “Similar search” or “did you mean” function?
15	D.6 Requests -- patron initiated	Describe how the patron-initiated request function integrates with the discovery search interface. Note the fields that patrons must supply and those which download automatically from bibliographic and citation databases. Note when a patron must accept copyright restrictions.
16	D.6 Requests -- patron initiated	Describe how the Discovery supports staff-initiated requests. Address both loan and copy requests. Note how staff can create and duplicate requests on behalf of patrons and reinitiate closed requests. Describe how the Discovery signals warnings, exceptions or conditions that apply when staff create or modify requests.Include descriptions of configuration options.
17	D.7 Training and Support	Describe any training and support available for patrons and staff.
18	D.8 Platform management	Describe how the user experience of the discovery is evaluated and improved. Include methods of gathering user feedback and reporting back to member libraries.
19	D.8 Platform management	Explain how frequently the global discovery index is updated, including the effect re-indexing has on end users. Include information about the time needed for changes at the local level to be reflected in the global index.
20	D.8 Platform management	Describe the current size and scope of the central index. Provide a list and count of the vendors (publishers/aggregators) in the index. Provide access to a file that lists the journal and newspaper titles included in the central index with ISSNs, dates of coverage, and level of indexing.
21	D.8 Platform management	Describe the discovery tool ability to provide comprehensive knowledge base that is automatically updated when vendors change metadata and content in their proprietary databases (e.g. resources from vendors such as ProQuest, EBSCO, Jane's Defence, LexisNexis, and others). Knowledge base must also be library-editable for additions of non-standard resources for complete integration and indexed discovery and access to all licensed and local-databases, and eBooks, eAudio-books, etc.
22	D.8 Platform management	Describe any ebook publisher agreements. List and describe any major publisher or aggregator agreements that are especially significant for the discovery service. Include information regarding open access ebooks and journals
23	D.8 Platform management	Explain the overall strategy for additions of content to the central index.
24	D.8 Platform management	List which data formats and metadata schemas the central index is able to import, including MARC, EAD, MODS, METS, TEI, KBART, Dublin Core, etc.
25	D.8 Platform management	Explain how the structure allows for locally managed resources to be administered at the Consortium level, along with the ability to configure individual library instances. Include the strategy for accommodating Consortial subscriptions and the varied needs of the member libraries.
26	D.8 Platform management	Describe how quickly and often administrative changes are reflected in the discovery results (e.g., turning on and off databases and customization of the interface).
27	D.8 Platform management	Describe how the discovery product provides full accessibility to users with disabilities under Section 508 of the Rehabilitation Act and Minnesota’s own accessibility standards.
28	D.8 Platform management	Describe the ability of the discovery product to to document and promptly assist customer with expunging/removing any links to documents and/or data sources from the Discovery Knowledge Base and/or search results that contains "restricted/classified" government information (for example WikiLeaks releases)
29	D.8 Platform management	Describe the ability of the discovery product to add a new institutions over time
30	D.8 Platform management	Describe the ability of the discovery product to add integrate internal repositories.
31	D. 9 Scoping	Describe the scoping options of the discovery service, including the ability to display the collections of a single library, subgroup of libraries, or the Consortium as a whole. Describe how the user navigates between the scopes
32	D. 9 Scoping	Describe the ability of the discovery product to provide separate interfaces depending on patron type.
33	D. 9 Scoping	Describe the options for promoting results relevant to the user’s affiliation and location. Include any information related specifically to Open Access ebooks, journals, and textbooks and their scopability.
34	D. 9 Scoping	Describe the Integration/interconnected with Content Management Systems such as Content DM, D-Space, LibGuides, etc.
35	D. 9 Scoping	Describe the ability of the discovery product to create customizable controlled vocabularies used throughout site to filter content.
36	D. 9 Scoping	Describe the ability of the discovery product to provide patron personalization tools, such as saved searches, reading lists, etc.
37	D. 9 Scoping	Describe the ability of the discovery product to provide a responsive web design (RWD) to accommodate various device platforms.
38	D. 9 Scoping	Describe the ability of the discovery product APIs and provide examples of the API capabililty to pull together curated lists of electronic and physical items (to include cover art), and local and web content.

AU-LES Library Management System Functional Requirements, &"-,Bold"Section D&"-,Regular" &"-,Bold"CATEGORY: Discovery

E. ERM & Auth & Licenses

	Sub Categories	ERM, Authentication, Licenses
1	E.1 Authentication	Describe how the LSP integrates with EZproxy or other proxy tools (e.g., Can the LSP generate EZproxy config file formatted data (i.e., EZproxy stanzas)?).
2	E.1 Authentication	Describe how the system responds when a link does not produce expected results or provides an incorrect full-text resource.
3	E.1 Authentication	Describe how the LSP automatically authenticates patrons to ensure their eligibility and good standing when they submit resource sharing requests.
4	E.1 Authentication	Describe how users with multiple affiliations are supported in the LSP, with respect to authentication, permissions assignment to their account, and permissions on their accounts.
5	E.2 ERM	Describe how non-traditional digital content will be managed, including but not limited to streaming audio, streaming video, digital humanities projects, statistical datasets, archival materials and individual institutional repositories both public and private.
6	E.2 ERM	Describe how the LSP notifies library staff if a resource is paid for but not made available.
7	E.2 ERM	Describe how electronic resource management records link to and interact with other resource records as well as license, order, and administrative/contact

information.

8	E.2 ERM	Describe the system’s process for updating records and performing coverage updates using external data. How are individual titles “matched” to incoming external data and identified for updating? How are multiple ISSNs/ no ISSNs and alternative titles handled?
9	E.2 ERM	Describe the system’s ability to support the creation, updating, storing, displaying, and reporting of internal and public notes for electronic resource management records.
10	E.2 ERM	Describe how the LSP enables exports of electronic resource records or lists for integration into library Web spaces or catalogs, such as the A-Z or external tools such as Springshare LibGuides.
11	E.2 ERM	Identify the national and international standards for electronic resource management that the system supports.
12	E.2 ERM	Describe the ability of the system to limit views and or privledges of access for restricited data i.e read vs edit.
13	E.3 Knowledgebase	Describe how bibliographic records for electronic resources can be managed from the knowledgebase.
14	E.3 Knowledgebase	Describe if the system indexes electronic resource data separately from normal bibliographic data. How is the electronic resource data displayed to the public if desired?
15	E.3 Knowledgebase	Describe how the knowledgebase operates at consortial, subgroup, and individual institution levels. In a consortial environment, some resources may be shared across libraries, but individual libraries will also have local collections under locally negotiated license terms. Coverage may also vary depending on acquisitions history. Describe how an individual library will manage its own knowledgebase or work within a shared knowledgebase.
16	E.3 Knowledgebase	Are there features or fields in resource records to describe the relationship between related electronic resource records, such as part of a

package, or a merger of multiple packages?

17	E.3 Knowledgebase	Is this a non-bibliographic “database or package level” record used to attach acquisition information and ERM data or is this also a bibliographic record with MARC fields? If bibliographic data is provided, are CONSER standards followed?
18	E.3 Knowledgebase	Describe how frequently the knowledgebase is updated based on vendor data. Describe how the quality of the knowledgebase is assured, (e.g., date coverage, links, etc.) Describe user community involvement in the maintenance and management of the knowledgebase. Provide a list, in electronic format, of publisher/providers currently represented in the knowledgebase and any other pertinent details.
19	E.4 License management	Describe how libraries within a consortium can build, modify, and share license agreement templates.
20	E.4 License management	Describe the support for the management of license agreements at the individual library, subgroup of libraries, and consortium levels. Include information about how scanned copies of executed licenses are stored and linked to license records.
21	E.4 License management	Describe how license management functionality integrates with acquisitions functionality (e.g., describe how users can link an order record to multiple related license records and vice versa).
22	E.4 License management	Describe how the LSP enables management of related licenses, such as parent-child licenses or master agreements and addenda including renewal at the individual library, subgroup of libraries, and consortium levels. Describe how license management functionality integrates with acquisitions functionality (e.g., describe how users can link an order record to multiple related license records and vice versa).
23	E.4 License management	Describe how license terms can be displayed or suppressed from public view. Describe how terms are displayed, or otherwise integrated, in other functional areas, such as acquisitions or resource sharing.
24	E.4 License management	Describe how the LSP enables license term searching.
25	E.4 License management	Describe how the LSP supports tracking of and compliance with licensing agreements.
26	E.5 Reports	Describe how the LSP supports the ability for usage statistics harvesting, including COUNTER and SUSHI.

Functional Requirements, &"-,Bold"Section E&"-,Regular" &"-,Bold"CATEGORY: ERM, Authentication, Licenses

F. Resource Sharing (ILL)

	Sub Categories	Resource Sharing
1	F.1 Electronic delivery	Describe support and workflow for electronic delivery of articles to websites and directly to patrons. Note browsers supported, additional software needed, formats supported and file size allowed. Describe electronic delivery controls on patron or library staff use. Address copyright warning notification, number of views, length of time that the article is available for viewing.
2	F.1 Electronic delivery	Describe electronic delivery controls on patron or library staff use. Address copyright warning notification, number of views, length of time that the article is available for viewing.
3	F.1 Electronic delivery	Describe support for the delivery of ebooks.
4	F.1 Electronic delivery	Describe how the LSP supports document delivery services. Address how the LSP distinguishes document delivery patrons from other patrons and document delivery requests from interlibrary loan requests.
5	F.1.a Electronic delivery - copyright compliance	Describe how the LSP supports copyright compliance. Note how the LSP requires patron acceptance of copyright restrictions, borrowing library indication of CCL (complies with copyright law) or CCG (complies with copyright guidelines) and display of this information on lending requests.
6	F.2 Loan Request Management	Describe how the LSP can support a configurable “place hold” button that does not display if items are non-circulating or on reserve.
7	F.2 Loan Request Management	Describe how individual libraries can modify parameters that control their patrons’ requests. Address how libraries can limit their patrons' active requests.
8	F.2 Loan Request Management	Describe how libraries can permit or prevent requests from their patrons for locally available items.
9	F.2 Loan Request Management	Describe how libraries can permit or prevent duplicate requests from their patrons.
10	F.2 Loan Request Management	Describe how the LSP generates notices to patrons when borrowed items arrive, become overdue, are/are not renewed, etc.
11	F.2 Loan Request Management	Describe the ability to create temporary circulation records for ILL items coming from a non-Army University Library Enterprise System library.
12	F.2 Loan Request Management	Describe how the LSP integrates circulation and resource sharing to track loans. Address loans of items borrowed from other libraries and loans of items lent to other libraries.
13	F.2 Loan Request Management	Describe how the LSP organizes borrowing and lending requests. Address searching for requests, status types, and individual and batch updating of requests. Note how the LSP employs a message file or similar mechanism to help staff manage requests efficiently. Address how the LSP handles messages between libraries. Describe how the LSP logs, stores, and displays transactions for each request. Note how the LSP refreshes the display with updated information.
14	F.2 Loan Request Management	Describe how the LSP manages loan requests for both borrowing and lending libraries, including integration with circulation. Address how the LSP determines due dates, supports patron- initiated and staff-initiated renewal requests, tracks overdues, and supports recalls.
15	F.2 Loan Request Management	Describe how the LSP provides reasons when libraries respond no to requests. List the supported reasons. Indicate whether reasons for responding no are included in requests and whether individual libraries can customize reasons for responding no.
16	F.2 Loan Request Management	Describe how the LSP supports expiry of requests and how expiry may be suspended.
17	F.2 Loan Request Management	Address how the system balances the routing of requests among Consortium members and other libraries. Describe how the LSP supports the option of a lender of last resort.
18	F.2 Loan Request Management	Describe how the LSP determines due dates and hold priority at the consortial level given numerous global and library-specific shelving locations, categories of patrons, and material formats.
19	F.2 Loan Request Management	Describe how individual libraries can suspend resource sharing services temporarily. Note how libraries can suspend borrowing, lending, or both. Address how the LSP notifies patrons if they try to submit requests when their library’s borrowing service is suspended. Describe how the LSP routes requests when one or more libraries suspend lending.
20	F.2 Loan Request Management	Describe how the LSP archives terminal requests and how staff can search for and display them. Address how the LSP supports the eventual removal of personal identifying information from terminal requests to protect patron privacy.
21	F.2.a Loan Request Management - eBooks	Describe how the LSP handles requests for ebooks and circulates ebooks for borrowing and lending.

F.2.a Loan Request Management - eBooks

Describe support for the delivery of ebooks.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.