MARC Listener: Bibliographic Wizard
MARC Listener Bibliographic policies determine how bibliographic records exported from OCLC Connexion® are loaded into the SirsiDynix Symphony catalog. Symphony automatically indexes the bibliographic records you imported; once this occurs, these records become available in the catalog.
This wizard is only available after SirsiDynix has enabled the Import from OCLC Connexion® feature for your library system. If your library is interested in using the Import from OCLC Connexion® feature, contact SirsiDynix Customer Support.
For more information on what is required for this import process, see Importing Bibliographic and Authority Records from OCLC Connexion.
This policy only affects how bibliographic records are loaded into SirsiDynix Symphony specifically from an OCLC Connexion® client. If you want information about loading bibliographic records from other sources, see the Acquisition Load Group Reports for a list of reports you can use to load bibliographic records into Symphony.
The policy contains the following attributes:
| • | Name |
| • | Description |
| • | User ID |
| • | Password |
| • | Station |
| • | Language |
| • | Title Control Number Matching Rule |
| • | Match on Title Control Number |
| • | Match on Title Control Number or Indexed MARC Tag |
| • | Match on Title Control Number and Indexed MARC Tag |
| • | Match on Catalog Key |
| • | Compare Multiple Occurrences of a Title Control Number Field (Not Recommended) |
| • | Ignore Catalog Record Format |
| • | Update Date Cataloged |
| • | Default Record Format |
| • | Update Title Control Information from Title Information Entry |
| • | Update Bibliographic Record When Updating Records |
| • | Update Publication Year |
| • | Remove Entries Listed in the File "Junktag" |
| • | Change Order of MARC Tags According to Catalog Format Policy |
| • | Remove Subject Headings |
| • | Copy Processing |
| • | Call Number Load Rules |
| • | Default Holding Code |
| • | Update AUTO-Assigned Call Numbers |
| • | Create/Update Price from Holdings Statement, 020 Subfield c |
| • | Preserve Spaces in Analytic Prefixes |
| • | Enable System Logging for Import Transactions |
This attribute uniquely identifies the Bibliopgraphic MARC Listener policy. This name is ten characters or less, and may not include spaces or punctuation, except for dash (-), underscore (_), and dollar sign ($). Additionally, the pipe character (|) may not be used.
This value is the name you provide to the OCLC Connexion® client in the Logon ID field of the export profile.
This attribute is required.
This attribute describes the purpose of the MARC Listener Bibliographic policy, and is used for reference purposes only. The description may be up to 60 characters in length. Although the Description attribute may contain spaces and punctuation, the pipe character (|) cannot be used.
This attribute specifies the user that SirsiDynix Symphony should associate with the commands it sends to support the feature. The value of this attribute is included in any logging for the MARC Listener feature. When the Enable System Logging for Import Transactions attribute is enabled, Symphony saves this logging to /Unicorn/Logs/Sys files; however, Symphony always saves User ID information to history logs. To choose a user, use the Browse User gadget.
This attribute specifies the password that corresponds to the user provided in the User ID field. This value is the password you provide to the OCLC Connexion® client in the Password field of the export profile. The password may be up to 62 characters in length. This value is stored securely in the SirsiDynix Symphony database.
This attribute is required.
This attribute specifies the Station policy SirsiDynix Symphony should associate with the commands it sends to support the feature. The value of this attribute is included in any logging for the MARC Listener feature. When the Enable System Logging for Import Transactions attribute is enabled, Symphony saves this logging to /Unicorn/Logs/Sys files; however, Symphony always saves Station information to history logs.
This attribute specifies a Language policy; SirsiDynix Symphony returns output information and any error messages in this language.
This attribute is required.
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.
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.
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.
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.
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 catalog key matches a catalog key found in the MARC tag or the MARC tag subfield specified in the Catalog Key Source for Incoming Items field or the Catalog Key Source Subfield field respectively. The catalog key in the incoming bibliographic record does not need to have a particular prefix (such as "a" or "u") to match an existing catalog key.
If there are multiples of the same MARC tag in the record, SirsiDynix Symphony matches the records based on the first of these tags that contains a catalog key.
Select a method of catalog key matching from one of the following options:
| • | Title control number source for incoming items—The Title Control Number Source for Incoming Items prescribes 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 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 order 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. |
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.
| • | Indexed MARC tag number—The Indexed MARC Tag Number 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.
| • | Catalog key source for incoming items—The Catalog Key Source for Incoming Items specifies the MARC tag in which SirsiDynix Symphony can find the catalog key to use for matching records. To determine whether an incoming record matches a record already in the Symphony database, Symphony compares the catalog key of the existing record with the catalog key of the incoming record in the specified MARC tag in each record. If Symphony finds a match, it merges the bibliographic data. If Symphony does not find a match, it creates a new record and assigns it an automatically-generated catalog key. |
This drop-down list is only available if the Match on Catalog Key option has been chosen.
| • | Catalog key source subfield—The Catalog Key Source Subfield specifies the MARC tag subfield SirsiDynix Symphony should use to check for a catalog key match in addition to the MARC tag specified in the Catalog Key Source for Incoming Items field. Select a MARC tag subfield from the drop-down list. Symphony checks the catalog for a catalog key match in the specified MARC tag subfield. |
This field is only available if the Match on Catalog Key option has been chosen.
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, or OCLC 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 this 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.
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.
Note: For detailed information on how SirsiDynix Symphony matches on indexed MARC tag numbers, see Indexed Tag Matching.
This attribute determines what the Date Cataloged value should be on each imported bibliographic record. Select one of the following options:
| • | No date—Incoming bibliographic records do not have a Date Cataloged value. |
| • | Today—Incoming bibliographic records have a Date Cataloged value of today's date. |
| • | No change—Incoming bibliographic records do not have their Date Cataloged value modified during the import. |
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 not 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. Select a record format from the list.
This attribute is required.
Update Title Control Information from Title Information Entry
This attribute specifies 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 and the date cataloged may be set to a batch date set in the load report. Use the Set Title Information gadget to select the entry ID that contains this title information.
Update Bibliographic Record When Updating Records
It may be more efficient to create or update call numbers and copies from loaded holdings statements than to do it manually. Clear this check box if no changes need to be made to the cataloging and only item information will be updated. If multiple matching records exist in the SirsiDynix Symphony database, and you choose to update matching records, only the first title encountered is updated.
This selection updates the publication year in the fixed field from the incoming record or entry type. The publication year is always updated when a record is loaded, and this value must be selected, and cannot be cleared.
Note: For UNIMARC records, the publication year is not always updated. If the U100 DATE1 field is empty, and if the U210 |d either doesn’t exist or doesn’t contain a 4-digits, the publication year will not be reset.
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 bibliographic record after the incoming record has been merged with the matching database record. If you clear this check box, all entries in the imported record will be loaded.
Note: The removed entries cannot be restored.
The display of entries is controlled through the Format and Entry ID policies.
Change Order of MARC Tags According to Catalog Format Policy
This attribute specifies whether or not SirsiDynix Symphony should change the order of the MARC tags of the incoming record. If this attribute is enabled and the incoming record matches an existing record, Symphony arranges the record's MARC tags in the order determined by the existing record's catalog format. If the incoming record does not match an existing record, Symphony determines the catalog format from the incoming record's MARC leader tag. If Symphony cannot determine a catalog format using the incoming record, it uses the catalog format specified in this policy's Default Record Format attribute.
If this attribute is not specified, SirsiDynix Symphony doesn't change the order of the MARC tags of the incoming record; the MARC tags remain in the order in which they were listed in OCLC Connexion®.
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.
Copies may be created automatically during the load process using a holding code entry such as the 949, or created or modified manually after the load. Use the Copy Processing Gadget to select a copy processing method.
The rules selected in this attribute determine how the SirsiDynix Symphony call number will be created from the bibliographic record, and what class scheme is being used. Use the Call Number Load Rules gadget to select a rule or list of rules.
When a holdings entry (such as the 999) is used to add holdings, there must be a call number load rule for that entry, and it should be the first call number load rule listed. When a copy processing option that references a holding statement is selected, the Copy Processing gadget automatically adds a call number load rule for that entry, and it is added as the last call number load rule. This call number load should be ordered at the top of the list.
This attribute 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 will use the library and location information defined by the selected holding code. When a holdings statement is present and being used to create calls/items, but a specific subfield contains an invalid value, the invalid value will be replaced with a valid value from the selected default holding code. Select a holding code from the list.
This attribute is required.
Update AUTO-Assigned Call Numbers
Records created ”on the fly” often have an automatically generated call number. Select this check box to replace any AUTO call numbers in matched records with the incoming call number.
Create/Update Price from Holdings Statement, 020 Subfield c
Each item has a Price field at the copy level, which may be updated from subfield p of the holdings statement, or from subfield c of the 020 tag. Clear this check box to retain the price in existing copy records.
Preserve Spaces in Analytic Prefixes
SirsiDynix Symphony by default removes the spaces from call number records that contain analytic entries such as "v. 1" or "vol. 1". If your library includes a space in these types of entries, this might produce duplicate records for a single call number (for example, one version including the space and the other not). The Preserve Spaces in Analytic Prefixes attribute lets you prevent the MARC Listener from deleting the space.
Enable System Logging for Import Transactions
This attribute instructs SirsiDynix Symphony to log import transactions in the /Unicorn/Logs/Sys files on the Symphony server.
Related topics