v.16 Upgrade Express Serials Doron Greenshpan

v.16 Serials 2 Session Agenda Serials workflow demo Publication Schedule goes Prediction modes New and improved pattern subfields Linking subscription and pattern Linking pattern pairs Claims Services Summary holdings setup

v.16 Serials 3 Serials Workflow Demo Agenda Cataloging Subscription creation Pattern-making In the Cataloging module In the Serials module With the old schedule form Opening expected items Check-in Claiming Routing

v.16 Serials 4 Publication Schedule The Publication Schedule is gone. The Z17 (Issue) table has been removed. The table is no longer functional, and the “MULTI- 85X” switch in tab100 has become obsolete. Z17 was used for Opening the next issue Merging issues Deleting issues Adding issues

v.16 Serials 5 Publication Schedule Functions that were available on the Publication Schedule are now available under the Group node. In v.16, when the Open Items option is used, the system opens a full cycle; there isn’t an option for opening the “next issue” only. Therefore, part of the upgrade process is opening all cycles to the end.

v.16 Serials 6 Prediction Two modes of prediction are supported: 853/4/5 Pattern fields (Older) Schedule form (Z12) A single BIB record can have its prediction defined in either the ADM record, or in the HOL record, but not in both.

v.16 Serials 7 New Features in Pattern Fields 853/4/5 - Subfield $$t used to add a caption, and the subscription sequence, to the item description and summary holdings statement Multiple occurrences of subfield $$y are now allowed. 853X/4X/5X field - Subfield $$o Specifies the item’s material type, for example: ISSBD for an item already bound; if $$o is not defined, the default value is ISSUE.

v.16 Serials 8 Linking Subscription and Pattern ($9) New fix for adding subfield $9 (with value of “1”) to the 853 field, linking it to a subscription. (INS fix_doc_add_sf9 in tab_fix in the HOL library). The linking of a pattern to a subscription is needed for the opening of items. The subfield will be added by the fixonly when a single subscription, linked to the HOL record, exists.

v.16 Serials 9 Linking Pattern Pairs ($8) When more than one pair of 853/853X exists in the same HOL record, subfield $8 is required to link each pair. Subfield $8 with the same value needs to be added to both 853 and 853X of the same pair. Example: First pair:853 $81… 853X$81… Second pair:853 $82… 853X$82… If only one pair exists, there’s no need to add $8. If patterns are created with the forms in the Acq/Serials module, subfield $8 is added automatically to 853/853X.

v.16 Serials 10 Serial Claims 3 options for claiming were added to the Subscription Information 2 nd tab: Send claims Yes – automatic via the serials-44 service. No – no automatic claiming. Irregular – as in ‘No’, but expected items will be shown in the claim report (serial-04).

v.16 Serials 11 New/Improved Services New: Test Pattern Opening (serial-12) This service checks serial patterns, and tries to open the next cycle based on the level-X (853X) fields. Improved: Import 85X Records (serial-52) Prediction fields exported from ADM records can be loaded to either ADM or HOL records by choosing the relevant load type.

v.16 Serials 12 New/Improved Services New: Merge and Deduplicate Serial Pattern Files (serial-53) Merges serial pattern files (up to 10 files) and de-duplicates identical records.

v.16 Serials 13 Deleted Services Open Publication Schedule (serial-10) Delete Publication Schedule (serial-20) Open Expected Issues (serial-11) The functionality of this service is now performed by Open Expected Issues (serial-13)

v.16 Serials 14 Summary Holdings Summary Holdings statements are 866/7/8 fields which are generated from paired 853/4/5 and 863/4/5 fields in the Holdings record by using expand or fix procedures. As an expand routine, the 863s are built on the fly when the record is displayed, and as a fix, they are actually added to the HOL record. The 866 is always added virtually as an expand.

v.16 Serials 15 Summary Holdings Statement Example If the following exists in the HOL record: L $$81$$av.$$bno.$$u9$$vr$$i(year)$$j(month)$$wm L $$81.1$$a1-4$$i L $$81.2$$a6-86$$i Then these holdings statements will be created: L $$av.1(1991)-v.4(1993)$$ L $$av.6(1995)-v.86(1997)$$81

v.16 Serials 16 Prerequisites Prediction pattern fields (853/4/5) should reside in the HOL record. The subscription (and items) are linked to the HOL record. (i.e. Hol. No. field in both subscription and item records has HOL record number.)

v.16 Serials 17 Setup fields are created by expand_doc_hld_stmt (for virtual display) or fix_doc_hld_stmt (for actual creation) in the HOL library’s tab_expand and tab_fix respectively fields are created by expand_doc_hol_86x in tab_expand of the HOL library. If relevant, add the fix to fix_doc.lng in HOL library for it to be available in the Cat module’s list of fixes. Setup tab_hld_stmt in the ADM library.

v.16 Serials 18 Why Use Fields 863/4/5? Fields 863/4/5 contain a description of the holdings of a bibliographic item, based on items in the system. They are needed as an intermediate stage between items (Z30) and the holdings summary statement.

