Load Tab
Make selections on this tab when loading bibliographic records with order information or loading bibliographic records with selection list information. See the following report topics for important information about how these fields are interrelated.
| • | Load Bibs with Order Info Report |
| • | Load Bibs for Selection Report |
| • | Load Bibs with Selections and Decisions Report |
On Unicode systems, if SirsiDynix flat format records are provided for loading, these records must be encoded UTF8. Also the encoding scheme code in the .000. entry of each flat record (the 8th position of 000|a) must have the value (a) as in the following example.
.000. |aamI 0c a
SirsiDynix reserves the 999 tag for a special use in the 9XX record loading process; records to be loaded by Acquisition Load group reports should not contain a 999 tag.
The following selections may display on this tab, depending on the report that is configured.
| • | Access Restriction |
| • | Bib Classification |
| • | Class Scheme |
| • | Classification |
| • | Compare Multiple Occurrences of a Title Control Number Field (Not Recommended) |
| • | Copy Processing |
| • | Create Accountability Based On Default Data |
| • | Create Accountability Based On Title Information Entry |
| • | Default Holding Code |
| • | Default Record Format |
| • | Do Not Create Accountability Information |
| • | File to Load |
| • | Ignore Catalog Record Format |
| • | Indexed MARC Tag Number |
| • | Match on Title Control Number |
| • | Match on Title Control Number AND Indexed MARC Tag |
| • | Match on Title Control Number OR Indexed MARC Tag |
| • | Need to Know |
| • | Remove Entries Listed in the file “Junktag” |
| • | Remove Subject Headings |
| • | Review Date |
| • | Shadow Loaded Records |
| • | Title Control Number Matching Rule |
| • | Title Control Number Source for Incoming Items |
| • | Update Title Control Information from Title Information Entry |
The Access Restriction field only appears on systems configured for accountability and is available only when the Create Accountability Based on Default Data option is selected. Select an access restriction from the drop-down list. The values presented in this list are defined in the Restrict Wizard. As bibliographic records are loaded, the title and item accountability records created will be assigned this default access restriction. The review date for this access restriction will be set to the date selected in the Review Date field on this tab.
The Bib Classification field only appears on systems configured for accountability and is available only when the Create Accountability Based on Default Data option is selected. Select a bibliographic classification from the drop-down list. The values presented in this list are defined in the Clearance Wizard. As bibliographic records are loaded, the title and item accountability records created will be assigned this default bibliographic classification. If you do not select a default bibliographic classification, the records will be set to the same value as the Classification field.
The Class Scheme selection allows you to select any class scheme policy which has an AUTO Make Rule attribute. Select a class scheme from the list. (Only those class schemes defined on your system that have an AUTO Make Rule are included in this list.) A SirsiDynix-generated (XX10001.1) call number is assigned in the library of the first holding code specified in the incoming record. AUTO is the default value.
The Classification field only appears on systems configured for accountability and is available only when the Create Accountability Based on Default Data option is selected. Select an accountability classification from the drop-down list. The values presented in this list are defined in the Clearance policy wizard. As bibliographic records are loaded, the title and item accountability records created will be assigned this default classification.
Important: The Classification field is required. If you do not select a default classification, the report will not run.
Compare Multiple Occurrences of a Title Control Number Field (Not Recommended)
If this check box is selected, all recurring fields in the record, such as ISBN 020, will be compared against the existing title control key. Also, the 035 field which has prefixes indicating that it is an WLN, RLIN, OCLC, or SirsiDynix number may have multiple occurrences within a record. All of the fields with the designated prefix in the incoming record will be matched against the existing title control key. If the check box is cleared, only the first field (or the first field with a matching prefix for the 035) that was selected in your match list and is encountered in the incoming record will be matched against the existing title control key. The first key encountered is always used for new records.
Items may be created automatically during the load process. If this check box is cleared, the report loads the catalog records with no items. If the check box is selected, the report creates one item for each catalog record it loads. By default (and by SirsiDynix’s recommendation), the check box is cleared.
Create Accountability Based On Default Data
This field only appears on systems configured for accountability. When you select this option, the Classification, Bib Classification, Access Restriction, Need to Know, and Review Date fields become available. You must select a value for the Classification field; the other fields are optional. After you make these selections, as bibliographic records are loaded, title and item accountability records will be created with the selected defaults.
Important: The Classification field is required. If you do not select a default classification, the report will not run.
Create Accountability Based On Title Information Entry
This field only appears on systems configured for accountability. When you select this option, the Entry ID field becomes available. Select the entry ID that contains the title and item accountability information. After you make these selections, as bibliographic records are loaded, title and item accountability records will be created with the classification, bib classification, access restriction, need to know, and review date values found in this entry. The entry can contain multiple access restriction and need to know values.
Important: If the entry does not contain a classification value, or if the classification is invalid, the bibliographic record will not be loaded but written to the error file, and a message will be written to the report log.
SirsiDynix Symphony Administrators may use an existing 9XX entry with the designated subfields for accountability information, or they may create a new 9XX entry ID/entry for this purpose.
The title information entry ID for accountability should contain the following subfields.
|a Classification
|b Bibliographic classification
|c Access restriction
|d Need to know
|e Review date
The default holding code is used when you choose to ignore holdings statements or there are no holdings statements present in the bibliographic records to be loaded. All of the records loaded by the report will use the library and location information defined by the selected holding code. Select a holding code from the list. The default holding code is DEFAULT.
This format is assigned to records that do not have enough information to be mapped to a format in SirsiDynix Symphony. When a record is loaded, the format, such as MARC or SERIAL, is mapped from the bibliographic record’s leader codes as specified in the Bibliographic Map policy. If a Bibliographic Map policy is defined for the leader codes, SirsiDynix Symphony will supply a format based on the same leader codes. If the leader codes used to determine the record format are missing, the Default Record Format is used. This field is required. Select a record format from the list.
Do Not Create Accountability Information
This field only appears on systems configured for accountability. If you select this option, no title or item accountability records will be created for the loaded bibliographic records. This option is selected by default.
The records to be loaded must have already been imported using the MARC Order Import Utility wizard for loading bib records with order information or the MARC Selection Import Utility wizard for loading bib records with selection list information. Select a file to load from the list. This selection is required.
If this check box is selected, SirsiDynix Symphony will ignore the catalog record format when matching records using either the Match on title control number or indexed MARC tag option or the Match on title control number and indexed MARC tag option. For example, if SirsiDynix Symphony matches two records with the same value for an indexed MARC tag and one record has a catalog record format of MUSIC and the other has a format of MARC, SirsiDynix Symphony will match the two records in spite of the differing record formats if this check box is selected.This field specifies the MARC tag values to check for a match in addition to the title control number, depending on the selected Match On Indexed MARC Tag Number option. If you select one of the Match on Indexed MARC Tag Number options, use the Match MARC Tag Hierarchy gadget to select Indexed MARC Tag Number values. SirsiDynix Symphony checks the catalog for a MARC tag match on the first Indexed MARC Tag Number value. If no match is found, the second Indexed MARC Tag Number is checked, and this pattern continues until either a match is found, or all Indexed MARC Tag Numbers have been checked. Note The Indexed MARC Tag Number field is available only when the Match on Title Control Number and Indexed MARC Tag option or the Match on Title Control Number or Indexed MARC Tag option is selected.
For detailed information on how SirsiDynix Symphony matches on indexed MARC tag numbers, see Indexed Tag Matching.
The record is considered a match only if the control number matches a title control number found in one of the Title Control Number Source fields. The following message displays in the finished report log when this option is selected.
Bibliographic records will be matched by flexible key
Match on Title Control Number AND Indexed MARC Tag
The record is considered a match if the title control number of a library catalog record matches one of the specified Title Control Number Source fields in the imported record, AND if at least one of the standard matching numbers from the incoming record (as listed in the Indexed MARC Tag Number field) matches an existing SirsiDynix Symphony database index. Both conditions must be met for the record to be considered a match.
The list you create of additional match keys (tags) is hierarchical in nature. The report will examine the first key in the list, such as the 010, and if there is a match, no further matching will occur. If a match is not found, the report will use the second key in the list to search for a match, and so forth. The match process will always start with the 010 tag. If a tag is repeated (such as multiple 020 tags) the report will examine each occurrence of the repeated tag.
For example, the report examines the 001, the title control number of the library catalog, and finds a match. Then, the report examines the first tag in the list, the 010, doesn’t find a match. The report examines the next tag in the list, the 035. It doesn’t find a match so it goes to the next tag in the list, the 020. There are multiple 020 tags, so the report examines each 020. It finds a match in the second 020, so the match process is complete.
The following message displays in the finished report log when this option is selected.
Bibliographic records will be matched by flexible key AND the text index
For detailed information on how SirsiDynix Symphony matches on indexed MARC tag numbers, see Indexed Tag Matching.
Match on Title Control Number OR Indexed MARC Tag
The record is considered a match if the title control number of a library catalog record matches one of the specified Title Control Number Source fields in the imported record, OR if one of the standard matching numbers from the incoming record (as listed in the Indexed MARC Tag Number field) matches an existing SirsiDynix Symphony database index. Either condition can be met for the record to be considered a match
The list you create of additional match keys (tags) is hierarchical in nature. The report will examine the first key in the list, such as the 010, and if there is a match, no further matching will occur. If a match is not found, the report will use the second key in the list to search for a match, and so forth. The match process will always start with the 010 tag. If a tag is repeated (such as multiple 020 tags) the report will each occurrence of the repeated tag.
For example, the report examines the 001, the title control number of the library catalog, and doesn’t find a match. Then, the report examines the first tag in the list, the 010, and it doesn’t find a match. The report examines the next tag in the list, the 035. It doesn’t find a match so it goes to the next tag in the list, the 020. There are multiple 020 tags, so the report examines each 020. It finds a match in the second 020, so the match process is complete.
The following message displays in the finished report log when this option is selected.
Bibliographic records will be matched by flexible key OR the text index.
For detailed information on how SirsiDynix Symphony matches on indexed MARC tag numbers, see Indexed Tag Matching.
The Need to Know field only appears on systems configured for accountability and is available only when the Create Accountability Based on Default Data option is selected. Select a need to know from the drop-down list. The values presented in this list are defined in the Need to Know Wizard. As bibliographic records are loaded, the title and item accountability records created will be assigned this default need to know. The review date for this need to know value will be set to the date selected in the Review Date field on this tab.
Remove Entries Listed in the file “Junktag”
Certain entries may not be used in completed catalog records in your library. The junktag file in the /Unicorn/Custom directory lists any unused entries that are to be stripped from imported records. If the Remove Entries Listed in the file ”Junktag” check box is selected, the entries are automatically, completely removed from the new bibliographic record created by the report. If you clear this check box, all entries in the imported record will be loaded.
The removed entries cannot be restored.
In the reports that load bibliographic records with order information or that load bibliographic records with selection list information, entries used in the 9XX processing cannot be listed in the junktag file. This includes the 999 entry which SirsiDynix uses as part of 9xx processing, and any 9XX field the library uses to carry order/selection information.
When a bibliographic record that matches an existing database record is merged, no junktags processing takes place.
The display of entries is controlled through the Format and Entry ID policies.
Allows you to specify the subject headings that should be removed from the matching record, based on the 6XX second indicator values, before it is loaded into the catalog. Use the Subject Source gadget to select subject heading types.
The Review Date field only appears on systems configured for accountability and is available only when the Create Accountability Based on Default Data option is selected. Use the Calendar gadget to select a review date. This review date will be assigned to the access restriction and need to know values. If you do not select a review date value, the review date will default to NEVER.
Note: The review date in the |e subfield of the title information entry should be in the MM/DD/YYYY format.
Use this option to shadow catalog records loaded by this report. If you select this check box, the catalog records are shadowed as follows.
| • | A bibliographic record that is new to the catalog will be shadowed. |
| • | A bibliographic record that is merged with an existing catalog record does not affect the title level shadow flag of that record. |
| • | When new call number record is created, if the title is not shadowed, the call number will not be shadowed. |
| • | When an item is created for the new or merged title, the item is not shadowed. |
Note: This option appears in the Load Bibs with Order Info report, Load Bibs for Selection report, and Load Bibs with Selections and Decisions report.
Title Control Number Matching Rule
The Title Control Number Matching Rule determines how the records being loaded will relate to existing records, in terms of creating new records and updating existing records. Use the Title Control Number gadget to select a rule. Error records not related to flexkey matching will only be printed in the log if there is a problem with the MARC record or copy processing.
Title Control Number Source for Incoming Items
This field specifies the number that will be used as the title control number in SirsiDynix Symphony. In determining whether an incoming record matches a record already in the SirsiDynix Symphony database, the title control keys of existing records are matched against title control key of the incoming record. The first title control key in the list of rules to match is provisionally assigned to incoming record, and is then matched against existing title control keys. If a match is found, selection data is merged. If no match is found, a new record will be created and will be assigned the first title control key rule named in the list. Use the Title Control Key Rules Gadget to select control key rules. This selection is required.
Note: This match and load process guarantees that the originally assigned title control number is retained regardless of that number’s place in the title control key rule hierarchy.
Update Title Control Information from Title Information Entry
Whether or not the title is shadowed may be specified during the load process, as well as the dates created, modified, and cataloged, for each record using a title information entry such as the 948. Alternately, dates created and modified may be set to the date of the load itself. Use the Set Title Information Gadget to select the entry to be used for updating title information.
Note: If multiple matching records exist in the SirsiDynix Symphony database, only the first title encountered is updated.
Related topics
Load Bibs with Order Info Report
Load Bibs for Selection Report
Load Bibs with Selections and Decisions Report
Match MARC Tag Hierarchy Gadget
Title Control Key Rules Gadget