Reasons why a cross-reference was created¶

Background¶

Animals can be referred to by multiple IDs over their lifetime. These IDs can be “cross-referenced” and all used to refer to the same animal. Within the national cooperator database, an animal’s data is connected to an internal animal key, including multiple IDs. Typically, there is an ID that is considered the primary ID, determined by several factors, for example, ID system reliability (840 > 982 tag series). Lower preference IDs can also be used to refer to and query the animal, but may not be the ID that shows up on CDCB files or publications.

IDs can be cross-referenced explicitly by collaborator submissions or can be created automatically as part of processing when it is suspected that records refer to the same animal. If an ID was incorrectly used for an animal, and the correct ID has been discovered, a ReID procedure may be appropriate to resolve the IDs. If both IDs exist in the database, a ReID will merge the data under both IDs if conditions are met, and delete the ID designated as erroneous. In the case that the correct ID does not exist yet in the system, the data is merged under the ID designated as correct, and then the ID designated as incorrect is deleted. More information on when a ReID may be appropriate, and the conditions under which ReIDs may occur during processing, is also below.

Explicit Cross-References¶

The CDCB phenotypic formats (1, 4, 5, 6, 8) contain a field known as the cross-reference field in positions 54-70. An explicit cross reference could occur if the cross-reference field is filled and the record type code in position 88 is P (Format 1), L (Format 4), B (Format 5), H (Format 6), S (Format 8), or X (Format 1, Format 4 + Lactation Type Code = P). Please note that for nomination records (Format 1 + Record Type G, aka Format 1Gs), the cross-reference field is used to include sample IDs, and does not create cross-references. If a cross-reference is created, there is a source code attached to the cross-reference denoting the source code origin of the ID.

If two IDs referring to the same animal exist independently in the national cooperator database, a cross-reference should be submitted to combine all of the animals' data under one key. To process the cross-reference, the pedigrees of the two IDs must match, and the birth date mustn't be an estimated birth date for either ID.

If one of the IDs does not exist in the national cooperator database, adding the ID as a cross-reference can be done via Format 1 or through WebConnect. Instructions on submitting cross-references can be found here: Corrections to pedigrees

Cross-references can also be deleted if two IDs should not be connected. Instructions for removing cross-references can be found here: Corrections to pedigrees

Cross-Reference Creation by CDCB Processing¶

During CDCB processing, data for potentially connected animals is being reconciled. Because data comes from many different sources, the data for one animal can be disconnected. Processing tries to pull the data for an animal together without creating conflicts with other close relatives. Maternal siblings are especially checked against one another. While this is done with the best intentions, incomplete or incorrect data can cause animals to be incorrectly merged. If a cross-reference occurs due to processing, you will receive a phenotypic return code notifying you that it has occurred.

Some cases where IDs can be merged:

• IDs have a matching pedigree, country code of ID, and a 12-byte unique ID, but a different ID breed code
• IDs are found within the same herd code, and with the same cow control number in a 273-day interval
• IDs have matching pedigree parentage, multi-birth code (MBC) of 1, and a birth date within 10 days
• IDs have a matching pedigree with the identical animal name

ReIDs vs. Cross-References¶

As stated above, a ReID will merge the data of two independently existing IDs if conditions are met, and delete the ID that is designated as being incorrect. Information that will be merged and moved includes pedigree, nomination, genotype, lactation data, etc. This is appropriate to use if the ID currently containing data for the animal should not be used to refer to the animal in the future. The procedure for creating a ReID is available here: Corrections to pedigrees

ReIDs can also occur during CDCB processing.