Page Comparison

Background

The CSU libraries provide a wide range of ebooks and other non-serial electronic resources, such as streaming video and audio. These resources may be paid for centrally or locally, shared widely or not at all. This document attempts to balance central needs for efficiency and coordination with unique local circumstances. 

Access and payment models

*DDA/PDA is an involved process and will be examined separately with Alma’s specific DDA functionality. This process contains some aspects of packages regarding record batches, but purchases can occur title-by-title; short-term loans may apply.

In the CSU system, these packages may be:

• Part of the ECC (negotiated centrally, paid for centrally, systemwide access)
  • Examples, purchased centrally:
    • The former “NetLibrary” package, now hosted in EBSCO ebooks.
    • The more recent systemwide DDA-triggered purchases, hosted on ebrary, myiLibrary, and EBL
  • Examples, subscribed centrally:
    • Safari Tech Books
    • Ebrary Academic Complete
• Opt-ins offered via SDLC (negotiated centrally, but paid for by each campus, local access only)
  • Examples, opt-ins:
    • ACLS Humanities Ebooks
    • Oxford Scholarship Online
• Locally purchased or subscribed (by each campus, outside SDLC, local access only)

Policy Statement

Collections purchased/subscribed centrally:

• If unique to the CSU (i.e. the Netlibrary and ebrary/EBL/myiLiibrary packages mentioned above), should be managed by creation of their electronic collections at the NZ level for sharing by all campuses.
• If standard packages, not unique to the CSU:
  • ebrary Academic Complete should be managed centrally by activating its CZ collection in the NZ. This is due to the package's large size and frequent changes in content.
  • DECISION PENDING RE SMALLER PACKAGES LIKE SAFARI Depending on analysis of CZ record currency and quality, options include:
    • • Active CZ collection in the NZ OR
      • Load records as an electronic collection at the NZ level for sharing (campuses would need to volunteer to maintain)

Collections negotiated centrally but opt-in at the campus level:

Best practice recommendations

If you are not going to use a CZ collection, create a Local Electronic Collection

Whenever possible, portfolios should be added to Local Electronic Collections. Even eresources that are not sold as collections (such as ebooks or streaming video titles purchased title-by-title) can be maintained more easily if they are in a Local Electronic Collection, as long as they are from the same provider, have the same license conditions, and share the same base url.

Local Electronic Collection Advantages

• Maintenance functionality in Alma is based on portfolios in collections rather than stand-alones
• Better display in Primo and Alma, with collection names
• Better reporting in Analytics
• Ability to maintain settings at collection level (proxy, activation dates for trials, etc.) and push them down to all portfolios

Procedures in Alma

TO BE DETERMINED

Action log