The Load Bibliographic Record Options Window:
Match Points
Match points are used to specify the entries in the incoming MARC record that will be used to check for a possible match in the catalog. Each match point is a lower case one-letter code that refers to a specific MARC entry. Match points are also used to create the title control number of the new record. Multiple codes should be entered without spaces or punctuation between them.
When loading a bibliographic record, Unicorn will check the catalog for a match on the first match point value. If no match is found, the second match point will be checked, and this will continue until all match points have been checked or an actual match with the catalog happens. In the above example, we are checking for a match on l (LCCN in 010), s (ISSN in 022), and i (ISBN in 020).
On the other hand, if the incoming record lacks the specified MARC entry, the next match point in the record will be checked, and so on until it either finds one or runs out of match points. In other words, the first match point that is found in the incoming record will be checked against the catalog. If no match points are found in the incoming record, no check will be performed against the catalog and the record will be loaded into the Loading Bib Record Window in Workflows.
Matching is made by comparing the match point with title control numbers in the catalog. If no matches are found, the incoming record will be loaded into the Loading Bib Record Window in Workflows. However, if a match does occur, Workflows will let you know which match point the match occurred. The record will still be loaded into the Loading Bib Record Window. If you click OK at this point, you will replace the record in the catalog with the incoming record. If you click close the import of the incoming record will cease.
A Warning dialog box indicating a match in the catalog:
Replacing title control numbers by using match points
When replacing a minimum level record or just a record that needs to be upgraded bibliographically, SmartPORT gives you the ability to update the title control number. This can be done by following the first match points with a forward slash followed by match points intended for updating the title control number. In the example above, we are using the same values used for matching to determine the new title control number.
Match points supported by SmartPORT:
| Code | MARC entry | Code | MARC entry |
| c | Gaylord control number (001) | n | LCCN (001) |
| g | Local number, as is (001) | o | OCLC number (001) |
| h | Local number, as is (035) | p | OCLC number (035) |
| i | ISBN (020) | q | Laserquest number (001) |
| j | ISBN (021) | r | RLIN number (001) |
| l | LCCN (010) | s | ISSN (022) |
| m | Marcive key (900) | w | WLN key (035) |
Call Number Sources
The Call Sources field is used to specify where to obtain the call number. It consists of four values separated by commas: class scheme, entry (MARC field), subfields to use, and whether the last occurrence of the entry should be used (Y or N). Multiple sources of call number information may be specified, separated by slashes. The call number that is obtained, if one is found, will be placed in the Call Number field of the Loading Bib Record window in Workflows.
In the example used above (LC,50,,N/LC,90,,N), we first type in the class scheme of LC, then the MARC field to look at which is 050 (the first zero is optional). Since the third value is blank, we will use all subfields of the 050. The last value indicates that we will use the first occurrence of 050. If the incoming record does not contain an 050, the next set of values will be checked (in this case, we will look for an 090). If neither an 050 or 090 are in the incoming record, then the term "AUTO" will be placed in the Call Number field of the Loading Bib Record window.
Valid values to use as a call number source:
| Position (1,2,3,4) | Valid values |
| 1 | LC, DEWEY, SUDOC, ASIS, LCPER |
| 2 | 50,86,90 |
| 3 | [blank],a,b |
| 4 | Y, N |