Retaining and Deleting MARC Fields in OCLC Records
Â
Â
Document status | APPROVEDÂ Dec 9, 2016Â ;Â REVIEWEDÂ May 15, 2019 |
---|---|
Area covered | cataloging |
Prepared by | Cataloging Task Force |
Adapted from | Orbis Cascade Alliance Collaborative Technical Services Team |
Â
Background
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, as Alma is unable to create the standard 035 field containing the OCLC number if too many 029 fields are present. The result is no future updates will overlay that bibliographic record.
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 | Oct 24, 2016Â | Policy needed to ensure removal of 029 fields from OCLC records. Â | To be discussed with TS Working Group. Â |
Finalize Policy Statement | Cataloging Task Force | Nov 11, 2016Â | Â | Â |
Revised | Cataloging Task Force | Â Feb 2, 2017Â | Â | Â |
Where applicable, identify and write up procedures in Alma | Cataloging Task Force | Feb 2, 2017Â | Â | Â |
Â