Serial/Binding Demo: Checkin

# Situation name Situation description Objective Orbis? # Notes
1 Re-sorting analytic title display in staff view Example: Monograph series (United States Catholic Historical Association). Main series bibliographic record: Orbis ABZ0607; analytics: Orbis FHP4014, ACC1791, FKE1327, PLN4781, DBX9975, ABV0567, ABV4396, DAE2924, DCJ7830, ACC4092, DDM1742, ACB9779, ABJ6490, ACD4354, ACE9577, ACD4010, PLM5746, ACC3259, DDV6723, ACD2267, ABK1106, DCQ5548, DCQ0503. In staff mode, search by series title, which should retrieve both the main series record & the analytics. a. What determines default index display arrangement: vol. no., title, date of publ., other? b. Can default display arrangement be modified at system level? c. Can staff rearrange the default staff view index display by: vol. no., alphabetically by title, date of publ., other options? d. Does staff view determine the display arrangement in the OPAC, or vice versa, or are the 2 views independent? Determine flexibility of index display for analytics in staff view; determine whether checkin staff can manipulate or customize the index display or whether this capability is limited to systems staff, or whether the system has a set display order that cannot be adjusted. Determine relation of staff view to OPAC view. N 1  
2 Series/analytic relationship in staff view display For the scenario described above, what is the default position of the main series within the index display in relation to the analytics? At the beginning of the display? The end? Within the alphabetic sequence? Which MARC field determines main series position in the index display: 130 or 245? Indicate whether and how staff can control the position of the main series in the index display in relation to the analytic listings. Determine where main series displays in relation to analytics, and whether staff may control its position relative to the analytics. N 2  
3 How system indicates a series is under authority control When records for a monographic series are retrieved in the bibliographic module, e.g. the example in 1 above, how can staff tell whether the series is under authority control? Cp. 12 below. Determine whether staff can readily ascertain whether a monographic series title is under authority control when searching the bibliographic database.   3  
4 Item record creation Starting from the serial module, show how item records for serial volumes are created, edited, displayed, and sorted for display. Determine whether item records are readily created from the serial module, whether they are easy to edit, and whether their display is easy to interpret and re-sort. Y 4  
5 Entering enumeration & chronology information in the item record Show whether operator can copy enumeration & chronology information from the checkin record to the item record without re-keying or copy-paste (e.g. with a keystroke or click); can system be set to copy from checkin to item record automatically upon completion of a volume, or, alternatively, upon receipt of each issue? Determine level of system support for entering enumeration & chronology info. into the item record N 5  
6 Entering circulation permissions Having created an item record for the serial volume, indicate whether staff may enable circulation permissions in the item record; indicate whether circulation permissions may be automatically enabled based on frequency and enumeration/chronology data already in the checkin record. (Note: Libraries at Yale circulate serials that are less than 10 years old for in-building use only. Serials older than 10 years circulate outside the building. We control this policy now by using different loan codes for each year and then updating the system tables annually). Determine whether staff may readily enable circulation permissions in the item record; determine whether the process is automatic or manual; and if manual, whether complex or simple Y/N 6  
7 Complex item record-bibliographic record associations with serials Demonstrate how staff can associate an item record for a series analytic with the series bibliographic record, the series checkin record, and the bibliographic record for the analytic. Demonstrate the same procedure when the series analytic is an analyzed multipart item and the item record is associated with a vol. of the multipart item (i.e. association for analytic at second level) Determine whether item record can be associated with multiple bibliographic & checkin records at multiple levels N 7  
8 Moving item records to a different location 30 item records are associated with one location; move the last 10 to location 4 for the same title Determine system support of multiple item record relinking from one location to another N 8  
9 Moving item records to a different title 30 item records are associate with one location; move the last 10 to location 1 for a different title Determine system support of multiple item record relinking from one location to another where item records must be associated with a different bibliographic record N 9  
10 Status tracking Yale Library uses a series of charges of item records to processing unit "patrons" in the Technical Services dept to track the status of material from receipt, through cataloging and to preparations. a. Does your system allow use of item records to track issues during technical services processing? b. Does your system have alternative tracking options? (e.g. for an issue in cataloging, on the new periodicals shelf, being bound) Determine how serial issues are tracked Y 10  
11 Changing module view to bibliographic record From a serial checkin record, display its associated bibliographic record; if there are variant views available (e.g. tagged, labeled) please indicate & indicate the default view Determine whether checkin staff can move easily from one module view to another N 11  
12 Changing module view to authority record From a checkin record for a series, display its associated series authority record; if there are variant views available (e.g. tagged, labeled) please indicate & indicate the default view Determine whether checkin staff can move easily from one module view to another Y 12  
13 Changing module view to order/payment record From a serial checkin record, display its associated order/payment record (or each record if they are separate) Determine whether checkin staff can move easily from one module view to another Y 13  
14 Creating a pay statement for a checked in series volume From a checkin record for a monographic series, retrieve an order/payment record & create a payment statement for the issue which has been checked in Determine whether staff can move easily from checkin module to payment module to perform an action Y 14  
15 Changing module view to MARC holdings record From a serial checkin record, display its associated MARC holdings record; if variant views are available (tagged, labeled) please indicate & indicate the default view Determine whether checkin staff can move easily from one module view to another Y 15  
16 Changing module view to item record From a serial checkin record, display its associated item records Determine whether checkin staff can move easily from one module view to another Y 16  
17 Changing module view to OPAC record From a serial checkin record, display its associated OPAC record (which should include bibliographic, volume holdings, checkin data , item status, & public notes generated from any of these staff records); if there are variant views available (tagged, labeled) please indicate & indicate the default view Determine whether checkin staff can move easily from one module view to another Y 17  
18 Creating bibliographic records for series analytics Demonstrate how staff create a bibliographic record for a series analytic after checking in the volume. a. Does the system carry over any data from the checkin record to avoid re-keying (e.g. series, issn, call number)? b. Can the record be created from the serials module (e.g. in a separate window, without closing serials in order to open the bibliographic module)? c. Demonstrate how the operator associates the item record with both the bibliographic record for the series & the bibliographic record for the analytic d. Can the system provide an electronic link between the checkin record and the analytic record? (i.e., can a checkin record, like an item record, be associated with both the series record & an analytic record?) Determine whether checkin staff can easily create a bibliographic record for an analytic & associate it with a checkin record for an issue Y 18  
19 Online help with MARC Show online help features for fixed field values, & for fixed field, variable field, and MARC holdings field definitions. Can staff click in fixed field values and MARC tags from the help file? Determine whether checkin staff can easily access online help features for MARC. N 19  
20 Suppression of bibliographic record, etc. Show how staff may suppress the OPAC display of the bibliographic record and/or associated checkin, item, and MARC holdings records for the series associated with a checkin record. Does each associated record need to be suppressed separately? Show suppressed records from the OPAC. Determine whether staff can suppress display of bibliographic record, etc. & whether associated records are automatically suppressed at the same time Y 20  
21 Suppression of location Show how staff may suppress the OPAC display of a location associated with a checkin record Determine whether staff can suppress display of location Y 21  
22 Note replacing call no. Show how staff may create an OPAC note from the checkin record and substitute the note for a call number; e.g. "Shelved by title" Determine whether note can repl. call no. in OPAC Y 22  
23 Hotlinking earlier/later titles in OPAC Show how & where OPAC user can hotlink from earlier to later title & vice versa in the OPAC   N 23  
             
