Field display in local OPAC (order of fields, and field labels): No need to coordinate with Alliance.

Search Menu options: Be sure that the option to Search Alliance union catalog is available from the Main Menu, and the pass-through search option is offered from all appropriate browse and individual record display screens.

Indexing: Not essential to coordinate with Alliance; local data is re-mapped and re-indexed when it arrives at central.

Branch and location codes (Branch codes in bibliographic records; loc codes in bib., item, order and checkin records.) Usually there is no need to notify Alliance. The central system does not use local location codes in determining circulation eligibility or due dates. It uses the local site's location codes only to display the label, or name of the location, in detailed holdings information for the institution, getting the label text from the table at the local site. Be aware that central re-reads local systems' branch code tables once a day (midnight or after). Changes in the local table will not take effect in central until the following day. Records added using a new code, for example, or a code where the label (branch name) was changed, will not display the correct location information.

Important exceptions: 1. Sites using software to distinguish between separate agencies sharing an INNOPAC need to contact central to coordinate communication with III to assign the new branch to one of the site codes. 2. Changes to codes used for Pickup and Pickup Anywhere locations must be coordinated with Alliance in advance.

Variable-length fields: If you are considering defining a new variable-length field (MARC or non-MARC), indicator, or subfield code not covered by standard MARC format, contact Alliance first to review feasibility and coordinate appropriate simultaneous or sequential changes to the local and central systems. A few examples of the dozens of variable-length fields: author, title, subject, and notes in bib. records; volume in item records.

BCode1 (Bib Lvl) Central looks for code <s> in BCode1 to identify serials – used in Scoping (pre-limiting a search to serial records, also called “Journal Scoping”).

o Local sites that use BCode1 for anything other than Bib Lvl should contact central.

o To use <s> for some meaning other than to identify a serial, or to use some other code or fixed field to identify a serial, contact central to initiate or update BCode mapping. Example of BCode mapping table

 

National standard for Bib Lvl ( US MARC and OCLC):

a - Monographic component part	US MARC Leader Byte 7, OCLC 006
b - Serial component part	US MARC Leader Byte 7, OCLC 006
c - Collection	US MARC Leader Byte 7, OCLC 006
d - Subunit	US MARC Leader Byte 7, OCLC 006
i - Integrating resource	US MARC Leader Byte 7
m - Monograph/item	US MARC Leader Byte 7, OCLC 006
s - Serial	US MARC Leader Byte 7, OCLC 006

 

BCode2 (Mat Typ) The local and union database codes must be consistent. The local label doesn't have to match the union catalog as long as the use is the same, and no need to contact Alliance if you modify only the label. For example: USMARC format defines code "g" as "Projected medium"; the central label is VIDEO/FILMS, but the local label could be FILMS ETC., A-V, etc. Contact Alliance for any other variances (different use of code values, additional codes, etc.); a mapping table can be implemented for remapping local codes to appropriate codes at central. More information about BCode2 and mapping tables.

BCode3 (Contribution, Suppression, and other uses) If you have a BCode3 local-central mapping table: Contact Alliance to coordinate additions and changes. If you do not have a mapping table: Keep in mind that codes recognized by INN-Reach software (g,l,n,o,s,z) must be used consistent with the Alliance use and definition. More info about BCode3. Note: Prior to Release 12: no mapping table to translate codes from local to central values. Many members were profiled and loaded to Summit without a mapping table. Codes recognized by INN-Reach software (g,l,n,o,s,z) must be used consistent with the central use and definition. Other codes will have no resulting "action" in the union catalog, so do not need to be coordinated with Summit.

Status You may change the local label at any time, without coordinating with Alliance, keeping in mind that the general use of the code must be consistent with central. To add and begin using a code not yet in the local table, please contact Alliance office first. See Status codes

Item Type (IType) Contact Alliance before adding or changing an item type code or label, to map the code to an appropriate central code for circulating (regular or short loan, or non-circ), and to update the master file of codes and uses (labels). more info: mapping local ITypes to Alliance ITypes

ICode2, or whichever Item fixed field is used for suppression and contribution: Contact Alliance before adding or changing an ICode2 code. Keep in mind that codes recognized by INN- Reach software (l,n,s,z,g,o) must be used consistent with the INN-Reach use and definition or "translated" via a mapping table. (more info about this field)

Code4, or whichever Order fixed field is used for suppression and contribution: Contact Alliance before adding or changing codes. Keep in mind that codes recognized by INN- Reach software (l,n,s,z,g,o) must be used consistent with the INN-Reach use and definition or "translated" via a mapping table

Scode2, or whichever Item fixed field is used for suppression and contribution: Contact Alliance before adding or changing codes. Keep in mind that codes recognized by INN- Reach software (l,n,s,z,g,o) must be used consistent with the INN-Reach use and definition or "translated" via a mapping table.

Patron type (PType) Contact Alliance before adding or changing a patron type code or label, so that the code can be mapped to an appropriate central ptype code and the master file updated. more info: mapping local ITypes and PTypes to Alliance ITypes and PTypes