Versions Compared

Key

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

...

Stakeholder group

Impact

DISC

  • Campus representatives can provide feedback and recommendations for treatment for individual collections.

  • Consider impact of campus search scope and CDI

  • Can provide feedback on what information about the collections to convey to end-users.

ERES

  • Provides guidance on how to “link” the collection-level bibliographic records with the relevant collections in Alma to support local staff who work on:

    • access problems

    • Order information

    • licensing information

    • Analytics reports

SCP + CDL staff

  • SCP staff are responsible creating and maintaining the collection-level bibliographic records. Concern that Alma collection descriptive records are not acceptable for discovery, and work around might be necessary to create a general/parent/umbrella bibliographic record that would stand in for the combined individual modules.

  • CDL will continue to set up collection level records on multipart collections for the time being, as CDL determines what seems best for any given collection. If anything develops later with a SILS team or group’s decisions about procedures or best practices that causes us to change our workflows, CDL will review it then.

  • CDL, without guidance to date, has made best efforts in accordance with Proverb. It is better to act decisively and apologize for it later than to seek approval to act and risk delay, objections, etc.  A strategy might include re-evaluate CDL Tracking Spreadsheet. If CDL establishes a place of record to track all multi-series entries, should a communication system be developed to offer UC Library System members a way to submit recommendation or edits?

User Experience

Given Tier 1, 2 and 3 acquisitions models, e-collection records will have a different outcome, have varying models based on vendor, interactivity of records between IZ and NZ content, and other factors such as search scopes set up in Primo.

CKGs, Instruction and reference services

  • Campuses can use and coordinate data for multiple tools, such as LibGuides A-Z Database List or Primo Database search, so combined metadata management output affects ability and consistency in achieving reference and instructional goals.

  • Different subject disciplines use and reference resources differently, so having their expertise applied to multi-series e-collection entries can ensure naming conventions match names used in professional disciplines.

Background

E-collections in Alma are structured to support back-end management, and are may not support discovery. Collections containing multiple modules often have separate entries for each module, and Alma collection descriptive records have been described as ‘not acceptable for discovery,’ so from a cataloging standpoint, the action to follow Alma instructions to unsuppress the collection-level bibliographic records results in both metadata management and discovery problems. Requests are usually made by library colleagues outside of technical services and have a specific use case they are trying to fulfill. This type of environmental scan to develop use cases and test with display scenarios exceeds the scope of ERES expertise.

...