...
*In the Alma context, “repository import profiles” are used to load bibliographic records and in some cases create inventory associated with those bibliographic records.:
...
Summary best practices:
Normalization
Use “allUC Normalization #1”
RMFG is still developing normalization rules, this page (and others) will be updated as needed
Merge
Use “allUC merge rule #1”
RMFG is still developing merge rules, this page (and others) will be updated as needed
Naming conventions
Match method
Use unique “OCLC identifier match method”
Set management tags: leave “suppress” unchecked
Do not check “Allow bibliographic record deletion”
...
Use Network Zone: this will always be set to “Yes” if using a template copied from the NZ; there is no way to change it. If records are meant to be IZ-only campuses will have to build their own profiles or copy from the CZ.
Profile name: if the profile is shared in the NZ and meant for the entire system, it should start with “allUC,” if the profile is shared in the NZ but is campus specific, it should start with campus initials. IZ-only profiles should follow local campus naming conventions.
“Originating system” is up to each campus/situation.
Import protocol is up to each campus/situation.
Physical source format is up to each campus/situation.
Encoding format is up to each campus/situation but ideally UTF-8.
Source format is up to each campus/situation.
Status must be set to “active” for the profile to be used.
File name patterns are up to each campus/situation.
Target format is generally MARC21.
Normalization & Validation:
Filter out the data using: is up to each campus/situation but there are shared indication rules available in the NZ if desired.
Correct the data using: campuses are strongly encouraged to use “allUC [name]’ since this matches the normalization used in the WorldCat Daily Updates. Campuses can do more granular normalization but should be aware that any records with OCLC numbers are subject to the update process and some fields may be re-added to the records.
Handle invalid data using: this is situational but also not likely to need adjusting.
...
Import local extensions: is situational but probably a good idea
...
Match Profile
Match by Serial/Non Serial: is up to each campus/situation but if records have OCLC numbers should probably use the OCLC method to reduce multi-matches.
...
Handling method: should be set to automatic; setting to manual will pause the import job until multi-matches are manually resolved
Upon match: this is somewhat up to each campus/situation. If the records are meant to replace existing NZ records then choose “merge,” otherwise use “do not import” or “use existing” as needed.
Merge method: if merge is selected then use “all UC [name].
Leave “allow record deletion” unchecked.
“Do not merge/override with a lower brief version” should be checked.
Community Zone record handling: this is situational. If you want to re-link portfolios from the CZ to the imported ILS bibs, select that option. If not, skip the records.
Automatic Multi-Match Handling: this is situational but in most cases probably want to skip matches for CZ bibs.
No match: this is situational but outside of bibs created for order purposes, if the records do not have OCLC numbers they should not be added to the NZ during import.
...
Match actions:
...