Indexed Tag Matching
When a report or the SmartPort wizard is configured for matching on an indexed MARC tag number, SirsiDynix Symphony first attempts to determine a match based on valid Internal Name values assigned to the selected field for that particular catalog format.
For example, if the indexed tag number selected as the matching criteria is the 020 field and the SirsiDynix Symphony catalog format of the incoming record will be MARC (as opposed to VM, MUSIC, or another catalog format), SirsiDynix Symphony examines the keyword index variation(s) configured for the 020 field for records of the catalog format, then their corresponding internal names, as shown in the following table:
|
Indexed tag number specified for matching |
Keyword variations |
Internal name |
|---|---|---|
|
020 |
020 |
T020 |
|
BATH1007 |
BT04 |
Determining the index to use for matching
SirsiDynix Symphony appends a "T" character to the front of the tag number and searches for the resulting internal name first before considering other internal names (for example, for the 020 field, SirsiDynix Symphony first checks for a "T020" internal name). SirsiDynix Symphony will use the internal name belonging to that keyword variation if the internal name (before appending the "T" character) is the same as the indexed tag selected for matching. Otherwise, SirsiDynix Symphony will check all valid internal names of all keyword variations assigned to the selected field.
For example, for the 020 field shown in the table above, SirsiDynix Symphony will check the internal name of the 020 keyword variation (T020) first; if there is not an internal name similar to "020" within the keyword variation assigned to the 020 field or a match with that internal name is not found, SirsiDynix Symphony searches the internal names of all the selected tag's keyword variations together. In the scenario described by the table above, if SirsiDynix Symphony could not find a T020 internal name to use for matching, SirsiDynix Symphony checks for any other valid internal names to use for matching. In this example, SirsiDynix Symphony would use the BT04 internal name.
Matching records
Once SirsiDynix Symphony has determined which internal name to use for matching records, SirsiDynix Symphony will attempt to match the bibliographic tag in the incoming record with the internal name entries for any matching tag in the existing catalog record.
For example, if SirsiDynix Symphony is using the BATH1007 keyword variation (which has an internal name of BT04) to match records, SirsiDynix Symphony will extract the data from the 020 field in the incoming record and attempt to match on the BT04 internal name value representing the 020 field in the existing catalog record. If SirsiDynix Symphony finds a match, SirsiDynix Symphony updates the bibliographic records or uses other rules set in the report selections to process the record.
The data SirsiDynix Symphony extracts depends on the contents of the field corresponding to the indexed tag. If the field contains an ISBN, SirsiDynix Symphony normalizes the extracted contents of the field to a standard 13-digit ISBN. For any other type of field in the record, the data in subfield a is extracted and used for matching.
When matching records based on indexed tags, reports may not accurately reflect the criteria that SirsiDynix Symphony used to match the records in the report output (for example, the report output may report that two records were matched based on a flex key when in fact the match was made based on an indexed tag number).
Related topics