Aleph 20 Syslib Guide - Items
Aleph 20 Syslib Guide - Items
Guide - Items
Version 20
CONFIDENTIAL INFORMATION
The information herein is the property of Ex Libris Ltd. or its affiliates and any misuse or abuse will
result in economic loss. DO NOT COPY UNLESS YOU HAVE BEEN GIVEN SPECIFIC WRITTEN
AUTHORIZATION FROM EX LIBRIS LTD.
This document is provided for limited and restricted purposes in accordance with a binding contract
with Ex Libris Ltd. or an affiliate. The information herein includes trade secrets and is confidential.
DISCLAIMER
The information in this document will be subject to periodic change and updating. Please confirm that
you have the most current documentation. There are no warranties of any kind, express or implied,
provided in this documentation, other than those expressly agreed upon in the applicable Ex Libris
contract. This information is provided AS IS. Unless otherwise agreed, Ex Libris shall not be liable for
any damages for use of this document, including, without limitation, consequential, punitive, indirect or
direct damages.
Any references in this document to third‐party material (including third‐party Web sites) are provided
for convenience only and do not in any manner serve as an endorsement of that third‐party material or
those Web sites. The third‐party materials are not part of the materials for this Ex Libris product and Ex
Libris has no liability for such materials.
TRADEMARKS
ʺEx Libris,ʺ the Ex Libris bridge , Primo, Aleph, Alephino, Voyager, SFX, MetaLib, Verde, DigiTool,
Preservation, URM, Voyager, ENCompass, Endeavor eZConnect, WebVoyage, Citation Server,
LinkFinder and LinkFinder Plus, and other marks are trademarks or registered trademarks of Ex Libris
Ltd. or its affiliates.
The absence of a name or logo in this list does not constitute a waiver of any and all intellectual
property rights that Ex Libris Ltd. or its affiliates have established in any of its products, features, or
service names or logos.
Trademarks of various third‐party products, which may include the following, are referenced in this
documentation. Ex Libris does not claim any rights in these trademarks. Use of these marks does not
imply endorsement by Ex Libris of these third‐party products, or endorsement by these third parties of
Ex Libris products.
UNIX is a registered trademark in the United States and other countries, licensed exclusively through
X/Open Company Ltd.
Microsoft, the Microsoft logo, MS, MS‐DOS, Microsoft PowerPoint, Visual Basic, Visual C++, Win32,
Microsoft Windows, the Windows logo, Microsoft Notepad, Microsoft Windows Explorer, Microsoft
Internet Explorer, and Windows NT are registered trademarks and ActiveX is a trademark of the
Microsoft Corporation in the United States and/or other countries.
Unicode and the Unicode logo are registered trademarks of Unicode, Inc.
1 LIBRARIES ..........................................................................................................5
2 COLLECTIONS ...................................................................................................5
3 COLUMN HEADINGS........................................................................................5
9.1 Print.ini.....................................................................................................16
18.1 The Special "852 Form" (Call Number Form - Type 6)..........................28
18.3 Author Number and Chronology Number: Methods and Algorithms .....34
18.3.1 Author Number by Cutter Three Figure Method ..................................................34
18.3.2 Author Number by Cutter Three Figure Without Caret Mark Method .................35
18.3.3 Author Number by Cutter Sanborn Method..........................................................35
18.3.4 Author Number by Lee Jai Chul Method..............................................................35
18.3.5 Author Number by Elrod ......................................................................................35
18.3.6 Author Number by Jang Il Sei...............................................................................37
18.3.7 Chronology Number Algorithm ............................................................................38
1. Define the ADM libraries related to the BIB library in the library_relation
table of the $alephe_root/tab directory.
2 Collections
In order to define Collections, edit tab40 using UTIL G/4/40 in an ADM library.
Following is a sample from the table:
! 1 2 3 4
!!!!!-!!!!!-!-!!!!!!!!!!!!!!!!!!!!!!!>
3 Column Headings
pc_tab_col.lng defines the columns of information that are displayed in list
windows in the GUI clients.
In order to define column headings, edit the bibliographic library (USM01) table
pc_tab_col.lng using UTIL I/9 or the ALEPHADM module.
The following is a list of the Items panes which use pc_tab_col.lng for formatting
data and their identifiers (Column 1 in pc_tab_col.lng).
4 Drop-down Menus
You may add or delete choices for some of the menus of the Item Form by editing the
following ADM library tables:
1. pc_tab_exp_field_extended.lng using UTIL L/1.
pc_tab_exp_field_extended.lng
GUI Fields
entries
INVENTORY-NUMBER Inventory Number
ITEM-LOCATION Call Number
ITEM-LOCATION-2 2nd Call Number
pc_tab_exp_field.lng
The drop-down menus defined here are for Item Call No. Type, Item Process Status,
Item List Sort Type, Item Gap Indicator, and Item Statistic, etc.
ALEPHADM Tables
1. Edit tab100 in your Administrative library. In that table, the relevant line is:
X852-ITEM-OVERRIDE=Y
If you want the Holdings Record to control the location information, enter Y in
column 2 as shown above. If you do not want the Holdings Record control, enter
N, instead.
2. Edit library_relation. Make sure that a line similar to the following line
appears in that table:
HOL USM50 USM60
You should replace "USM50" with the name of your ADMinstrative library. and
"USM60" with the name of your HOLdings library.
[ExpandField]
ItemLocation1Field=4
ItemLocation2Field=3
SerialLocation1Field=4
SerialLocation2Field=3
Use "ItemLocation..." for the Items function and "SerialLocation..." for the Serials
function. You may enter 1, 2, 3, 4, 5, 6 or 7 to the right side of the equal (=) sign. The
meaning of each value is listed below:
• 1 - a drop-down menu will be available whose choices you must define
in pc_tab_exp_field_extended.lng (UTIL L/1 in an Administrative
library) under the IDs ITEM-LOCATION and ITEM-LOCATION-2.
The choices may include counters that have been defined using UTIL
G/2.
• 2 - the user must type a call number in the field, or activate a counter
by typing ? and the code of the counter that is defined in UTIL G/2.
This option 4 and the Z311 record have additional functionality for automatic
assignment of sequential call numbers. This is dependent on assigning call
number type "i" when creating an item record. The Z311 is used to register the
last sequence number assigned for a sublibrary+prefix, so that the next highest
number can automatically be assigned when an item record is created. Prefixes
do not have to be set up beforehand; when a new sublibrary+prefix
combination i is detected, a new Oracle record is created.
So, if the call number type is set to "i" and if the user enters a prefix code
followed by "?" (for example, ABD ?) in the call number field, the system
assigns the next number in sequence. The sequence is set according to
sublibrary+prefix. (NOTE: a suffix may be added, but it is not taken into
account when assigning a sequence number).
0 - location
1 - inventory-number
o Column 3: Program name
• 5 - the user may define the call number by filling in a form that has
standard 852 subfields. The form also includes a Browse button to
select a call number from a Browse List of Call Numbers. The user can
copy a line from the Browse list and the information will be copied
into the form, in the proper subfields.
• 6 - the user may define the call number by filling in a special 852 form.
This form includes the option to calculate Author number and
Chronology Number based on various methods. For example, for Latin
material, Cutter Sanborn and Cutter Three Figure methods and for
Korean material (Hangul and Hanja), Lee Jai Chul, Jang Il Sei, and
Elrod methods. The form also includes a Browse button to select a call
number from the Browse List of Call Numbers. The user can copy a
line from the Browse list and the information is copied into the form in
the proper subfields. For more details, see the Item Call Number-
Author Number and Chronology Number section of the Aleph 20.01
System librarian's Guide – Items.
• 7 - the user may define the call number by filling in a special 852 form.
This form includes the option to calculate Author number based on
various methods. For example, for Latin material, Cutter Sanborn and
Cutter Three Figure methods and for Korean material (Hangul and
Hanja), Lee Jai Chul, Elrod, and Jang Il Sei methods. The form also
includes a Browse button to select a call number from the Browse List
of Call Numbers. The user can copy a line from the Browse list and the
information is copied into the form in the proper subfields. For more
details, see the Item Call Number- Author Number and
Chronology Number section of the Aleph 20 System Librarian's
Guide – Items.
When the librarian uses the Build Call No. Field form to enter the GR (format) and
the USIG (prefix/suffix), the system checks the counters in UTIL G/2 to determine
which counter should be used for assigning the NR (number). The system first
searches for a counter that is Sublibrary+GR. If one is not available, the system will
then search for a counter that is defined for the Sublibrary. If that is not found, the
system will search for a counter defined for the GR (format) only.
The rules for combining the three components (NR/USIG/GR) for display in the
location field are defined in tab_acc_location (in the tab directory of an
Administrative library). This table also defines the delimiters that should be used
when displaying the three components. However, in case the librarian does not
provide information about the GR (format) or USIG (prefix/suffix), the system will
not display irrelevant delimiters. Unnecessary delimiters that may not be displayed
are:
• hyphen -
• slash /
• bracket ()
• period .
tab_item_history.lng list the actions and items fields that create an Item History log
record. The following is a list of possible values that can be set in column 1 of
tab_item_history.lng:
• ITEM-LOCATION
• ITEM-CALL-NO-2
• ITEM-COLLECTION
Use "ALL-FIELDS" in order to register a change in any other field. When using
ALL-FIELDS, list it last in tab_item_history.lng.
If ALL-FIELDS is listed before the specific field, changing a listed field will register
both "ALL-FIELD" and the specific field.
Use "ALL-NON-CIRC" in order to register all changes except item (Z30) changes
caused as a result of the following item circulation activities:
z30-date-last-return
z30-hour-last-return
z30-ip-last-return,
z30-no-loans
z30-maintenance-count
The item information history fields are set in HTML display which is defined in the
server file: ./xxx50/pc_display_lng/item-history-expand.
The Change Info tab can include item information "before and after" the change (to
do this; refer to the sample demo file ./usm50/pc_display_lng/item-history-expand).
NOTES:
1) The "Change Details" section includes ALL changed field. This means that each
updated field will be reported, regardless of whether it triggers an item history record
or not.
The sort order options available to the librarian are displayed in a drop-down list in
the panes displaying: Item List, Check-In List and Group List. The text in the drop-
down list and the link to the relevant sort option in tab_z30_sort is defined in the
following menus of the pc_tab_exp_field.lng table of the Administrative library:
ITEM-SORT-TYPE
For the Item List displayed by selecting the Item List root, or the List of Items root in
the Cataloging, Acquisitions/Serials and Circulation modules.
SERIAL-CHK-SORT-TYPE
For items displayed in the Check-In List in the Acquisitions/Serials module.
SERIAL-GRP-SORT-TYPE
For items displayed in the Group List in the Acquisitions/Serials module.
SERIAL-SORT-TYPE
For the Items List of a particular subscription displayed by selecting the Items node
under the Subscription root in the Acquisitions/Serials module.
The last sort option selected by the user is saved, and serves as the default the next
time the list is displayed.
UTIL F/2/23 (of the ADM library) can be used to check item sort. This utility enables
you to view the Z30 text according to which the item is sorted.
For example: to view sorting routine 07 of ADM record 55675 sequence 30:
Enter values as defined in Col. 3 or 5 of tab_z30_sort: 07
Enter z30 key (number+seq) (Q to quit) : 000055675000030
IN -000055675000030-
<<<connect directly no listener
TYPE -ISSUE-
OUT -3 UEDUC GEN 000000001 0000011 2005-
[ADM Library]
This section determines the default ADM library of the connected library.
For example:
usm01=usm50
[CatalogItemBar]
FgColorDescript
This setting determines the color of the text displayed in the item bar.
[ItemTree]
BKColor
This setting determines the color of the Item Tab.
ItemLabel 00 N P label.prn
ItemLabelPrint 00 N P itemlbl.prn
10 Items Tables
LIBRARY TABLES
1. pc_tab_exp_field_extended.lng
pc_tab_exp_field_extended.lng defines the Item form drop-down menus
(in Items, Acquisitions/Serials and Cataloging). This table is similar to
pc_tab_exp_field.lng except that it has a column for a sublibrary (you may
use #) which allows for sensitivity to sublibraries.
2. tab_export_03
This table is used in the ADMinistrative library to set the data of the item
records for the barcode labels' output file. When constructing the
tab_export_03 table, you may combine fields. For example, in the table
below, the sublibrary, a comma, and the collection together will take up only
11 spaces in the export file and will be cut off if too long so that the
title/author will always start at position 34 of the output file.
!1 2 3 4
5
!!-!!!!!!!!!!!!!!!!!!-!!!!!!!!!!-!!!!!!!!!!!!!!!!!!-!!!!!!!!!!
20 Z30-BARCODE
The above table construction will produce an output file (in table format) like
this:
3. tab100
tab100 is the central configuration table for system-level, server-level and
library-level variables. See Items-related Entries in tab100 on page 19 and the
tab100 table header.
4. tab15.lng
Defines the item statuses and various parameters connected to these statuses.
5. tab25.lng
This table defines the list of possible values for Z30-MATERIAL (item
material type). The list must also be defined in UTIL L/2, so that it will be
available as a pull-down menu option for the registering item data.
6. tab40.lng
tab40.lng defines collection codes and names. This table defines the
expansion of the collection code as entered in the Z-30-COLLECTION FIELD
in items, to the expanded form to be displayed in the OPAC.
7. tab_filing_call_no
8. tab_item_history.lng
tab_item_history.lng defines in which cases a field change or an action
will cause an item history record to be written. In addition, the table defines
the fields displayed in the Item History screen and their description. This
information is accessible via the "History" button in the Items module.
9. tab_label.lng
tab_label.lng defines the prefixes that will be printed on the spine label.
This table can contain up to 2000 lines.
10. tab_label_parse
tab_label_parse specifies the routines used to parse (split apart) the call
number and item description when generating item labels. The definitions in
this table are used to create the raw XML data. The relevant template should
be checked to make sure it includes elements for printing this data.
11. tab_z30_sort
tab_z30_sort defines sort options for items. Different sort routines can be
used in different parts of the system.
12. tab42
tab42 controls automatic updating of the processing status field in the item
record. Automatic updating is triggered by various actions or changes in the
Acquisitions, Serials and Items modules. List of the various triggers
(processing actions) that can affect the item process status can be found in the
tab42 header.
13. tab_checksum
tab_checksum is used for defining the checksum programs. The programs can
be used for creation, validation and correction of item barcode, patron
barcode, budget code prefix, vendor/supplier code prefix, and vendor/supplier
additional code. The relevant programs for checksum of item barcode are:
1. codabar
14. tab_events.lng
If the tab_event.lng table in the bibliographic library does not exist in the
database then the events will not be created. This is not a problem.
15. form_print_method
This table defines the print methods for XML-based printouts. The default
method is XML_XSL.
16. tab_z311
This table is used in the ADM library to define the Z311 programs used by the
system for the creation of the Z311 counters for the z30-call-no, z30-call-no-2
and z30-inventory-number fields.
ALEPHE TABLES
1. library_relation
library_relation defines the relation between libraries by library type.
2. tab_sublibrary
tab_sublibrary is used to define the drop-down menu of the sublibrary field
on the Item Information form.
BIND-USE-DESCRIPTION
This variable is used to define what information ALEPH will return to external
binding preparation software packages.
Possible values are: Y or N.
Y - Return Z30-DESCRIPTION in case Z30-CALL-NO is empty.
N - Always return the Z30-CALL-NO.
N - Item retrieval by call number is disabled (i.e. there is an attempt to retrieve the
item by barcode; if it fails, no further attempt is made to retrieve by call number).
The digit to the right of each line refers to the three options listed above.
The ItemStatisticDelimiter determines the delimiter that separates the parts of the
special form (option 3).
13 Print Templates
13.1 Available Templates
The names of the Items template files are listed below (where nn is a number
identifying the version).
Note: When nn is in the range 00 - 19, inside labels will be produced. When nn is in
the range 20 - 99, spine labels will be produced.
Items Templates
print.ini
Template Purpose
function name
Copy Label Generated from the Cataloging GUI: Items
item-copy- tab/Items List pane, Label button or from ItemLabel
label-nn the service b-item-03
Copy Label
Generated from the Cataloging GUI: Items
item-copy-
Menu: Print Item Labels ItemLabelPrint
label-nn
Issue Label Generated from the Cataloging GUI/Items
ItemLabel
item-issue- tab:Items List pane, Label button or from
Note that libraries can share the same forms by adding a definition to the path_convert
table under the library's tab directory. Your ADM library is probably linked to your
BIB library:
$usm50_dev/usm50/form_eng $usm01_dev/usm01/form_eng
Services Templates
Items Services
Service Form
Report of Missing Items (ret-item-02) missing-items-report.xsl
Shelf Reading Report (item-04) shelf-reading-report.xsl
Shelf List (item-05) shelf-list.xsl
default_lock_period
Locked item records are automatically unlocked after a period defined in this entry.
The variable is defined in seconds.
item_label_restore
This entry works together with the GUI-Circulation utility Change Item Information.
Possible values:
Y - When the user changes item information (using the Change Item Information
N - The original item information will not be restored when the item label is printed.
serial_bind_period
The maximum number of days for serial issues to arrive after the Expected Arrival
Date, after which a volume containing them will be considered complete to appear in
the Completed Volume Report.
(a) If the barcode starts with a digit, it is left-padded with zeros, e.g.
"1234" --> "000000001234".
(b) If the barcode starts with "C", "M" or "S" (see (c) below for "S" with
specific prefixes) followed by digits, zeros are added between the alpha prefix
and the digits, e.g. "M4567" --> "M00000004567".
(c) If the barcode starts with one of the following prefixes - "S96", "S97",
"S98" or "S99", zeros are added between the prefix and the remaining digits,
e.g "S981123" --> "S98000001123".
The following example shows how to perform the UEA Item Barcode (valid)
Checksum:
1 2
!!!!!!!!!!!!!!!!!!!!!!!!!!!!-
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
CSV-LOAN-ITEM-BARCODE chksm_valid_item_barcode_uea
hvd_call_no_type (site-specific)
This entry determines whether or not there will be a correction of the item's call
number type "7" when the call number contains subfield 2 with special characters.
This correction is not valid for the database but only for the call number filing
procedure (in order to take the correct line from tab_filing_call_no and build
z30_call_number_key). When hvd_call_no_type is set to Y: If the call number type
is "7" and the call number field contains subfield 2 (selected uppercase) then the call
number type will be overridden to "a" for filing purposes only. When
hvd_call_no_type is set to N: the call number type will remain "7" in any case.
The Call No. and Second Call No. fields can be opened in various modes/forms as
explained in the Call Number Field section of Aleph 20.01 System Librarian's Guide –
Items. To activate the special 852 Form that includes Author Number and Chronology
Number, set the value 6 in ItemLocation1Field and or ItemLocation2Field parameters
of the PC file 'alephcom.ini'
[ExpandField]
ItemLocation1Field=6
ItemLocation2Field=6
852 Form of type 6 allows the assigning of "Author Number" and "Chronology
Number" for Item Call Number. This is in addition to the other Call number fields:
Prefix, Call, Number, Suffix, and Source.
To activate the special 852 Form that includes Author Number (and not Chronology
Number), set the value to 7 in the ItemLocation1Field and or the ItemLocation2Field
parameters of the PC file 'alephcom.ini'
[ExpandField]
ItemLocation1Field=7
ItemLocation2Field=7
852 Form of type 7 allows the assigning of "Author Number" for Item Call Number.
This is in addition to the other Call number fields: Prefix, Call, Number, Suffix, and
Source.
The 852 Form is one of the options for recording location (call number) information
in the Item record. The six fields which make up this form are based on the MARC21
Standard for Holdings Records as follows (in brackets: tag subfield name in
MARC21): Prefix, Call Number, Author Number, Chronology Number, Suffix, and
Source.
The Special "852 Form" (Call Number Form - Type 7)
From GUI-Cataloging-Item Form, click the button next to the Item Call Number field
to display the following form:
Note that this form is the same as form type 6, except of the Chronology Number field
which is disabled.
Prefix
Call number prefix ($$k) can be manually assigned by the staff user. Users may select
the relevant value from a drop-down list which is set in the LOCATION-PREFIX
menu of ./xxx50/tab/pc_tab_exp_field_extended.lng.
Call Number
Item classification number ($$h). The Item Call Number can be automatically
assigned by the system based on BIB information or manually assigned by the staff
user. For more details, see tab_author_num.conf.
Author Number
The Call Number's Author Number part ($$i). This field is a combo-box containing
the Author Number calculation methods. The content of the combo-box list is driven
from ITEM-PART-1 menu of./xxx50/tab/pc_tab_exp_field_extended.lng.
When the 852 Special Form is opened, the Author Number field can be
automatically generated by the system or manually assigned by the staff user. This
behavior is depended on ./xxx01/tab/tab_author_num.conf (see details in
"tab_author_num.conf" section).
If the Author number value is already filled-in, the user may re-select one of the
methods. The recently calculated value overrides the current value.
Note that user may activate the button which is located to the right of the Author
Number field and override the default system behavior which is defined in
tab_author_num.conf. Clicking this button displays a list of BIB tags for calculating
Author Number and can be used if the operator decides to use an alternative tag for
calculation the Author Number field (not the tags defined in tab_author_num.conf).
The Author Number field may also be left blank. The following are the available
Author Number Methods:
• Lee Jai-Chul – Lee Jai Chul method that can be applied for Korean material
(Hangul and Hanja). The algorithm that is used to calculate the Lee Jai Chul
author number consults the setup table: in ./xxx01/tab/tab_lee_jai_chul. The
Lee Jai Chul method can have multiple entries in the Author Number combo-
box (as defined in ITEM-PART-1 menu of
./xxx50/tab/pc_tab_exp_field_extended.lng).
• Elrod – Elrod method that can be applied for Korean material. For more
details, see the Author Number by Elrod section.
• Jang Il Sei – Jang Il Sei method that can be applied for Korean material. For
more details, see Author Number by Jang Il Sei on page 37.
• Cutter Sanborn – Cutter Sanborn method that can be applied for Latin and
non-Korean material. The algorithm that is used to calculate the Cutter
Sanborn author number consults the setup table: in ./xxx01/tab/tab_cutter.
• Cutter Three-Figure – Cutter Three Figure method that can be applied for
Latin and non-Hangul/Hanja material. The algorithm that is used to calculate
Cutter Three Figure author number consults the setup table in
./xxx01/tab/tab_cutter_three. Note that if the cutter-three-figure is calculated
Chronology Number
The Call Number's Chronology Number part ($$i). This field is a combo-box
containing one option, Chronology Number. The content of the combo-box list is
driven from ITEM-PART-2 menu of./xxx50/tab/pc_tab_exp_field.lng. When the '852
Special Form' is opened, the 'Chronology Number' field can be automatically
generated by the system or manually assigned by the staff user. This behavior is
depended on ./xxx01/tab/tab_author_num.conf (see details in "tab_author_num.conf"
section). If the Chronology Number value is already filled-in, the user may select the
Chronology Number from the list; the value just calculated overrides the current
value. The Chronology Number field may also be left blank. The Chronology
Number field is cleared if one or more of the following 852 Form fields are changed,
Prefix, Call Number, and Author Number. For technical reasons related to the Call
Number sorting routine, the original year (the year value before calculating the
chronology number) are recorded in $$9 of Z30-CALL-NO/ Z30-CALL-NO-2. If
both fields Author Number and Chronology Number are filled-in, two $$i entries
are created in the Z30-CALL-NO/ Z30-CALL-NO-2. For more details, see the
section, Chronology Number Algorithm.
Suffix
Call number suffix ($$m). Can be manually assigned by the staff user. Users may
select the relevant value from a drop-down list which is set in LOCATION-SUFFIX
menu of ./xxx50/tab/pc_tab_exp_field_extended.lng.
Source
Call number source ($$2). Can be manually assigned by the staff user. Users may
select the relevant value from a drop-down list which is set in LOCATION-SOURCE
menu of ./xxx50/tab/pc_tab_exp_field_extended.lng.
NOTES:
Note 1:
When the 852 Form is opened for an item which has no value in the Call Number
field (Z30-CALL-NO or Z30-CALL-NO-2 is empty), the system fills in values as
defined in the relevant configuration settings (see tab_author_num.conf for
configuration information).
When a filled 852 Form is opened, the system displays the current values without
automatic recalculating the empty fields. If you want to update or re-calculate the
values, type or select a relevant scheme. If the prefix, call number, or author number
is changed, the chronology number is cleared.
Note 2:
Note 3:
To support the GUI drop-down list for 'Chronology Number' field, set the following
in ITEM-PART-2 menu of ./xx50/tab/ pc_tab_exp_field.lng
ITEM-PART-2 L Chronology Number CHRON
Note 4:
To support the GUI drop-down list of BIB tags which are used as an alternative tags
for Author Number calculation, set ITEM-PART-1-TAG menu of ./xxx50/tab/
pc_tab_exp_field.eng. For example:
ITEM-PART-1-TAG L 600 600
ITEM-PART-1-TAG L 610 610
ITEM-PART-1-TAG L 111 111
18.2 tab_author_num.conf
The bib library tab_author_num.conf (./xxx01/tab/tab_author_num.conf) defines the
library's policy for assigning the following Item Call Number fields of the special
852 Form: Item Cal Number, Author Number and Chronology Number.
Different policies can be set per sublibrary. This can be achieved by setting the
sublibrary code as the extension of the table file name. For example, to define
Sample of tab_author_num.conf
[CALL-NO]
LAW = 090##,a,1,056##,a,1,082##,a,2
WID = 050##,a,2,052#1,a,1,090##,a,3
##### = 050##,a,2,052#1,a,1,090##,a,9
[AUTHOR-NAME]
fields = 100,110,111,245
[LATIN-TYPE]
type = 1
[HANGUL-TYPE]
type = 8
[COMMON-KOREAN]
common_words = ae40,c774,bc15,cd5c,c815,c870,ac15,c7a5,d55c,c724
[SPECIAL-LETTER-VALUE]
special_letter = 3131
[CHRON-TYPE]
type = 1
sequence = korean
[CALL-NO] section
Define the BIB fields that are applied in order to build the Call Number ($$i of Z30-
CALL-NO / Z30-CALL-NO-2) and Call Number type (Z30-CALL-NO-TYPE/
Z30-CALL-NO-TYPE-2). For example:
WID = 050##,a,2,052#1,a,1,090##,a,9
“WID” is the item sublibrary code, BIB tag 050##$$a is a first candidate tag to
populate $$i of the item call number. If 050##$$a is used for populating the call
number, then the value "2" is set in the Call Number type. If the BIB record has no
050##$$a, the system will keep checking the next option: 052#1,a,1 and so on.
[AUTHOR-NAME] section
Define the BIB fields that are applied in order to determine whether the BIB record
is Korean (Hangul or Hanja) or Else. For example:
AUTHOR-NAME = 100,110,111,700,710,711
The system first looks for 100, then for 110, and then 111, and so on, until it finds a
matching field.
Note that user may override the BIB value defined in AUTHOR-NAME of
tab_author_num.conf by activating the button which is located at the most right side
of the Author Number field (at the "852 Form"). This button offers list of alternative
BIB tags for calculating the Author Number.
[LATIN-TYPE] section
Use for generating Author Number field for non-Korean material (e.g.: Latin). For
example:
type = 1
[HANGUL-TYPE] section
Use for generating Author Number field for Korean (Hangul and Hanja) material. For
example:
type = 4
[COMMON-KOREAN] section
Used by the system in case where the Author Number is assigned using one of the
Lee Jai Chul types.
It is used to define the commonly used Korean names. For example:
common_words = ae40,c774,bc15,cd5c,c815,c870,ac15,c7a5,d55c,c724
[SPECIAL-LETTER-VALUE] section
Used by the system in case where the Author Number is assigned using Lee Jai
Chul types 5 or 6 or 8. It is used to define the exception letter that should be
handled differently. For example:
special_letter = 3131
[CHRON-TYPE] section
Used by the system to to define policy for assigning the Chronology Number. This
section has two parameters: "sequence" and "type". For example:
type = 1
sequence = korean
The parameter type defines whether the library wishes the Chronology field to be
automatically populated when the 852 Form is opened.
Types values can be "0" or "1".
0 – Chronology Number is displayed null (it is not automatically generated by the
system). User may manually select the "Chronology Number" option from the drop-
down list or type it in.
1 – Upon opening the 852 Form, the Chronology Number field is automatically
populated based on the Chronology Number algorithm. User may override the
automatically filled value.
The sequence parameter defines according to which sequence list the chronology
number sequence part is set: Korean sequence list or Latin sequence list.
Values can be "korean" or "latin".
[LATIN-TYPE]
type = 2
[LATIN-TYPE]
type = 3
[LATIN-TYPE]
type = 1
[HANGUL-TYPE]
type = 5
type 1 thru 8 are dedicated to Lee Jai Chul various types.
[HANGUL-TYPE]
type = 9
Elrod author number consists of two parts delimitated by a single space: the Author
Number part and the Title Number part. For example, if Author number part is
XXX and Title number part is Y, the author number by Elrod is 'XXX Y'.
Author Number part of Elrod
Author Number part is up to three Korean syllables which are extracted from the
$$a of the following author heading fields in the BIB record. If an author name is
The BIB record is checked for Author heading fields as defined in AUTHOR-
NAME section of tab_author_num.conf.
For example:
AUTHOR-NAME = 100,110,111,700,710,711
The system first looks for 100 and then for 110 and then 111, and so on, until it
finds a matching field.
If the relevant author name in the BIB record is in Chinese letters, the systems
extracts three letters as an Author Number part from the AUTHOR-NAME field
and then transliterate it to Korean letters. The transliteration from Chinese to
Korean, uses the fix_doc program named “fix_doc_transliteration” with the
program argument “HANJA_TO_HANGUL”.
If the Chinese author name is XXX and its translation into Korean is YYY; the
result is YYY.
If 245 $$a main title starts with a pre-title put in parentheses, the system ignores the
pre-title with parentheses and then take the very next letter.
If 245 $$a main title is in Chinese letters, the system transliterates it to Korean
letters.
If the Chinese main title starts with X and its translation into Korean is Y, the result
is Y.
If 245 $$a main title starts with in Roman or Numeric characters, the system takes it
as it is. Staff users change it to the correct number.
Note:
Elrod algorithm uses a special entry in column 1 of tab_character_conversion_line:
CALL_NO_ELROD. The library may define in column 5 of
tab_character_conversion_line any character conversion table that should be used for
CALL_NO_ELROD.
For example: It is possible to set a special character conversion table for
CALL_NO_ELROD including the values from hanja_to_hangul and values from
kana2hangul.
The following is an example of ./alephe/unicode/tab_character_conversion_line that
defines cjk_to_hangul table for CALL_NO_ELROD:
CALL_NO_ELROD ##### # line_utf2line_utf cjk_to_hangul
The ./alephe/unicode/cjk_to_hangul table must be set to define the Unicode values to
be used by CALL_NO_ELROD routine.
18.3.6 Author Number by Jang Il Sei
The Jang Il Sei method is applied to Korean titles, regardless of MARC formats
KORMARC or MARC21 and material types Book, Serials, etc.
To set the automatic assignment of the Jang Il Sei method for Korean titles, set the
following in table ./xxx01/tab/tab_author_num.conf:
[HANGUL-TYPE]
type = a
Jang Il Sei Author Number consists of two sequential parts: the Author Number part
and the Title Number part. For example, if the Author Number part is XXX and Title
Number part is Y, the Author Number by Jang Il Sei is 'XXXY'.
Note:
The Jang Il Sei algorithm uses a special entry in column 1 of
tab_character_conversion_line: CALL_NO_JANGILSEI. The library may define in
column 5 of tab_character_conversion_line any character conversion table that should
be used for CALL_NO_JANGILSEI.
For example: It is possible to set a special character conversion table for
CALL_NO_JANGILSEI including the values from hanja_to_hangul and values
from kana2hangul.
The following is an example of ./alephe/unicode/tab_character_conversion_line that
defines cjk_to_hangul table for CALL_NO_JANGILSEI:
CALL_NO_JANGILSEI ##### # line_utf2line_utf
cjk_to_hangul
The ./alephe/unicode/cjk_to_hangul table must be set to define the Unicode values to
be used by CALL_NO_JANGILSEI routine.
• If the publication year is between 1901 and 1999, the last two numbers of the
year are assigned.
1901 Æ 01
1902 Æ 02
1970 Æ 70
1999 Æ 99
• If the publication year is 2000 or after 2000, the last three numbers of the year
are assigned.
2000 Æ 000
2001 Æ 001
2007 Æ 007
Sequence Number Part of Chronology
The numbering for the sequence part of the Chronology Number can be
differentiated depending on the library preferred sequence language counter, Latin
In case where:
sequence = latin
The sequence number should be assigned in alphabetical order basically. The first
turn is from a to z, the second turn is from za to zz, the third turn is from zza to zzz,
and then the following tune is in the same way.
In case where:
sequence = korean
The sequence number is not based on the serial number. It is assigned according to
the predefined order of Hangul syllables which consist of the Hangul consonant and
the Hangul vowel only.
가 [U+AC00]
갸 [U+AC38]
거 [U+AC70}
겨 [U+ACA8]
“omitted”
히 [U+D788]
Note that there are total of 140 Hangul syllables which are set in
./alephe/unicode/tab_hangul_syllable_seq
The first tune is based on the order of the above Hangul syllables. If the order is
reached the last Hangul syllable, that is “히”, the following sequence numbers are
expanded merely based on the serial numeric number that should be attached to the
last Hangul syllable “히”, like “히1”, “히2”, “히3” ...”히n”.
Base of counting (How to check the last number)
In order to assign new Sequence Number, the system checks the last number of it. The
base of the counting of Sequence Number is not simply the Year Number. It should
be:
“Prefix (if exists) + Classification number + other item number (if exists) + Year
Number”
Example 1:
Marc format: MARC21 (Latin)
Published year in 008/07-10: 2007
Prefix: Ref
Classification number: 330
Year Number will be generated by Chronology method: 007
Sequence Number will be generated by Chronology method:
• The base of the counting of Sequence Number is “Ref 330 007” [Prefix +
Classification number + Year Number]
The following is a sample of a call number browsing list around “Ref 330 007”:
.
Ref 330 006히
Ref 330 006히1
Ref 330 007가
Ref 330 007갸
Ref 330 007a
Ref 330 007b
Ref 330 007c
Ref 330 008a
Ref 330 008b
Example 2:
Marc format: KORMARC (Korean)
Published year in 008/07-10: 2007
Prefix: Ref
Classification number: 330
Year Number is generated by Chronology method: 007
Sequence Number is generated by Chronology method:
• The base of the counting of Sequence Number will be “Ref 330 007” [Prefix +
Classification number + Year Number]
• In order to see he last number of Sequence Number, the system should check the
call number indexes starting with the above base “Ref 330 007”.
• If the last call number which has the base of “Ref 330 007” is “Ref 330 007갸”,
the last Sequence Number is “갸”.
Followings are Call number browsing list around “Ref 330 007”:
..
Ref 330 006히
Ref 330 006히1
Ref 330 007가
Ref 330 007갸
Ref 330 007a
Ref 330 007b
Ref 330 007c
Ref 330 008a
Ref 330 008b
Therefore, new Sequence Number is “거”, based on the KORMARC way. Eventually,
the whole Chronology number will be “007거”.
• . /alephe/unicode/hanja_to_hangul_dictionary_utf8.txt
• ./alephe/unicode/hangul_to_hanja_dictionary_utf8.txt
• ./alephe/unicode/ tab_hangul_syllable_to_letters
• ./alephe/unicode/tab_hangul_syllable_seq
19 Barcode Checksum Routines for Keio
Special for Keio (Japan) - checksum algorithms can be applied for patron and item
barcode validation.
The checksums can be implemented using ./xxx50/tab/tab_checksum.
The Keio checksum routines to be set in the 2nd column of tab_checksum are:
• checksum_valid_item_bar_keio - Item validation algorithm
Note: When setting up the table with above algorithms, make sure there are no item
barcode creation routines defined in col.1 (routines that starts with CSCR-), such
routines lead to a conflict with the new Keio-item validation check.
For example:
For 1040230001
1 x 10 = 10
0x 9= 0
4 x 8 = 32
0x 7= 0
2 x 6 = 12
3 x 5 = 15
0x 4= 0
0x 3= 0
0x 2= 0
1x 1= 1
------------
Sum 70
70 / 11 = 6 remainder 4
10 - 4 = 6 (10 is 0)
Check Digit = 6 (10402300016)
Action item 2
1. Multiply each digit starting from the left by 1-2-1-2-1-2-1-2-1-2.
When the sum is a 2-digit number, divide it into each digit, and add all the sums.
2. Divide the sum from step 1 by 10 and calculate the remainder.
3. Subtract the remainder from step 2 from 10. This sum is the check digit.
(However, if the sum is 10, check digit is 0.)
For example:
For 1010050001
1 x 1 = 1 -> 1
0 x 2 = 0 -> 0
1 x 1 = 1 -> 1
0 x 2 = 0 -> 0
0 x 1 = 0 -> 0
5 x 2 = 10 -> 1 + 0 = 1
0 x 1 = 0 -> 0
0 x 2 = 0 -> 0
0 x 1 = 0 -> 0
1 x 2 = 2 -> 2
-------------------------
Sum 5
5 / 10 = 0 remainder 5
10 - 5 = 5 (10 is 0)
Check Digit = 5 (10100500015)
If the barcode does not match the result of the checksum algorithm, the following
error message is displayed: “incorrect barcode”.
Action item 3
1. Multiply each digit starting from the left by 11-10-9-8-7-6-5-4-3-2, and add all the
sums.
2. Divide the sum from step 1 by 11 and calculate the remainder.
3. Subtract the remainder from step 2 from 11. This sum is the check digit.
(However, if the sum is 10 or 11, check digit is 0.)
For example:
For 8010000007
8 x 11 = 88
0 x 10 = 0
1x 9= 9
0x 8= 0
0x 7= 0
0x 6= 0
0x 5= 0
0x 4= 0
If the barcode does not match the result of the checksum algorithm, the following
error message is displayed: “incorrect barcode”.
Action item 4
The barcode should match one of the following four conditions:
1. Multiply each digit starting from the left by 10-9-8-7-6-5-4-3-2, and add all the
sums.
2. Divide the sum from step 1 by 11 and calculate the remainder.
3. Subtract the remainder from step 2 from 11. This sum is the check digit.
(However, if the sum is 11, the check digit is 0, and if the sum is 10, check digit is
"X").
For example:
123456789
1 x 10 = 10
2 x 9 = 18
3 x 8 = 24
4 x 7 = 28
5 x 6 = 30
6 x 5 = 30
7 x 4 = 28
8 x 3 = 24
9 x 2 = 18
------------
Sum 210
210/ 11 = 19 remainder 1
11 - 1 = 10 (10 is X)
Check Digit = X (123456789X)
If the barcode does not match the result, perform the next check:
1. Multiply each digit starting from the left by 9-8-7-6-5-4-3-2-1, and add all the
sums.
2. Divide the sum from step 1 by 11 and calculate the remainder.
3. Subtract the remainder from step 2 from 11. This sum is the check digit.
(However, if the sum is 11 or 10 or 0, check digit is 0.)
For example:
For 123456789
If the barcode does not match the result, perform the next check:
1. Multiply each digit starting from the left by 10-9-8-7-6-5-4-3-2, and add all the
sums.
2. Divide the sum from step 1 by 11 and calculate the remainder.
3. Subtract the remainder from step 2 from 11. This sum is the check digit.
(However, if the sum is 11 or 10 or 0, check digit is 0.)
For example:
For 123456789
1 x 10 = 10
2 x 9 = 18
3 x 8 = 24
4 x 7 = 28
5 x 6 = 30
6 x 5 = 30
7 x 4 = 28
8 x 3 = 24
9 x 2 = 18
------------
Sum 210
210/ 11 = 19 remainder 1
11 - 1 = 10 (10 is 0)
Check Digit = 0 (1234567890)
If the barcode does not match the result, perform the next check:
1. Multiply each digit starting from the left by 9-8-7-6-5-4-3-2-1, and add all the
sums.
2. Divide the sum from step 1 by 11 and calculate the remainder.
3. Subtract the remainder from step 2 from 11. This sum is the check digit.
(However, if the sum is 11 or 10 or 1 or 0, check digit is 0.).
For example:
For 123456789
If the barcode does not match the result of the checksum algorithm, the following
error message is displayed: “incorrect barcode”.
Action item 5
1. Divide the 8-digit number into each digit and add them all to get the sum.
2. Divide the sum from step 1 by 10 and calculate the remainder.
3. Subtract the remainder from step 2 from 10. This sum is the check digit.
(However, if the sum is 10, check digit is 0.).
For example:
For 12345678
1
2
3
4
5
6
7
8
------------
Sum 36
36/ 10 = 3 remainder 6
10 - 6 = 4
Check Digit = 4 (123456784)
If the barcode does not match the result of the checksum algorithm, the following
error message is displayed: “incorrect barcode”.
19.2 Patron Barcode Algorithm - checksum_valid_bor_id_keio
The following chart describes the algorithm, checksum_valid_bor_id_keio, used for
checking patron system numbers.
.
As in all other patron barcode check routines, the patron checksum is applied to all
patron keys (Z308-KEY-TYPE) except of the patron ID (Z308-KEY-TYPE=00).
Action patron 1
The barcode should pass one of the following checks:
1. Multiply each digit starting from the left by 9-8-7-6-5-4-3, and add all the sums.
2. Divide the sum of step 1 by 11 and calculate the remainder.
This remainder is the check digit.
(However, if the remainder is 10, the check digit is 0.)
For example:
For 1234567
1x 9= 9
2 x 8 = 16
3 x 7 = 21
4 x 6 = 24
5 x 5 = 25
6 x 4 = 24
7 x 3 = 21
------------
Sum 140
140/ 11 = 12 remainder 8
Check Digit = 8 (12345678)
If the barcode does not match the result, perform the following check:
1. Multiply each digit starting from the left by 9-8-7-6-5-4-3, and add together all the
results.
2. Divide the result of step 1 by 11 and calculate the remainder.
3. Subtract the remainder derived in step 2 from 11. The result is the check digit.
(However, if the result is 11, the check digit is 0. If the result is 10, the check digit
is "X".)
If the barcode does not match the result, perform the following check:
For example:
For 1234567
1
2
3
4
5
6
7
------------
Sum 28
ones place digit = 8
10 - 8 = 2
Check Digit = 2 (123456782)
If the barcode does not match the result of the checksum algorithm, the following
error message is displayed: “incorrect barcode”.