Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties
Document status

Status
titleDRAFT

Area coveredERM
Lead AuthorChristopher Bulock
Co-authors

Table of Contents

Background

This best practice document applies to resources purchased and managed by individual campuses. Once electronic resources are activated within Alma, they need to be updated from time to time to reflect changes to access details and dates of availability. There is a cooperative element to this process due to the availability of information in the Community Zone and the likelihood of changes to affect multiple CSU campuses. However, centrally acquired resources will also be managed and updated centrally, so individual libraries will generally only be editing collection and portfolio level information that applies to their own library's IZ.

Policy Statement

These are the 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.

Best practice recommendations


Updating date coverage for portfolio

...

When editing a portfolio, enter the “Linking Information” tab. If you’re entering a journal level URL, you will probably need to use the Bulk::BULK parser, that is likely already selected. To update the link, enter a new parameter in the Parser Parameters (override) field with the syntax jkey=http://www.website.org

Image Modified

Even with some vendor-specific parsers, an update to the parser parameter may be fairly straightforward. For example, for an ABC-CLIO ebook portfolio using the ABC::ABC parser, the parameter is just the ISBN. If you notice a typo in the ISBN, you might just correct it using the Parser Parameters (override) field and the following syntax: bkey=9781440829918

...

The most important consideration with notes is how you will find and use them later on. When searching for portfolios or collections with these notes, it is strongly recommended that you used the advanced search rather than a simple search. This is because of the duplication of search indexes from portfolios and electronic collection services in the simple search drop down of fields. For example, when conducting a simple search for an electronic portfolio, you will likely see “internal description” appear twice, but there is no indication of whether it’s the portfolio internal description or the service internal description. However, the advanced search makes this distinction much clearer.

Simple search


Advanced Search


Procedures in Alma

Many of the topics here, as well as some others related to local collections (rather than thosed pulled from the CZ) are discussed in the Alma Ask an Expert videos on eResource Architecture and Concepts, Parts One and Two.

Action log


SectionPoint Person

Expected Completion Date

Last action takenNext action required

Articulate the need for the policy (background)

 

8/23/2016- ERM Task Force discussed the ERM policy and procedures outline and assign a policy to a task force member. Jessica assigned the policy and procedures for shared resources in Alma.


Draft for Shared Resources due September 30th. Send draft to Tech Service Working Group Leads//


Rough Draft for Shared Resource policies and procedures

Christopher Bulock

 

9/30/16 Rough draft is up now

ERM Task Force meet to discuss rough draft of policies and see if there is any feedback from the Working Group Leads


 



Send rough drafts of policies to Tech Services-discuss policies in Open Forum. Ask for feedback from working group.


 

 Link to Drafts were sent out to the Tech Services Working Group

ERM Task Force will go over the feedback received from the ULMS Team and the Tech Services Working Group. Meet with other TS Working Groups to discuss overlap of policies and procedures. ERM Task Force will meet  

Final "live" Draft for Shared Resources is due

 

Final drafts for policies is December 9th. All policies for all task forces are due this date.
ERM Task Force meet to discuss final drafts of polices and see if any feedback from the Working Group Leads

 




Tasks to be completed

  •  Type your task here, using "@" to assign to a user and "//" to select a due date