You are here: Reports > FAQs for the Reports Module > Indexed MARC Tag Matching

Indexed MARC Tag Matching

When a report 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 that MARC tag for that particular catalog format.

For example, if the indexed MARC tag number selected as the matching criteria is the 020 tag and the catalog format of the incoming record is MARC, SirsiDynix Symphony examines the keyword index variations configured for the 020 tag for records of the MARC catalog format, then their corresponding internal name values, as shown in the following table:

Indexed MARC tag number specified for matching	Keyword variations	Internal name
020	020	T020
020	BATH1007	BT04

SirsiDynix Symphony first checks for any keyword variations that have the same name as the indexed MARC tag being used for matching; SirsiDynix Symphony will use the internal name belonging to that keyword variation if the keyword variation name is the same as the type of indexed MARC tag. Otherwise, SirsiDynix Symphony will check other valid keyword variations.

For example, for the 020 tag shown in the table above, SirsiDynix Symphony will use the internal value of the 020 keyword variation first; if there was not a keyword variation of 020, SirsiDynix Symphony would use the internal name value of the BATH1007 keyword variation instead.

Once SirsiDynix Symphony has determined which internal name to use for matching the existing record and the incoming record, SirsiDynix Symphony will check the values inside the internal names for the incoming record . For example, if SirsiDynix Symphony is using the BATH1007 keyword variation to match records, SirsiDynix Symphony will search all the BATH1007 entries in the incoming record for a match with the BATH1007 entries in the existing record. If SirsiDynix Symphony finds a match, SirsiDynix Symphony merges the records.

Whether or not the existing record that is merged with the incoming record keeps its former catalog format or receives the catalog format from the incoming record is determined by the report being used to merge the records.