Table of Contents cont. B. Cataloging 28 B-1. Introduction 28 B-2. Basic Questions 28 B-3. Cataloging Documentation 30 B-4. Cataloging Reports 31 B-5. Editing 31 B-6. Z39.50 Capabilities 32 B-7. Bibliographic Control Requirements 32 B-8. Item Record Requirements 34 B-9. Creating Item Records 36 B-10. Linking 37 B-11 Access Restrictions 38 B-12. Authority Control Requirements 39 B-13. Editing of Authority Records 41 B-14. See References 42 B-15. Cataloging Reports 43 B-16. Global Change 44 B-17. Global Change Reports 45 B-18 Conversion Process 46 C. Circulation 47 C-1. General 47 C-2. Security 48 C-3. Profiling 48 C-4. Searching 49 C-5. Checkout and Checkin 50 C-6. Recalls, Holds and Searches 52 C-7. Reserve Room 52 C-8. Fines and Accounting 54 C-9. Patron (or Borrower) Files 55 C-10. Notices 56 C-11. Conversion Process 57 D. Digital Media Archiving 58 E. Interlibrary Loan 59 E-1. Overview 59 E-2. General Capabilities 59 E-3. Interfaces with Related Systems 60 E-4. Integrated Management 61 E-5. Copyright Compliance 63 E-6. Borrower Billing Capabilities 63 11
The screen name/icon should be displayed consistently throughout the acquisitions module so that an operator is able to identify the current application. The Acquisitions module should provide a view of structures for serial items that are parent records, memberships or combinations, or parts of a monographic series. QUESTION: How does your acquisitions module handle donations and gifts? A-3. Searching The system must be able to search existing purchase orders, main catalog, and cataloging work files. The system must be able to autoprompt for searching all files. The system must be able to search all files without re-keying the search. The system must be able to search existing orders by author, title, PO number, vendor name, vendor code, ISBN/ISSN, LC card number, OCLC number, or local control number. The system must be able to recall the last search entered. The system must be able to scroll forward and backward through a list of orders or items in the OPAC. The system must be able to display bibliographic information m MARC format. A-4. Ordering The system must permit the order file to include but not be limited to the following data: purchase order number item number library location vendor order type order condition order date
The system must be able to display history of an order's conditions. The system must be able to create pseudo orders. The system must be able to create new order records. The system must be able to use existing bibliographic record or an existing order record as a template for a new order. For each purchase order, when applicable, the system must be able to default the material and format codes into the order record from the bibliographic record. The system must be able to perform checks on titles with duplicate ISBN/ISSN numbers, warning if an order already exists. The system must be able to provide for Library- defined subject codes. The system must be able to provide for Library- defined sort The system must be able to generate an order in real-time. The system must be able to provide a flag to control the transfer of bibliographic information from an order record to the OPAC. The system must be able to warn if a vendor that has a status of inactive is specified on an The system inust be able to create a single open purchase order for multiple orders from a single vendor. The system must be able to provide note fields in the purchase order record for handling, processing, etc. The system must be able to permit the Library to create and assign, automatically or manually, action codes to control processing steps for each individual order record. The system must be able to generate multi-line purchase orders from separate requests to a single vendor. The system must be able to update an open order. The system must be able to change the fund allocation on an open order.
category, amount of time spent by each user connected to each specific database or destination, total number of searches, total number of retrievals, and the time of day of access. The gateway must automatically determine whether the client to be invoked when a destination is selected is resident on the server or on the desktop. If the client software resides on the desktop workstation, it must be invoked automatically and must communicate with the external database or service without any host server involvement. For fee-based services, the system must provide the option to prompt for account ID and password before connecting. G-9. Display The Library should be able to easily modify all record display screens to suit its needs and preferences, including the selection, order, and captions of displayed fields. For example, on the screen showing the results of a call number search, the Library should be able to define what data elements accompany the call number. OPAC displays must be and easy to read. System should support character display at terminals for the visually impaired. System times out and returns to the welcome screen following a specified period of inactivity. System must allow Library to define menus, summary screens, and bibliographic and item record displays. System must allow the user, through simple menus and/or search queries, to determine: if items are owned where they are located whether or not they are available, with item's status in real time QUESTION: Are any limits on the size of field labels and display constants or on the number of uniquely definable labels and display constants? If yes, what are they? QUESTION: What hardware/software if any, can your system interface with for physically impaired users?