Match profiles: Most commonly used

This list of match profiles shows the most common ones used for matching and updating Inventory records (Instances, Holdings, Items). This list does not have the complete details. See working document here (very rough)

Color key

Black = match is being used
Red = match is needed, but not yet available
Blue = mentioned as a possible match, but not in use, or use case/example not yet identified

Instance records

Incoming record	Existing record	Notes
MARC Bib 001	Instance HRID
MARC Bib 001	MARC Bib 001	Usually this is the Instance HRID
MARC Bib 035$a	Instance OCLC number
MARC Bib 035$a	Instance System control number
MARC Bib 024$a	Instance Other standard identifier
MARC Bib 9xx$y	Purchase Order Line number (POL) associated with the Instance	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Available as of Morning Glory.
MARC Bib 9xx$y	Vendor reference number (from POL) associated with the Instance	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Available as of Morning Glory.
MARC Bib 999 ff $i	MARC Bib 999 ff $i	Instance UUID
MARC Bib 999 ff $s	MARC Bib 999 ff $s	MARC Bib SRS UUID
Static match	Instance status =	Used as a submatch, to determine whether an instance has been cataloged or is yet to be cataloged
Static match	Statistical code
Static match	Suppress from discovery	Use Static match Text = true and Instance record field: Admin data: Suppress from discovery as a submatch to narrow search results to only a single instance suppressed from discovery Use Static match Text = false and Instance record field: Admin data: Suppress from discovery as a submatch to narrow search results to only a single instance NOT suppressed from discovery Similar static matches can be constructed for the Instance Staff suppress and Previously held checkboxes
MARC Bib 039 9\	MARC Bib 035 9\	MARC Bib information in 035 9\
MARC Bib 035$a with qualifier "begins with"	MARC Bib 035$a with qualifier "begins with"	This is the match I use for almost all of our vendor records
Static match	MARC Bib 899$a	Local collection code field. Can be used as a secondary match to make sure the primary identifier match is selecting a record from the correct collection.
MARC Bib 01x, 02x, 03x 9xx	MARC Bib 01x, 02x, 03x, 9xx	Available as of Morning Glory For repeated fields, current functionality is Only first incoming field is considered for matching, but it matches against any copy of that field in the existing SRS MARC Need additional MARC-to-MARC matches for normalized control numbers, e.g. ISBN, OCLC number. See UXPROD-2742 Additional details about MARC-MARC matches for repeatable fields: Pretend that these fields are in an incoming record: (Field Ind1 Ind2 Subfield) 024 _ _ $a 12345 024 1 1 $a 45678 024 1 _ $x 67890 024 2 2 $x 67890 And the fields in the existing SRS record are 024 2 2 $x 67890 024 _ _ $a 12345 024 1 _ $x 13579 024 1 1 $a 45678 024 1 _ $x 67890 FOLIO only pays attention to the first incoming field, not the rest, but compares to any matching fields in the existing record. When setting up different match profiles, this is the logic that is in place now: If the match profile is 024 _ _ $a: Matches, because the incoming first 024 looks for an existing 024 with blank indicators and $a and the same value (even though that is the second 024 in the existing record) If the match profile is 024 1 1 $a: Matches, because the first incoming 024 with indicators 11 and $a (which is the second 024 in the incoming file) looks for an existing 024 with indicators 11 and $a and the same value (which is the fourth 024 in the existing record) If the match profile is 024 1 _ $x: Matches, because the first incoming 024 with indicators 1_ and $x (which is the third 024 in the incoming file) looks for an existing 024 with indicators 1_ and $x and the same value (which is the fifth 024 in the existing record) If the match profile is 024 2 2 $x: Matches, because the first incoming 024 with indicators 22 and $x (which is the fourth 024 in the incoming file) looks for an existing 024 with indicators 22 and $x and the same value (which is the first 024 in the existing record) However, pretend the incoming record looks like this: 024 1 1 $a 12345 024 1 1 $a 45678 And the existing SRS record is 024 1 1 $a 45678 If the match profile is 024 1 1 $a Does not match, even though “024 1 1 $a 45678” is present in both incoming and existing records. SRS starts searching a field specified in match profile, and only considers the first occurrence of 024 1 1 $a in the incoming record. The first occurrence is “024 1 1 $a 12345". So, SRS tries to match “024 1 1 $a 12345” and can’t find it in the existing record.

Holdings records

Incoming record	Existing record	Notes
MARC Bib 9xx$y	Holdings HRID	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
MARC Bib 9xx$y	Holdings UUID	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
MARC Bib 9xx$y	Former Holdings ID	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field. Is this currently being used? If so, please provide an example or use case..
Static match	Holdings Permanent location	Submatch after the correct Instance is identified
Static match	Holdings Temporary location	Submatch after the correct Instance is identified
MARC Bib 856$u	Holdings Electronic access URI	Needs testing to be sure it actually works
MARC Bib 856$y	Holdings Electronic access link text	Submatch after the correct instance is identified or a direct match. For 5C, a good use case is our NAXOS where we have 5 urls that are pretty much the same but our link text is all different and unique for each school. Having this match point would be powerful to work with our eResources
MARC Bib 9xx$y	Purchase Order Line number (POL) associated with the Holdings	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Available as of Morning Glory.
MARC Bib 9xx$y	Vendor reference number (from POL) associated with the Holdings	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Available as of Morning Glory.
Static match	Statistical code	Is this currently being used? If so, please provide an example or use case. (Note: Please see use cases above for stat code. For 5C with merged records, matching on stat code could be very powerful for updates and batch processes.)
Static match	Holdings Type?	Is this currently being used? If so, please provide an example or use case. UChicago has been using a static match on holdings type since Lotus. It is currently working in Nolana. We use this regularly to differentiate between holdings that are physical and electronic, especially when receiving shelf ready cataloging at the point of invoicing since the location will be same for both physical and electronic holdings. We also use it to make sure that we update the instance record with the electronic holdings attached vs the instance record with the physical holdings attached if both forms of the record have the same OCLC number, which happens with electronic record sets from vendors on a regular basis.
Static match	Holdings Call number type?	Is this currently being used? If so, please provide an example or use case.

Item records

Incoming record	Existing record	Notes
MARC Bib 9xx$y	Item HRID	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
MARC Bib 9xx$y	Item UUID	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
MARC Bib 9xx$y	Item Barcode	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field.
Static match	Item status?	Is this currently being used? If so, please provide an example or use case. Cornell: Static match on "on order" status to move an item from "on order" to "in process" (+1 for 5C)
MARC Bib 9xx$y	Item Accession number	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field. Is this currently being used? If so, please provide an example or use case.
MARC Bib 9xx$y	Item Former identifier	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC field. Is this currently being used? If so, please provide an example or use case.
MARC Bib 856$u	Item Electronic access URI	Needs testing to be sure it actually works
Static match	Statistical code	Is this currently being used? If so, please provide an example or use case. (Note: See use cases for instances and holdings for 5C.)
MARC Bib 9xx$y	Purchase Order Line number (POL) associated with the Item	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Available as of Morning Glory.
MARC Bib 9xx$y	Vendor reference number (from POL) associated with the Item	Can be in any MARC 9xx field except 999 ff, and in any subfield within that MARC 9xx field. Available as of Morning Glory.