Shared Import Profiles / Normalization Rules Naming Conventions

Document status	APPROVED
Area covered	Cataloging, Systems
Lead Author	@Micah Jeffries (Unlicensed)
Co-authors	@Marcus Jun (Unlicensed), @Moon Kim (Unlicensed), Elizabeth Rallos, Jeremy Hobbs

Background

Import profiles and normalization(norm) rules can be created and managed for the Institution, Community and Network zone. Within the Resource Management Configuration Import Profiles screen, profiles are displayed in alphabetical order. Norm rules are also listed in alphabetical order, but in the Metadata Editor. With 23 campuses contributing to profiles and rules to the network zone and several consortia contributing to the Community Zone there is a potential for the lists of profiles to become unwieldy.

Policy Statement

This policy will apply to import profiles and normalization rules created for use in the Network and Community Zones. By adopting a standard naming convention for import profiles and normalization rules CSU libraries should be able to search and find the needed resource more efficiently.

Best practice recommendations

Import Profiles

The base profile name should contain the vendor, package or source of the records, followed by the type of records being imported, such as physical, electronic, or mixed.

For example:

Network Zone records start the profile with the following:

PACKAGE/VENDOR/SOURCE + PHYSICAL/ELECTRONIC/MIXZED

GOBI Physical

For Community Zone records start the profile with the following:

CSU + PACKAGE/VENDOR/SOURCE + PHYSICAL/ELECTRONIC/MIXZED

CSU EBL ELECTRONIC

Normalization Rules

The base rule name should contain the primary action, relevant MARC field(s), (data type or phrase to be included omitted, or modified).

For example:

Network Zone records start the profile with the following:

PRIMARY ACTION + MARC FIELD(S) + DATA

"add 999 Affordable Learning Solutions"

"remove 938, 945"

"modify 599 change collection to Collection"

For Community Zone records start the profile with the following:

CSU + PRIMARY ACTION + MARC FIELD(S) + DATA

"CSU add 599 Roddenberry Collection"

"CSU remove 029, 938"

"CSU modify 650 change to North America"

Action log

Section	Point Person	Expected Completion Date	Last action taken	Next action required

Section	Point Person	Expected Completion Date	Last action taken	Next action required
Articulate the need for the policy (background)	@Micah Jeffries (Unlicensed)	Oct 14, 2016
Create a Policy Statement	@Micah Jeffries (Unlicensed)	Nov 11, 2016	Added statment	Request review
Identify and create best practice recommendations	@Micah Jeffries (Unlicensed)	Dec 13, 2016
Where applicable, identify and write up procedures in Alma	@Micah Jeffries (Unlicensed)	Dec 13, 2016