Executive Summary
2CUL TSI Non-MARC Metadata Working Group
Phase 1 Report
2013 July 30
...
One of the non-MARC FTE at Columbia is primarily devoted to non-MARC metadata creation and remediation, the other mostly focuses on strategizing, consultations, crosswalking, as well as staff education and training. On rare occasions, other catalogers may work with non-MARC metadata if subject or language expertise are needed. At Cornell, non-MARC metadata work focuses on consultative services and design strategy, with some VRA Core cataloging for the images-for-teaching collection and occasional science or special collections metadata generation. The Columbia non-MARC staff work also with MARC metadata while non-MARC staff at Cornell have little interaction with MARC metadata.unmigrated-wiki-markup
For more information on the staffing and expertise, see the full report: \[provide link to the full document once available in Confluence\]report: Non-MARC metadata staffing and expertise
Examine and evaluate reporting and decision-making structures at both institutions
Administrative reporting structures and functional reporting structures vary significantly at the 2CUL institutions. Non-MARC metadata staff at each institution report administratively within their technical services units; however, functional reporting and decision-making structures vary on a project-level or initiative-level and rarely occur within technical services for the Metadata Librarians / Coordinator. For non-"Librarian" or non-"Coordinator" staff members, functional reporting and decision-making structures usually align with the Metadata Librarian / Coordinator overseeing the project.unmigrated-wiki-markup
For more information on reporting and decision-making structures, see the full report: \[provide link to the full document once available in Confluence\]
Identify dependencies and limitations inherent in working with other functional areas at Columbia and Cornell, both within and beyond technical services
Non-MARC metadata projects at both 2CUL institutions have significant dependencies outside of their respective technical services departments, which closely align with the functional reporting structures described above. Limitations often entail technical support and development, including programming (both institutions) and desktop administrative rights (Columbia).
...