# Situation name Situation description Objective Orbis? # Notes
1 Binding: Exporting data via EDI (Monographs) Show how to populate an online binding instructions template, using commercial bindery software such as LARS or ABLE. Use bibliographic information from the catalog record for a monograph. Determine if binding data for a monograph can be sent from the local system to an external binder’s system N 1  
2 Binding: Exporting data via EDI (Serials) Show how to populate an online binding instructions template, using commercial bindery software such as LARS or ABLE. Use bibliographic information from the catalog record for a serial. Determine if binding data for a serial can be sent from the local system to an external binder’s system N 2  
3 Label printing: Call number formatting options Does system allow different processing units to print call numbers in different styles? a. Can Library A print call numbers on labels vertically, i.e., with class number on line 1, cutter number on line 2, book number on line 3, date on line 4, etc. while Library B prints call numbers horizontally with class number followed sequentially by cutter number, etc.? b. Can processing unit set default line break, i.e. for an LC class number combination of double letters and numbers, can staff set the default break between the letters & the numbers? c. Can a single processing unit select vertical or horizontal on a case by case basis? d. Can a single operator select style case-by-case? Determine call number formatting options and system flexibility a. Y b. N c. N d. N 3  
4 Label printing: Location stamps Can your system convert a brief location code to a more detailed location stamp when the label is printed?   Y 4  
5 Label printing: Maximum length For a call number formattted vertically, print a label indicating maximum number of lines and maximum number of characters per line. Determine if label program can accommodate long call numbers, long location stamps, etc.   5  
6 Label printing: Copy numbers Show how a copy number can be printed or suppressed. Can the operator set the default? Determine if label program offers flexible defaults regarding the copy number.   6  
7 Label printing:EXAMPLES Print call number on label in vertical format as instructed in the following serial & monographic examples. Line breaks are represented by a single underscore "_ ". Determine if label program can accommodate complex call numbers & special characters Y 7  
8 Label printing: Monograph, single/multiple location For a monograph bibliographic record, generate a call number label, vertical format, location stamp printed above the call number, line breaks as indicated. Call number examples:     8  
9   Single location. Location stamp: SML Call number: ByL_5_ I_ 24:4     9  
#   Single location Location stamp: Music Call number: M219.5_M939+_ K.454_A     #  
11   Single location. Location stamp: Mudd Library Call number: Vg12_ M523_Sa28_1858     11  
#   Single location Location stamp: Art Call number: NJ18_Aa6_A12_FJA_5312E_1991_(LC)     #  
#   Single location. Location stamp: Music Call number:M_1602_S864_A4++     #  
#   Location 2. Location stamp: Art ND1805_+R44_1993_(LC)     #  
15   Single location Location stamp: Music Call number: M_219.5_B664+_G.25-30     15  
#   Single location Location stamp: Microtext Call number: Film_14426:2     #  
17   Single location Location stamp: Music Call number: M_244_C549_N7+_C#min.     17  
# Label printing: EXAMPLE: Input stamps Input stamps are free-text data entered by the cataloger, stored in association with the location code & the call number, often to indicate a sublocation not represented in the library's location tables. In label output, the input stamp prints below the location stamp & above the call number. Example: Music <location stamp generated from location code> Historical Sound Recordings <sublocation stamp generated from location code> H.S.R.<Input stamp entered by cataloger> ML <class letters of call number> 156.7 <class numbers of call number> G478 <cutter number> J5 <book number> Show how your system handles input stamps.     #  
# Label printing: Serial, multiple locations (no vol. no.) For a serial bibliographic record with multiple locations attached, generate a call number label for a single location. Example: Print a label for location 5. Location stamp: Music Call number: AS2_W927+ Determine complexity & number of steps needed to generate label when multiple locations occur & no vol. number should be printed; does presence of item record w/vol. no. affect label program when no vol. no. should be printed? Y? #  
# Label printing: Serial, single location (vol. no.) For a serial bibliographic record with only one location attached, generate a call number label for a single volume. Example: Journal of Baltic studies (ABY6865) Generate a call number label with item record for v. 5. Determine complexity & number of steps needed to generate label when multiple locations occur & vol. number should be printed Y #  
# Label printing: Editing Show how operator can modify output on label. Example: Call number: M2_R295+_ v.63. Change to: M2_R295+_ v.63-63a Determine flexibility of printing program Y #  
# Label printing: Printer equipment Can your label program run on our current printer: Lexmark 2390 “Straight Path”? If not, please provide a list of system compatible printers. Determine if current label printer equipment is system-compatible Y #  
# Label printing: Label stock Can your label program run on our current label stock: tractor-feed sealing tape and a clear overlay tape, each 1296" long per roll. If not, please provide list of specific label stock system can run. Can it run on different types of label stock, e.g. Avery labels? Determine if current label stock is system-compatible; determine alternative types of label stock. Y #  
# Label printing: Fund code information Show how a fund code can be displayed from the label printing view, for determination of appropriate bookplate Determine if system can cue fund code at point of label-printing, to aid in bookplate selection N #  
# Label printing: Templates For serial or multipart item call numbers where a vol. number is recorded as part of the label, SML sometimes must include the trailing text "(LC)" , i.e. <location> <CALL NUMBER><VOL NUMBER><(LC)>. EXAMPLE: SML BX4700 G35 1986 (LC). For a serial or multipart, the call number with trailing (LC) combination will usually NOT include the vol. number when it is represented and stored with the bibliographic record. In order to generate the label, our current label printing program retrieves this call number and inserts the vol. number, which is stored separately in the item record. However, our current program is unable to insert the vol. number between the call number and (LC), so additional editing is required for every vol. label printed for serials or multiparts where the trailing (LC) is used. We also have a problem with subseries situations where the vol. number IS included in the call number as stored in the system, but which cannot be used in that form on the labels for individual volumes, e.g. SML BX470 Determine if a series of call number labels can be produced with minimal or no rekeying. Determine from where in the record the label program derives the volume number N #  
#   Demonstrate whether your system can generate a series of labels for a serial or multipart call number with an internal variable, i.e, whether your system provides for the creation of a macro or template that allows the operator to specify that only a segment of the call number as stored be used to create the label when it is combined with data from the item record and then automatically adds the trailing data ("(LC)" or any other specified text) to the end of the string.     #  
# Binding: Statistical reports Show how staff can access statistical reports for: Determine if staff can generate online, in-house statistical bindery reports. N #  
#   Number of pieces checked in/out within a given time frame     #  
#   Number of pieces checked in/out by a given check-in person     #  
#   Number of pieces checked in/out by a given receiving location     #  
#   Number of pieces checked in/out by a given material type     #  
#   number of volumes overdue for return from the commercial bindery     #  
# Binding status If the system binding module has a binding status, indicate what information is made available in the OPAC (e.g. vol. detail; date sent; date expected) Determine information captured from binding status which is displayed in OPAC.   #  
# Situation name Situation description Objective Orbis? # Notes
1 New bibliographic record for serial title change The serial publication Theology & public policy (Orbis FFV0660; OCLC 20460775) has changed title to Shalom papers (Orbis FMG2887; OCLC 40893323). For purposes of our demo, there is no bibliographic record for Shalom papers in our local online catalog, and in order to create a checkin record for Shalom papers, an associated bibliographic record must be made available. Show how a new bibliographic record may be entered & associated with the new checkin record using the following 3 techniques: Demonstrate how serial checkin staff can create bibliographic record to associate with new checkin record when title change occurs with particular attention to ease/difficulty of changing modules N 1  
2 New bibliographic record A: Bibliographic record for new title created by downloading from OCLC (and RLIN if possible); indicate whether bibliographic record may be imported from a local resource file; from a vendor supplied electronic record)   Y 2  
3 New bibliographic record B: Brief (245/260/780) bibliographic record for new title created via data-entry; indicate online help support (e.g. pull down menus) for fixed fields and variable tagging, indicators, & subfields; alternatively, if a brief bibliographic record can be automatically generated from a new checkin record, demonstrate.   Y 3  
4 New bibliographic record C: Bibliographic record created by deriving and editing data from the catalog record for Theology & public policy. New record should include new title, place of publication, link to old title   Y 4  
5 New checkin record with no associated bibliographic record ALTERNATIVELY, derive and edit data from the checkin record for the old title to create a temporary checkin record for the new title, with no associated bibliographic record. New checkin record should include new title, place of publication, and link to old title. Determine whether a checkin record can be created and displayed in staff and public view without creating an associated bibliographic record N 5  
6 Hotlinking earlier/later titles Show how earlier/later titles for bibliographic records described above are hotlinked via 780/785 MARC fields in staff mode, whether there is corresponding linkage in the OPAC, whether hotlinking is automatically based on field tag or must be enabled by staff, & whether there is corresponding linkage in the checkin records Determine whether system provides hot-link web features in staff mode for earlier/later titles for bibliographic, checkin, and OPAC records, and level of system support. N 6  
7 Hotlinking complex earlier/later titles: A If hotlinking staff records is feasible, show how earlier/later titles are hotlinked when an earlier title splits into 2 titles. Demonstrate corresponding linkage in OPAC, whether hotlinking is automatically based on field tag or must be enabled by staff, & whether there is corresponding linkage in the checkin records. Same as 6., but for a more complex situation. N 7  
8 Hotlinking complex earlier/later titles: B If hotlinking staff records is feasible, show how earlier/later titles are hotlinked when 2 earlier titles merge into one. Demonstrate corresponding linkage in OPAC, whether hotlinking is automatically based on field tag or must be enabled by staff, & whether there is corresponding linkage in the checkin records. Same as 6., but for a more complex situation.   8  
9 Hotlinking title in different formats If hotlinking staff records is feasible, show hotlinking via 776 MARC fields of a title represented by 2 different records, one for the paper format and one for the microfiche record. (Orbis AEC9917 and FMU4715 Calendar of business). Demonstrate corresponding linkage in OPAC, whether hotlinking is automatically based on field tag or must be enabled by staff, & whether there is corresponding linkage in the checkin records. Determine whether 776 can generate hotlinks for the same title in different formats.   9  
10 Retroactive title change Title change is not noticed by checkin staff until 2 volumes of the new title have been checked in under the old title. Transfer checkin and order/payment data from old record to new record, and relink item records. Determine level of automated support for title change maintenance activities Y (but labor intensive) 10  
11 Undoing title change After a presumed title change, checkin staff have created a new bibliographic & checkin record and checked in issues for the supposedly new title. Upon review, the cataloger decides that the title did not actually change. Show how staff may transfer data from the checkin record (and MARC holdings if necessary) to the old title, delete or suppress the new checkin & bibliographic records, & re-link any associated records (e.g. subscription orders) to the old title. Demonstrate whether staff may easily undo the creation of a new title record, and easily transfer checkin data from that record to an old title record; demonstrate whether all changes related to undoing the title change may be initiated from the checkin model or whether multiple protocols are required N 11  
# Situation name Situation description Objective Orbis? # Notes
1 MARC holdings creation (853-865) Using MARC 853-865 fields, create holdings for v. 1 (1990)-v. 10 (1999), supplement to v. 3 (1992) and index for v.1-10 for a monthly serial title. Determine how MARC holdings for basic bibliographic units, supplements and indexes are created according to MARC21 Format for Holdings Data (2000 ed.) and ANSI/NISO Z39.71-1999 for detailed holdings (level 4); determine level of difficulty & system support N 1  
2 Captions & calendar division database For scenario described in 1., staff should be able to access (e.g. via menu) and import from a caption and calendar division database consisting of prescribed abbreviations & capitalization. a. Can the appropriate text derive automatically to the appropriate subfields based on the language code of the associated bibliographic record? b. If not, how is the data imported? (e.g., clicking on pull-up menu? Are keyboard alternatives to mouse clicking available?) c. Can the database be updated, and at what level? (vendor only? local systems staff? authorized staff?) Determine whether system provides caption/calendar division database; whether data can be imported automatically; means of access; how updated. N 2  
3 MARC holdings display Based on the MARC holdings created in situation 1, a. In both staff & OPAC modes, display MARC holdings in compressed form; display MARC holdings in non-compressed form (individual vols.; individual issues) b. In staff mode, display MARC holdings compressed/non-compressed in both tagged and labeled formats. If the default view (e.g. labeled) is set by the system, can staff change the default view? Determine MARC holdings display options in staff mode and in OPAC. N 3  
4 OPAC holdings display combining checkin of incomplete vol. and MARC holdings Based on MARC holdings created in Situation 1, check in current issues for v. 11, no. 1-8, Jan.-Aug. 2000 on the checkin record. Show how OPAC display combines current issues from checkin record and bound volumes, supplements and indexes from MARC holdings record Determine how MARC holdings & checkin record interact in the OPAC display Y 4  
5 Update of MARC holdings from checkin record Based on Situation 3, check in additional current issues for v. 11, no. 9-12, Sept.-Dec. 2000 on the checkin record. a. Demonstrate if v. 11, no. 1-12 can be compressed or collapsed into MARC holdings record as v. 11 (2000) without re-keying, and whether this needs to occur prior to or after binding. b. Then demonstrate if v. 11 (2000) on MARC holdings record can be expanded into individual item listing for v. 11, no. 1-12. Determine whether system allows staff to update MFHD from checkin record without re-keying; determine where binding fits into the MFHD updating process; determine whether staff can control compression/expansion of MFHD display. N 5  
6 Caption/Pattern changes (853-855) Using the above scenario, suppose that when Jan. 2001 issue arrives, the numbering has changed to new series, v. 1, no. 1 and the frequency has changed from monthly to bimonthly. Modify the Caption/Pattern field (853) to reflect the current captions and publication pattern. a. If the enumeration & frequency are updated on the checkin record, can the 853 be updated automatically? b. If the enumeration & frequency are updated in 853, can the checkin record be updated automatically? c. Can the enumeration & frequency be updated in the checkin record without updating the 853 field? Determine how the Caption/Pattern field is updated; determine how the Caption/Pattern field interacts with the checkin record. N 6  
7 Holdings update for new volumes (853/863) Using MARC 853/863 fields, create holdings for v. 1 (1997)-v .2 (1998) and v. 3, no. 1 (1999:Spring) for a semiannual serial. Check in v. 3, no. 2, Fall 1999, which completes v. 3. Demonstrate how MARC holdings are updated to show that v. 3 is complete Determine how MARC holdings are updated for new volumes. N 7  
8 Holdings update for gaps (853/863) Using MARC 853/863 fields, create holdings for v. 1 (1997), v. 2:no. 2 (1998:Apr.), v. 2:no. 4 (1998:Oct.) and v.3 (1999) for a quarterly serial. Check in v. 2, no. 1, Jan.1998 and v. 2, no. 3, July 1998 issues which complete v.2. Demonstrate how MARC holdings are updated to show that v. 2 is complete. Determine how MARC holdings are updated when back issues are received to fill the gaps. N 8  
9 Holdings creation (866-868) Using MARC 866-868 fields, create compressed holdings for v. 1 (1990)-v. 10 (1999), supplement to v. 3 (1992) and index for v.1-10 of a monthly serial. Determine how MARC textual holdings for basic bibliographic units, supplements and indexes are created. Y 9  
10 Holdings update for new volumes (866) Using MARC 866 fields, create holdings for v. 1 (1997)-v .2 (1998) and v. 3, no. 1 (1999:Spring) for a semiannual serial. Check in v. 3, no. 2, Fall 1999, which completes v. 3. Demonstrate how MARC holdings are updated to show that v. 3 is complete Determine how MARC textual holdings are updated for new volumes. Y 10  
11 Holdings update for gaps (866) Using MARC 866 fields, create holdings for v. 1 (1997), v. 2:no. 2 (1998:Apr.), v. 2:no. 4 (1998:Oct.) and v.3 (1999) for a quarterly serial. Check in v. 2, no. 1, Jan.1998 and v. 2, no. 3, July 1998 issues which complete v.2. Demonstrate how MARC holdings are updated to show that v. 2 is complete. Determine how MARC textual holdings are updated when back issues are received to fill the gaps. Y 11  
12 Holdings transfer Demonstrate whether partial or complete holdings data can be transferred from one copy to another for the same title or from one title to another. Also demonstrate whether the Caption/Pattern data (853) alone can be transferred from one title to another. If possible, demonstrate whether the Caption/Pattern data can be transferred from the network (OCLC/RLIN) to the local system. Determine whether holdings data can be transferred easily and efficiently. N 12  
13 Holdings deletion/suppression Demonstrate how to delete partial or complete holdings data from the MARC holdings record and how to suppress partial or complete holdings data from OPAC display. Determine whether holdings data can be easily deleted or suppressed Y/N 13  
14 “Shelved as” The periodical “Developmental brain research” (Orbis ACP6438) is issued as a section of the periodical “Brain research” (Orbis ABY9405). Create MARC holdings for “Developmental brain research” to show that v. 1 (1981) is shelved as v. 227 of “Brain research,” v. 2 (1982)-v. 4 (1982) are shelved as v. 254-v. 256 of “Brain research” and v. 5 (1982)-v. 9 (1983) are shelved as v. 281-v. 285 of “Brain research.” Create item record for v. 227 and link it to both bibliographic records. Determine how MARC holdings for a serial (or subseries) within a serial (or main series) are entered and whether the item records can be linked to both bibliographic records. Y/N 14  
15 Notes for public in MFHD Annual report of the secretary of agriculture (Orbis FMB2987; FMU1641) is received in fluctuating formats: sometimes microfiche, sometimes paper. a. Show how staff can enter a general OPAC-displayed note in the MFHD for FMB2987 (MFHD for the microfiche format) with the following text: See paper format record for additional holdings. b) Show how staff can enter a corresponding general OPAC-displayed note in the MFHD for FMU16419 (MFHD for the paper format) with the following text: See microformat record for additional holdings. c. The MFHD subfield z (public) note may be used with different MFHD variable fields, e.g. 852, 866. Show how the same text displays in the OPAC depending on which MFHD variable field is utilized. If 866 is used for the public note & volumes are recorded in both 866 & 863 (or just 863), how is the note display affected? Determine how public notes are entered and displayed in MFHD; simple or difficult? How does variable field selection determine display of note in OPAC? Y/N 15  
16 Notes for staff-only in MFHD For the same title, a. Show how staff can enter a staff-only note in the MFHD for FMB2987 (microfiche) with the following text: Add paper copy to MFHD <record number of the paper copy> b. Show how staff can enter a staff-only note in the MFHD for FMU1641 (paper) with the following text: Add microformat copy to MFHD <record number of the microfiche copy> c. Does a nonpublic note entered in MFHD also display in the checkin record? MFHD subfield x (nonpublic note) may be used with different MFHD variable fields, e.g. 852, 866. Would the variable field selected have an effect on note display in the checkin record? Determine how staff notes are entered and displayed in MFHD; simple or difficult? Whether note also can be used in checkin record. Whether variable field selection would affect display in checkin record. Y/N 16  
17 MARC holdings for irregular serials Demonstrate how MARC holdings for irregular serials should be created. Should we use MARC 853/863 fields? Can we set up the publication pattern field (853) for an irregular serial? For examples of irregular serials, see the periodicals “Biochimica et biophysica acta” (Orbis ABY9343/OCLC#1536398) and “Mutation research” (Orbis ADF7796/OCLC#1590350) Determine how MARC holdings for irregular serials should be created and whether publication pattern can be set up for irregular serials. N 17  
18 Displaying old MARC holdings (converted from NOTIS MHLD) with the new MARC holdings created in the new system Use the periodical “Science (weekly)” (Orbis ABZ0825/OCLC#1644869) as an example. Suppose that after the NOTIS MHLD for the 1st location is converted, we begin to create new MARC holdings using the 853/863 fields for the current vols. Demonstrate how the old holdings from NOTIS (all in 866 fields) and the new holdings (in 853/863 fields) are displayed in staff mode and in OPAC. Determine how the old MARC holdings (converted from NOTIS MHLD) and the new MARC holdings created in the new system are displayed in staff mode and in OPAC. N 18  
# Situation name Situation description Objective Orbis? # Notes
1 Relation of claiming to checkin & MFHD For claiming to function, is it sufficient for the predictive pattern to be set up in the checkin record, or must publication pattern in MFHD (MARC Format for Holdings) field 853 need to be entered as well?   N 1  
2 Claim without predictive pattern Demonstrate how operator can set up a claim not based on the publication pattern of a title, e.g. a standard default claiming period when publication pattern is unknown Determine system support for standard default claiming period not tied to actual publication pattern Y 2  
3 Automatic claiming when issue is skipped on checkin For a title held at one location, issue 1 has been received on checkin and issue 3 arrives; show whether system can automatically print a claim form for the missing issue 2 Determine how system automatically claims an issue from a publisher if it is skipped on checkin with an example of printed form output. N 3  
4 Automatic electronic claim on skipped issue For a title held at one location, issue 1 has been received on checkin and issue 3 arrives; show whether system can automatically prepare an electronic claiming form for the missing issue 2 Determine how system automatically claims an issue from a publisher if it is skipped on checkin via an electronic message. N 4  
5 Automatic claiming when copies are missing on checkin For a title held at 4 locations, issue 1 has been received on checkin for all 4 locations and issue 3 arrives for only 1 location; show whether system can automatically claim (print and/or electronic) the 3 missing issue copies of issue 2 For the scenarios described in 1 & 2, show how the system automatically claims multiple copies of an issue from a publisher when a title is skipped N 5  
6 Overriding automatic claiming for a single issue For either of the 2 multiple location scenarios above, it turns out that the subscription for location 2 has been cancelled; show how the claim for issue 2, location 2 may be blocked (print and/or electronic) Determine how system allows an automatic skipped issue claim to be temporarily overridden for a single or multiple copies N 6  
7 Overriding automatic claiming permanently (global) If general library policy decision is to not implement automatic claiming could this be done at system level?   N 7  
8 Overriding automatic claiming permanently (selective by location) 2 of the 4 multiple locations do not want automatic claiming implemented; show how the system can turn off automatic claiming for these locations permanently Determine how system allows automatic claiming to be permanently suspended on a selective basis N 8  
9 Overriding automatic claiming permanently (selective by title & location) Title is on subscription at location 1 but location 2 receives some second copies of some issues as gifts. Subsequent issues for the title on location 2 should not appear on claim reports or be claimed automatically. Can staff override the claim permanently? If a decision is later made to initiate a second subscription for location 2, can claiming then be resumed? Determine how system allows automatic claiming to be permanently suspended & then resumed on a selective basis N 9  
10 Automatic staff notice for skipped issue For a title held at one location, issue 1 has been received on checkin and issue 3 arrives; show how the system notifies staff to claim the issue; can staff be prevented from checking in issue 3 if the skip is unacknowledged? If system does not allow automatic claiming, show how system flags skipped issues for staff attention N 10  
11 Staff initiated claim For the scenario above, show how staff claim the issue with a mouse (and with keystrokes) for a printed form; for an electronic form Determine "manual" claiming to indicate level of complexity, keystroke alternatives, different outputs. Y 11  
12 Staff initiated claims on multiple copies For a title held at 4 locations, issue 1 has been received on checkin for all 4 locations and issue 2 arrives for only 1 location; show whether staff need to claim (print and/or electronic) each copy separately or whether system allows staff to process claims on multiple copies as one Determine whether system supports staff initiated multi-copy claiming N 12  
13 Standard claim memo messages Show how standard claim memo messages are created, edited, and invoked in the claim memo; indicate whether authorized unit staff can create and update these messages or whether the messages are set at system level Determine system support of standard claim messages Y 13  
14 Customizing claim memo messages Show how a non-standard specific claim message can be created by an operator; show how a standard claim message may be edited for a specific situation by an operator Determine how claim messages may be customized for a specific situation Y 14  
15 Automated notification of late issue Issue 3 of a quarterly has not arrived when it normally would, but since issue 4 has not arrived, it cannot be detected as "skipped." Show how the system notifies staff that issue 3 is late. Determine system notification for late issues. N 15  
16 Batch claim (Printed) Show how staff can claim all skipped and late issues not delivered by a specific vendor (e.g. Ebsco) for Aug. 2000 in one printed memo. Staff should be able to initiate the claim at any time, given proper authorization. Determine whether the system can claim multiple issue copies or multiple title issues from a specific vendor (a dealer in multiple titles from multiple publishers, or a publisher with multiple titles; and not all vendors but just one) for both skipped and late issues for a predetermined period with an example of printed form output. N 16  
17 Batch claim (Electronic) Show how staff can claim all skipped and late issues not delivered by a specific vendor (e.g. Ebsco) for Aug. 2000 in one electronic memo. Staff should be able to initiate the claim at any time, given proper authorization. Determine whether the system can claim multiple issue copies or multiple title issues from a specific vendor (a dealer in multiple titles from multiple publishers, or a publisher with multiple titles; and not all vendors but just one) for both skipped and late issues for a predetermined period with an example of electronic form output. N 17  
18 Automatic batch claim Can the batch claim described in 15. be set to print automatically at set intervals?   N 18  
19 Automatic batch claim scheduling limitations (staff initiated or automatic) What are the scheduling limitations, if any? (e.g. daily? weekly? monthly? quarterly?) Determine scheduling limitations of automatic claiming. N 19  
20 Limiting automatic batch claim by subset Can the automatic batch claim be set to run only for certain locations? Determine whether automatic batch claim may be limited by subset. N 20  
21 Viewing & editing claiming reports Can claims (individual or batch) be viewed and edited online before printing or sending? (e.g., suspension or deletion of a claim prior to submission; adding a priority flag; adding a specific message; changing vendor, changing order number) Determine whether on-line view of claims is available; determine to what extent it may be edited prior to submission. N 21  
22 Relation of report to claim What is the relation of the report to the claim? After editing, can an individual or batch claim be initiated from the online report? Determine relation of online report function to claiming function. N 22  
23 Content of claiming reports What information is included in online claiming reports? (e.g. title, enumeration & chronology, ISSN, claiming history, vendor, publisher, order number, call number). Can the information be customized by processing unit? Determine information recorded in claim report; determine whether it may be customized by processing unit. N 23  
24 Sorting claiming reports Show how claims may be sorted by vendor, for each vendor by publisher, for each publisher by title in both electronic and printed versions. Indicate other sorting options, e.g. by library location, by order number, by title, by no. of times claimed. Determine whether claiming reports may be sorted and/or limited by vendor or publisher, date, etc.? N 24  
25 Sorting claiming reports by subset Show how a claim report may be limited by subset, e.g. limiting scenario in 21. above to a single location or processing unit. Determine whether claiming report may be limited by subset. N 25  
26 Merging different groups of claims Merge all Ebsco claims for Aug./Sept. 2000 If claims (individual or batch) may be sorted, can different groups be merged? N 26  
27 Recording claims Show where notes on claiming are recorded & indicate space limitations Determine whether claiming notes are easy to enter & retrieve, & whether adequate space is provided Y 27  
28 Viewing & editing claiming history Show how notes on claiming history of a title are accessed, sorted, & edited; indicate whether notes may be printed. Determine whether claiming history may be organized, edited, and printed out N 28  
29 Statistical reports Show how system creates reports based on the following variables: Number of claims generated (vendor & location) Number of claims filled (vendor & location) Number of outstanding claims Number of issues not yet published Determine reporting options for serial claims N 29  
30 Statistical subsets Show how system creates reports based on subsets of the variables above, e.g. for a single location. Determine flexibility of reporting options for serial claims N 30  
31 Alternatives to claiming Some units, e.g. Government Documents, are not able to claim from their supplier. They need an expired action list, where staff enter an anticipated receipt date which is reported as expired if no receipt action takes place on or before that date. However, reports of expired action dates must now be generated at system level. Can your programs allow staff to initiate and customize such reports? Does your system offer other alternatives to claim reports that would provide the equivalent of the expired action list? Determine whether system provides alternatives to claim reports. Y/N 31  
# Situation name Situation description Objective Orbis? # Notes
    Assumption: unless otherwise noted, predictive checkin pattern has been established on the system prior to checkin for all situation descriptions        
1 Retrieving checkin record Demonstrate indexes by which the checkin record may be retrieved: title, ISSN, order number, issuing body. a. Are there additional indexable fields in the checkin record? b. If a bibliographic record is associated with a checkin record, will any field indexed on the bibliographic record also retrieve the checkin record when searching in the checkin module? c. Can the operator add indexable fields to the checkin record that may not be indexed on the bibliographic record, e.g. certain government publication numbers? Determine indexing flexibility of the checkin record Y/N 1  
2 Receive as monograph without checkin For a complete backfile or a sample issue, can a serial issue or issues be received without a checkin record, i.e. as a monograph? Determine whether there are any advantages to receiving a serial title without a checkin record Y 2  
3 Checkin without bibliographic record For a sample or gift issue, does a bibliographic record need to be created in order to checkin the issue, or is a checkin record sufficient? If not, what information from the checkin record will display in the OPAC? What information from the checkin will display in the bibliographic module? See also Title changes #5. Determine link between bibliographic record & creation of new checkin record; effect on OPAC display. N 3  
4 Checkin without MARC holdings If a bibliographic record must exist in order to create a checkin record, is a MARC holdings record required to create a checkin record? Determine link between MARC holdings & creation of new checkin record N 4  
5 Checkin without order/payment record Indicate whether an issue may be checked in without being associated with an order/payment record (e.g. for an "issued with" title, a sample issue, or a title change situation) Note that the next scenario is preferable N 5  
6 Multiple checkin title links to order/payment record Indicate whether an order record may be linked to 2 different serial titles (where serial B is issued with serial A) Determine whether multiple checkin records may be linked to a single order/payment record. N 6  
7 Simple checkin with mouse Show how an issue for a single location is checked in using a mouse. Determine whether checkin system is easy to use, i.e. does not require a complex number of steps and a lot of mousing. N 7  
8 Simple checkin with key strokes Show how an issue for a single location is checked in with key strokes and key stroke combinations only. Determine whether checkin system is easy to use; i.e. does not require a complex number of steps and keystrokes; determine whether keystroke alternatives to the mouse are available for all checkin steps. Y 8  
9 Simple wand checkin Show how an issue with a SICI barcode for a single location is checked in with a barcode reader. Determine whether wand checkin is an option and whether there are any obvious glitches. N 9  
10 Multiple copy checkin Show how 3 multiple copies for 3 different locations may be checked in using options 1-3, where the library has the title in 5 locations. Determine whether system will support expeditious checkin for multiple locations but not all of the multiple locations. N 10  
11 Checkin authorization by processing unit Show how the system prevents staff from one processing unit from adding an issue to a location controlled by another processing unit. Determine whether the system can prevent issues from being checked in to the wrong location. N 11  
12 Overriding checkin authorization Show how the previous scenario may be overridden. Determine flexibility of this aspect of the system. N 12  
13 Re-sorting locations in staff view Where a title has multiple locations, show how locations may be rearranged in staff view (e.g. to rearrange staff view to bring together regular and oversize locations for the same title in the same collection; to rearrange view alphabetically by location). Determine whether the system can rearrange locations in staff view to optimize checkin accuracy and productivity. N 13  
14 Overriding pred. pattern for numerical irregularity Show how the predictive pattern may be overridden for a single checkin which is in sequence (e.g. an unscheduled combined issue). (The New Yorker is a weekly but a subscription is 46 issues with 6 unscheduled combined issues: Orbis ABZ1559/OCLC #01760231) Determine how the system handles numerical sequence irregularities in predictive pattern at point of checkin without causing a claiming error. N 14  
15 How system handles publisher errors in enumeration and chronology Show how predictive pattern for a single checkin handles a situation where issue is misnumbered due to publisher error. (Orbis FFY9902; Title: ENR; a weekly. Staff receive v. 245, no. 5 (2000: Aug. 7) which is issued by the publisher as no. 6. Previous issue was v. 245, no. 4 (2000: July 31). Note that the date for the latest issue received is consistent with the predictive pattern. Is a claim generated? Is the predictive discrepancy between the number and the date flagged? What happens when staff receive the next issue, with correct number & date, i.e. v. 245, no. 6(2000: Aug. 14)? Determine how system handles publisher labeling errors when the issue itself conforms to predictive pattern. N 15  
16 Checking in backfiles w/wout pred. pattern (temporary override or other strategy) Show how the predictive pattern may be applied (or overridden) for a single checkin which is out of sequence with regard to initial date (e.g. backfile issues). Determine how the system handles chronological sequence irregularities in predictive pattern at point of checkin without causing a claiming error. N 16  
17 Overriding pred. pattern for non-sequential irregularity Show how the predictive pattern may be overridden for a single checkin which is not part of the sequence (e.g. a supplement; an index). Determine how the system handles non-sequential irregularities in predictive pattern at point of checkin without causing a claiming error. N 17  
18 Overriding predictive checkin feature indefinitely Advances in inorganic biochemistry (ACA2109) , last v. rec'd 1996; checkin pred. pattern set for every 2 years; publisher advises publ. date of next vol. is unknown. Can claiming be overridden indefinitely? Determine whether predictive checkin can be suspended indefinitely N 18  
19 Overriding claim Vol. 3, no. 2 of a title will be claimed on Ebsconet rather than via the local claiming software; indicate how a duplicate claim on the local system is prevented & how staff may record in the local system that the issue was claimed on Ebsconet. If claim is overridden, does the local system prompt operator to enter a reason? Determine how staff may block a claim for an individual issue at point of checkin & how staff records why the claim was blocked on the system N 19  
20 Titles issued together Advanced materials (Orbis FLA2257/OCLC #21104347) is issued in Chemical vapor deposition (Orbis FME7580/OCLC #34081658). Show how it would be checked in Determine how "issued withs" are checked in. Separate checkin records or just one checkin record? Y 20  
21 Subseries Orbis ACA5164 (Dialogues d'histoire ancienne) and Orbis ACA5160 (Recherches en linguistique etrangere) are 2 of a number of subseries of the main series title Orbis ABZ9454 (Annales litteraires de l'Universite de Besancon). Demonstrate how each of the 2 subseries might be checked in a. Separately from the main series, as well as on the main series b. On the main series only, but with a link to the main series from the subseries If there are different options, demonstrate them. Determine how subseries titles may be checked in N 21  
22 Format varies Some government document serials may vary in format between microfilm and paper. Separate bibliographic records are created for the different formats. a. If separate checkin records are created, how does the system indicate to the public that latest issue may be associated with either the paper title or the microfiche title? b. If a single checkin record is created, how are the separate MFHD records updated from the single checkin record? Example: Orbis AEJ8911 (paper) and Orbis FNA7679 (microfiche) Determine how checkin handles multiple formats where latest issue may vary in format; determine whether single checkin for multiple records is possible. N 22  
23 Setting staff note to appear at checkin Show how a note can be created & set to display to staff upon checkin of every issue, e.g. "Mark by year" Determine whether system can flag a note to display on every checkin N 23  
24 Setting staff note to appear at checkin for multiple locations Show how a note can be created & set to display to staff upon checkin of every issue for multiple locations Determine whether system can flag a note to display on every checkin for multiple locations N 24  
25 Setting staff notes for display at regular intervals Show how a note can be created & set to display to staff upon checkin of last or first issue of each volume (e.g. "Recall volume issues/recall previous volume issues from Reading Room for binding") . Determine whether system can flag a note to display at regular intervals. N 25  
26 Setting different staff notes for regular intervals for different locations If such a note described above can be set, show whether the instructions can differ for copies of the same issue in different locations (e.g. location 1 note displays on checkin of last issue of vol.: "Recall volume issues"; location 2 note displays on checkin of first issue: "Recall previous volume issues from Reading Room"). Determine whether a note flagged to display at regular intervals may differ by interval and text based on location. N 26  
27 Setting staff notes for specific issues Show how a note can be created & set to display to staff upon checkin of a specific issue, (e.g. "Notify J. Jones in cataloging before checking in.") ; demonstrate whether note may be edited at a later date Determine whether staff notes in checkin records can be applied to specific issues. N 27  
28 Issue specific web links URL is available for a specific issue; indicate how the issue specific link is entered Determine whether link to web is available for individual issues N 28  
29 Editing recurrent staff notes Show how a note set to display recurrently may be edited for all expected issues (e.g. delete all instances of a note; change all "Mark by number" to "Mark by year" Determine whether and how staff notes may be edited. Y 29  
30 Setting system generated staff notes for public display Show how system generated staff note may be set to display to the public, (e.g. "issue claimed 8/14/00") Determine whether system generated staff note can display in the OPAC. N?? 30  
31 Staff generated OPAC notes Show how staff may generate notes from the checkin record to display to the public (e.g. "Current issues in reading room") Determine whether system supports staff generated OPAC notes. Y 31  
32 Editable generic note database Show how generic notes may be created and stored for use in other checkin records without rekeying; indicate whether the stored notes may be edited and whether notes transferred from storage to checkin records may be custom edited for the specific checkin record location Determine whether system supports storage of generic notes for ready insertion into checkin records, and whether such notes may be edited. N 32  
33 System limitations for serial checkin notes Indicate maximum number of notes and number of characters for each note allowed in the checkin record; indicate maximum number of notes and number of characters for each note allowed to display to the public. Determine system limitations for checkin notes. Y 33  
34 Information from other modules required for checkin verification Does the following information from the bibliographic, order, item, and holdings records display in the checkin record?: location, call number, title, issn number, order number, volumes held, number of item records, staff member who created the checkin record, staff member who updated the checkin record; date of checkin, last payment record Determine whether checkin record provides sufficient information to verify issue in hand quickly and to leave an audit trail. Y 34  
35 Checkin link to order record when order record changes An order/payment record has been created for a sample issue and a checkin record is created & linked to it. Decision is to subscribe & a new order/payment record is created. When the first issue of the subscription is received, the checkin record needs to be linked to the order record for the subscription; show how the system ensures that the checkin record is linked to the new order record & prevents linkage to the closed order record for the sample. Determine whether the system promotes accurate linkage of checkin record to order/payment record N 35  
36 Package & membership orders Create a membership order/payment record and then create & link 3 separate serial title checkin records to the order/payment record; show how a new (4th) checkin title would be created & linked to the order/payment record; show how a closed title or title dropped from the package may be un-linked from the order/payment record Determine how (and whether) package order record may be linked to separate serial checkin titles when titles are known in advance; when a new title is added to the package; when a title is dropped N 36  
37 Package & membership orders: change in order/payment record The order number in the previous scenario has been changed & a new order/payment record needs to be created; show how the links to the checkin records are updated Determine whether links to multiple checkin records from order/payment record may be updated dynamically N 37  
38 Monographic series checkin Show how volumes in a monographic series are checked in; does system have special features associated with monographic series checkin? Determine whether system supports checkin for monographic series; determine whether checkin differs from checkin of serial titles Y 38  
39 Monographic series analytic links Titles in the series Monographs in population biology (FKY3208) are checked in on one record; that record is in turn linked to an order/payment record. Analytic records are created for each title in the series. Show whether your system can create an automatic link from each analytic record to the checkin and order/payment records. If the system is incapable of linking the analytics to the checkin record, show whether your system has sufficient note space to record brief title and isbn no. of the analytic in the checkin record Determine whether system can readily indicate whether analytic title was received as a standing order on an Orbis record, or as firm order; if this is the case, detailed checkin note would not be necessary, as well as the sso note on the analytic N 39  
40 Maximum receipt display Does system have a limit to the number of issues checked in that it can display in the OPAC?   NOTIS: 15 40  
41 Statistical reports Indicate whether system can generate statistical checkin reports based on the following variables: by checkin person by chronological period by receiving location by type of material (e.g. annual, periodical, print, non-print) Determine report options for checkin N 41  
42 Statistical subsets Indicate whether system can generate subsets of the reports, e.g. by single location for a determined chronological period, for a certain type of material Determine flexibility of the report options. N 42  
# Situation name Situation description Objective Orbis? # Notes
1 Automatic creation of checkin record with predictive pattern for single location From a bibliographic record for a periodical already in the database, demonstrate how or to what extent the system derives a publication pattern automatically & uses the pattern to generate predictive checkin records for a title represented by a single location. Determine whether the system can generate predictive checkin records from data in the bibliographic record without recourse to manual data entry N 1  
2 Automatic creation of checkin records with predictive pattern for multiple locations Perform scenario above for a title represented by multiple locations. Determine whether checkin records for multiple locations may be created automatically at the same time. N 2  
3 Relation of MFHD caption/pattern fields to checkin record Do the 853-855 fields for caption/pattern in MFHD (MARC Format for Holdings) need to be entered in order to create a predictive pattern in checkin records? If no, can a predictive pattern set up in a checkin record be transferred to the appropriate 8xx fields in MFHD? Can MFHD be updated automatically based on checkin data without creating a corresponding publication pattern in MFHD?   N 3  
4 Manual creation of predictive pattern for single location From information in a bibliographic record for a periodical already in the database, or from information on an item in hand, set up a predictive pattern by means of data entry with support of menus (pull up, click on, etc.) or other devices & use the pattern to generate predictive checkin records for a title represented by a single location. How many steps required? Determine whether manual creation of predictive pattern template is adequately supported by system software (no. of steps required, complexity). N 4  
5 Captions & calendar division database For scenario described in 4., staff should be able to access (e.g. via menu) and import from a caption and calendar division database using prescribed abbreviations & capitalization. a. Can the appropriate text derive automatically to the appropriate checkin fields based on the language code of the associated bibliographic record? b. If not, how is the data imported? (e.g., clicking on pull-up menu? Are keyboard alternatives to mouse clicking available?) c. Can the database be updated, and at what level? (vendor only? local systems staff? authorized staff?) Determine whether system provides caption/calendar division database; whether data can be imported automatically; means of access; how updated. N 5  
6 Manual creation of predictive pattern for multiple copies in multiple locations Based on scenario described in 4., create predictive pattern for a title represented by multiple copies in multiple locations. How many steps required? Determine whether checkin records for multiple copies in multiple locations can be generated from a single template, or whether a single predictive pattern can be applied to multiple copies in multiple locations. N 6  
7 Copying predictive pattern for a different checkin record title Demonstrate how a predictive pattern set up for one periodical title may be copied or derived in order to set up the predictive pattern and checkin records for a different title (e.g. for a title change) in the local database Determine whether a predictive pattern for one checkin record may be easily derived for use as a checkin record for a different periodical title. N 7  
8 Loading vendor supplied checkin data electronically Can a database of vendor supplied predictive checkin records be loaded & matched to our currently held titles in our local database? Determine whether predictive pattern can be derived from other sources with automated matching N 8  
9 Deriving checkin titles with predictive patterns from a vendor supplied database If an automatic match is not possible, can vendor provide access to a database of checkin titles already set up with predictive patterns which staff could readily import into the local database? Determine whether staff can derive predictive pattern from other sources provided by the vendor. N 9  
10 Predictive pattern template database Show whether system maintains a menu or database of both common & unusual patterns that may be used to create the predictive pattern of a checkin record; indicate whether the database/menu may be updated or edited, & whether the update is at system or workstation level Determine system support for manual creation of predictive pattern checkin records with editable resource file of predictive patterns N 10  
11 Suspension of predictive checkin (indefinite) Library receives the initial reels of a newspaper on microfilm, with a standing order for the title; show how the checkin record can be set up so the title does not have to be checked in issue by issue Determine how predictive pattern may be suspended indefinitely when format does not allow title to be checked in by issue N 11  
12 Checkin without setting up a predictive pattern Sample issue for vol. 2, no. 2 2000 is received; at this time there are no plans to subscribe. Does a predictive pattern need to be set up in order to receive the issue? Can issues be checked in without first creating a predictive pattern? If no, what alternatives do the staff have? Y 12  
13 Complex predictive patterns A : extra issue Show how predictive pattern is set up for Chemtracts (Orbis FKX4393): 310: Monthly, with an extra issue in June and Dec.   N 13  
14 Complex predictive pattern B: change in enumeration/frequency Show how predictive pattern is updated when a change in enumeration and/or frequency without a title change occurs. Also: can the obsolete predictive pattern be retained for use with back issues? a. Orbis FLD1892. Art issues. Change in frequency upon receipt of issue of Sept./Oct. 1993 (new predictive pattern is also somewhat complex) b. Orbis ACB2609. Arte medievale. Change in enumeration upon receipt of 2. ser, anno 1, nn. 1 e 2 (1987) Determine whether changes in frequency and/or enumeration are easy to update in predictive checkin; whether obsolete pattern is kept. N 14  
15 Complex predictive pattern C: cumulations Library receives regular updates of an index; the publisher sends an annual cumulative index, at which point the updates are discarded. Show how the checkin record would be set up a. Orbis AEL5301. New York Times index. (Semimonthly with annual cumulation) b. Orbis ADJ7650 Reader's guide to periodical literature (Semimonthly with annual cumulation) Determine how cumulations are handled by the system N 15  
16 Complex predictive pattern D: monographic series Geoscience and man (FFR8805) is a series standing order. Show how (or whether) a predictive pattern is set up for a series standing order, which in this case is analyzed Determine how predictive pattern is applied to monographic series N 16  
17 Complex predictive pattern E: loose-leafs Current protocols in protein science (FKM1619) is a loose-leaf publication kept up to date with quarterly supplements; show how predictive pattern is set up Determine how predictive pattern is applied to loose-leafs N 17  
18 Complex predictive pattern F: electronic journal Demonstrate how the predictive pattern for an electronic journal updated quarterly would be set up Determine how predictive pattern is applied to electronic journals N 18  
19 Complex predictive pattern F: New multipart monograph Demonstrate how the predictive pattern for a 10 v. multipart monograph would be set up from v. 1, a. Where the publisher announces that a new vol. will be published each year b. Where the publisher provides no information about when to expect forthcoming volumes Determine how predictive pattern is applied to multipart monographs N 19  
20 Complex predictive pattern G: Multipart monograph (editing predictive pattern) For the 18b. scenario above, staff notice that the publisher has been issuing a new vol. every other year. Show how the predictive pattern may be updated. Determine how the predictive pattern for a multipart may be updated from irregular to regular. N 20  
21 Automatic claiming date derived from predictive pattern Indicate whether a claiming date for each expected issue is set automatically as part of the creation of the predictive checkin pattern Determine whether system provides automatic claiming date N 21  
22 Editing claiming date If claiming date is set automatically, indicate if it is capable of being edited (for an individual issue; for all subsequent issues) Determine whether automatic claiming date may be edited Y 22  
23 Manual setting of claiming date Indicate whether a claiming date may be set manually if it is not provided automatically Determine whether checkin record allows manual set of claiming date Y 23  

Last Updated on 1/18/01
By steven arakawa
Email: steven.arakawa@yale.edu