Versions Compared

Key

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


There are three models of e-resource acquisitions and management available for Alma:

...

Reviewed and Revised by ERM CommitteeAugust 15, 2019


Table of ContentsIn-Depth Articles
Table of Contents
Child pages (Children Display)

Introduction

  • Electronic resources are managed very differently than physical resources in Alma. While physical items rely on item records to provide access and availability information, Electronic Portfolios are used to manage this information for electronic resources.
  • The IZ, NZ, and CZ also play very different roles with electronic resources compared to physical items. Electronic Collections and Portfolios will generally only reside in the NZ for centrally purchased or negotiated resources.
  • For resources that are purchased individually, Electronic Collections and Portfolios will reside in the IZ, even if several different CSU campuses own the resources.
  • Additionally, while some localization may occur, the CZ will be the source for most Electronic Collection and Portfolio information.

Best Practice for Electronic Resource Management

These documents provide best practices and procedures for selecting and activating new e-Resources in the Institution Zone (IZ) as it relates to IZ: Local Only.   These resources will continue to be locally acquired, licensed, and managed by the individual libraries.  SDLC and the Electronic Resources NZ administrator will activate, maintain, and in some cases, order e-resources that will be shared by some or all of the libraries in the NZ.  These procedures and best practices are for Network Zone - ECC and Network Zone - Opt-in resource management and acquisitions in the NZ admin instance.  Please Note:  E-Books and Media will have a different policy.

These are also best practices for maintaining and updating e-resources and portfolios that are already activated in Alma. This would be for updating date thresholds, activating or removing portfolios, updating parse parameters (jkeys/bkeys/URLs) and updating linking parameters.

Often it is necessary to make local changes to linking and availability information for e-resources when the information from the community zone is either inaccurate or does not match local details. While this localization is sometimes required, always keep in mind that updates to the CZ information may come later, so be sure to look carefully at update notes when localized information is involved.

When discussing electronic resource management, it’s important to keep in mind the types acquisitions available, local IZ and NZ:

  • Institution Zone: Local Only
    The local acquisition, licensing, and e-resource management by the individual libraries This model is only for the IZ and will not be used for shared acquisitions. Libraries will continue to manage acquisitions of their own e-collections in the IZ.  
  • Model 2Network Zone: ECC (Central Only)
    The centralized acquisition, licensing, and e-resource management of the ECC e-resources in the NZ. The Chancellor's Office will manage the acquisition and payment for the e-collections included in the ECC. 
  • Model 3Network Zone: Opt-ins (Mixed Central & Local).
    The centralized negotiation and management of the Opt-in e-resources in the NZ and local acquisitions by libraries in the IZ. License terms and fees are negotiated by the Chancellor's office and purchasing and invoice processing is done by the individual libraries. Libraries will need to create a vendor for the Chancellor's Office in the IZ for the Opt-in e-collections. The library will use the CO as a vendor to pay for the Opt-in resource. 
Resource Acquisition and Activation 
TitleDescriptionStatusStatus
OpenURL, Proxy, Discovery Interface Display Logic, and Troubleshooting in the IZFinal
E-Model 1, Local only: Practice recommendations.Draft
Maintaining and Updating Active E-ResourcesModel 1, Local only: Practice recommendations.Draft
OpenURL, Troubleshooting, and Display Logic/GESModel 1, Local only: Practice recommendations.Draft
License term field recommendations and Collection Development 
Draft
Shared E-Resources (ECC & Opt-Ins)

Models 2 & 3: Instances where SDLC and the NZ administrator will set up and maintain shared e-resources. Includes 4 sub-sections:

Draft
E-Books and MediaModels 1-3: Policy and best practice recommendations for handling non-serial electronic resource records.DraftBooks and MediaFinal


Electronic Collections: The following example illustrates a single title that is offered by two vendors. (ERM)

Physical Record: The following example illustrates an ongoing serial with three issues with holdings in Periodicals. (Cataloging)

Image Added

Image Added

Workflow of Catalog items and ERM items:

Catalog:

  • OCLC imported to NZ. Master Record is in the NZ.
  • CSU-wide library catalog is in the NZ.
  • Local fields, holdings and items, located in the IZ.
  • NZ and IZ records linked.

ERM:

  • NZ linked to the CZ for ECC/Opt-in e-collections.
  • IZ linked to the CZ for local subscriptions to e-collections.
  • NZ and IZ e-collections are not linked. Shared e-collections will not appear in the IZ.
    • There is an option to display subscribed ECC/Opt-it collections, residing in the NZ, to appear in the IZ.  Combined Search Results will display subscribed NZ collections in the IZ tab.
  • Combined Search Results in IZImage Added


Image Added

Related Policies

Acquisitions:  Ordering using the Alma Network Zone
TitleDescriptionStatus
Tech Services: Provider-Neutral Records & Use of Database-Level RecordsRecommends the use of Provider-Neutral records for electronic resources to eliminate proliferation of records describing essentially the same content.Draft

Status
colourGreen
titleApproved

Supplemental Information

ERM Best Practices, Policies and Procedures OUTLINE (Jessica's notes.)

Policy and Procedure FORMAT

ERM Dates:

September 30th: Rough drafts for Policy, Procedures and Best Practices due

September 30th: Send to Tech Services Working Group Leads for feedback

October 5th: ERM Task Force meets to discuss feedback -send out to Tech Services

October 6th: Discuss rough drafts during Tech Services open forum

November 8th: ERM Task Force meeting to discuss feedback for policies and procedures

December 2nd: “Final” working drafts due

December 2nd: Send final drafts to Tech Services Working Group Leads for feedback

December 6th: ERM Task Force meets to discuss final drafts -send out to Tech Services

December 8th: Discuss final drafts during Tech Services Open Forum