...
| Page Properties | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
MARC fields in the OCLC master record should be retained because: 1) CSU policy is that libraries work at the network level, and part of that is minimizing maintenance on master records; and 2) once daily updates begin, the OCLC master record, when edited, will replace the corresponding Alma record automatically.
Policy Statement
Catalogers must retain all MARC fields in OCLC records when exporting from Connexion with the exception of the 029 field, which must be deleted. The 029 field is an important exception. OCLC records can contain dozens of 029 fields. If there are too many 029 fields, , as Alma is unable to create the standard 035 field containing the OCLC number , so if too many 029 fields are present. The result is no future updates will overlay that bibliographic record.
To automatically delete 029 fields upon export:
In Connexion, go to Tools > Options
On the Export tab, click the “Field Export Options” button
In the “Fields to Delete -- Bibliographic Records” box, enter 029
Click “OK”, then “Apply” and “Close”
The 029 field must also be deleted from any OCLC records that are batch loaded.
Note: Fields 029, 936, 938, 984 will be deleted from daily OCLC record updates. Shared Import Profiles for NZ will also remove these fields.
Procedures in Alma
Deleting MARC Fields in OCLC Records
Action log
| Section | Point Person | Expected Completion Date | Last action taken | Next action required | |||
|---|---|---|---|---|---|---|---|
Articulate the need for the policy (background) | Cataloging Task Force |
| Policy needed to ensure removal of 029 fields from OCLC records. | To be discussed with TS Working Group. | |||
Finalize Policy Statement | Cataloging Task Force |
| Identify and create best practice recommendations |
| |||
Revised | Cataloging Task Force |
| |||||
Where applicable, identify and write up procedures in Alma | Cataloging Task Force |
| |