v.16 Serials 19 Setup of tab_expand For items not linked to a subscription, or linked to it, but having no data in the Copy Number field, the parameter GET_Z30_BY=HOL should be defined in col. 3 of tab_expand: ! !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!> WEB-FULL expand_doc_hld_stmt GET_Z30_BY=HOL For items linked to a subscription, you may choose the Copy-ID field to group items together. Note: this is also the default, should no parameter be defined in col. 3.

v.16 Serials 20 Setup of tab_expand Note: The routines generating summary holdings statements should be listed in tab_expand in the following order: ! !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!> WEB-FULL expand_doc_hld_stmt WEB-FULL expand_doc_hol_86x For adding the 866/7/8 For adding the 863/4/5

v.16 Serials 21 Setup of tab_fix The following line should be added to tab_fix of the HOL library in order to create the 866 fields: HSTMT fix_doc_hld_stmt

v.16 Serials 22 Setup of tab_fix For items not linked to a subscription, or linked to it, but having no data in the Copy Number field, the parameter GET_Z30_BY=HOL should be defined in col. 3 of tab_fix: ! !!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!> HSTMT fix_doc_hld_stmt GET_Z30_BY=HOL For items linked to a subscription, you may choose the Copy-ID field to group items together. Note: this is also the default, should no parameter be defined in col. 3.

v.16 Serials 23 Setup of fix_doc.lng In order for the fix option to be available in the Cataloging module’s list of fixes, the following line should be added to fix_doc.lng: ! !!!!!-!-!-!!!!!!!!!!!!!!!!!!!!!!!!! HSTMT N L Create Summary Holdings* * Free text in col. 4.

v.16 Serials 24 Which Item Records Are Included in the Statement Items with an item process status which is different than NA (not arrived) or NP (not published). The latter will, however, create a gap indicator in the statement. Items that have a HOL No. in the HOL Link field (i.e. linked to a HOL record). All items which share the same Linking Number identifier in subfield $8, and the same Copy-ID. Items for which the enumeration field is equal to or greater than the value entered in subfield $$a of S63/4/5 (Starting Point field) – if that field exists.

v.16 Serials 25 tab_hld_stmt Resides in the ADM library. For mapping items into either an NA or NP process status, based on one or more of the following filters: Sublibrary Collection Item status Item process status Break indicator

v.16 Serials 26 tab_hld_stmt Example, a library that wants to exclude missing items from the holdings statement should map the process status MI (missing) as NA in tab_hld_stmt, as follows: ! !!!!!-!!!!!-!!-!!-!-!! ##### ##### ## MI # NA ##### ##### ## ## g NA ##### ##### ## ## n NP Col. 1: sublibrary Col. 2: collection Col. 3: item status Col. 4: item process status Col. 5: break indicator Col. 6: item process status to be mapped into.

v.16 Serials 27 The S63/4/5 Fields These fields should be added by libraries that already have holdings statement fields for item records, and wish to create a new statement from a certain point onwards. They define from which Starting Point (volume number) and for which Copy ID a holdings statement should be generated. S63/4/5 subfield $$a is the volume number's Starting Point, and subfield $$t is for the Copy ID.

v.16 Serials 28 The S63/4/5 Fields For example, if field S63 contains the value "3" in subfield $a, then only items with the first enumeration level of "3" (or higher) will be included in the holdings statement. If field "S63" contains the value "2" in subfield $t, then only items with the value "2" in the copy number field (Z30-COPY- ID) will be included in the holdings statement. Example : S63 L $$a3 $$t L $$81.1$$a3$$b2-4$$i2002$$j03-07$$wg$$t2$$9Y L $$81.2$$a4$$b1-2$$i2003$$j01-03$$wg$$t2$$9Y L $$81.3$$a4$$b4-5$$i2003$$j07-09$$wg$$t2$$9Y

v.16 Serials 29 The S63/4/5 Fields It is possible to have several S63 fields in the HOL record. In this case, a set of holdings statement (863/4/5) fields will be created for each S63 field that includes subfield $t (copy-ID) L $$81.13$$a1$$i $$t1$$9Y L $$81.14$$a2$$b1-3$$i2001$$j01-05$$wg$$t1$$9Y L $$81.15$$a2$$b5-6$$i2001$$j09-11$$t1$$9Y L $$82.13$$a1$$i2000$$t2$$ $$9Y L $$82.14$$a2$$b1$$i2001$$j01$$wg$$t2$$9Y L $$82.15$$a2$$b3$$i2001$$j05$$wg$$t2$$9Y

v.16 Serials 30 More on 863/4/5 Subfields Subfield $$9Y: Denotes that the holdings statement field should be regenerated each time the expand or fix procedures are used. Subfield $$9N: Denotes that the holdings statement field should be retained each time the expand or fix procedures are used. Subfield $$w: Value "g" indicates a gap break (for issues that did not arrive). Value "n" indicates a non-gap break (for issues that were not published).

v.16 Serials 31 Linking 863 and 866 If the 866/7/8 field has the same sequence number in subfield $8 as that registered in subfield $8 of the 863/4/5 field, then no other 866/7/8 field will be generated by the program. If the 866/7/8 field has “ 0 ” in subfield $8, then no other 866/7/8 field will be generated by the program.