Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Compile an inventory of non-MARC metadata staffing and expertise at both Columbia and Cornell; compare current job assignments -- "metadata librarian" can mean very different things in different institutions. (deadline: April 10)
  2. Examine and evaluate reporting and decision-making structures at both institutions. (deadline: May 1)
  3. Compile an inventory of all policies, practices, and workflows involving non-MARC metadata activity at both institutions -- including systems and schemas. (deadline: May 15)
  4. Identify dependencies and limitations inherent in working with other functional areas at Columbia and Cornell, both within and beyond technical services. (deadline: May 29)
  5. If possible, establish baseline productivity numbers for activities and projects at each institution to allow for future assessment of potential changes and development associated with 2CUL TSI. (deadline: June 12)
  6. Recommendations regarding a work plan and critical issues to explore in Phase 2 of the group's assignment (deadline: July 25)

PHASE 2

Originally, the aim of the second stage of TSI was to begin the incremental integration of technical services workflows, practices, policies, and projects.  However, with with the change in direction for TSI in June 2014, the revised aim of the second stage of TSI is to pursue those collaborative projects and alliances that are most promising with regard to quality, productivity, improvement, and innovation.  Based  Based on the findings of the Non-MARC Metadata Working Group during Phase 1, this means:

  1. Perform an environmental scan of the current availability of a metadata capture and editing tool that would allow 2CUL to: (a) collaborate extensively on non-MARC projects, (b) facilitate alignment of non-MARC metadata practices, and (c) enhance the quality of jointly created non-MARC metadata.  If 2CUL decides to implement Alma in 2016, this scan should include a formal evaluation of that system's existing or planned capacity to address this need.  Submit written results of this work to the TSI JSMIN group

    Begin collaborative investigations and training of new and existing tools and standards for metadata creation and management, with the aim both to reduce net effort.

  2. Develop a proposal for review by the TSI JSMIN for

    a formal consulting network between the two institutions.  Solicit appropriate input from stakeholders outside of 2CUL technical services and incorporate tenets and guidelines from the forthcoming 2CUL governance agreement and any memoranda of understanding developed for 2CUL TSI in early 2014.
  3. Provide input for the creation of a space for shared TSI documentation.  Edit and package existing and new non-MARC metadata documentation for optimal use in this shared space (expected sometime in 2014), keeping in mind the eventual need to distinguish between 2CUL and locally specific guidelines.
  4. Begin a formal program of cross-training for new and existing standards between the two institutions.
  5. Begin collaborative investigations of new and existing tools and standards for metadata creation and management, with the aim both to reduce net effort and to align joint practices when appropriate

    an informal consulting network between the two institutions.

  6. Coordinate the programs of the Metadata Working Groups at both institutions to permit greater joint engagement in and broader scope for these programs

    .Maintain an inventory of relevant expertise, as needed

    .

  7. Provide assistance to the TSI Steering Committee in the form of feedback and, if

    necessary

    possible, data to measure the costs and benefits of

    all the preceding steps, plus any new 2CUL tasks or initiatives related to this charge.  This evaluation will guide future decisions about the practicality of long-term integration of non-MARC metadata functions and

    the collaborative initiatives.

  8. Communicate regularly with the 2CUL TSI Steering Committee, through the designated liaison with that group and/or through publicly posted meeting notes, reports, or other announcements.

The group is strongly advised to observe the Operating Principles for Technical Services Integration throughout its work.

...