Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
See Best Practices for Decision Pages and Tags for groups
Legend:
Status
titlenot started
Status
colourYellow
titleIN PROGRESS
Status
colourRed
titleSTALLED
Status
colourGreen
titledecided
Page Properties

Status

Status
colourGreen
titledecided

Description

Sharing local e-resources practices

Decision summary

The E-resources subteam created a Slack Community Channel (#acquisitions-and-e-resources) as an opportunity to share resources, trade workflow adaptations among campuses, and raise concerns with ERM software or e-resource products. Biweekly ERES troubleshooting meetings also provide a space to communicate about issues of concern at each campus.

Owning group

ERES + Jeremy Whitt

Approver

ERES

Consulted

ERES

Informed

Decision-making process

Priority

Target decision date

Date decided

Recommendation

  • The eE-resources subteam recommended adding an ERES slack channel to the new SILS Community Channel, which . This channel was created on May 18, 2023. At the time that this issue was initially raised, no Community Slack channel to discuss e-resources existed.

  • A channel description was added to the Slack channel on 10/31/23 to encourage discussion of ERES topics in these areas.

  • At the 11/9/23 meeting, ERES agreed to change the status of this Work Plan to

    Status
    colourGreen
    titledecided
    , since the newly created Slack channel and biweekly ERES troubleshooting meetings fulfill the goal of providing a space to share local e-resources practices.

Background

  • Campuses had periodic questions about e-resources and thought it would be helpful if they could pose questions to an audience wider than ERES, and sought a forum to hold discussions outside of ERES meetings.

  • Based on the ERES https://uc-sils.atlassian.net/l/cp/jTdLfW75 a Slack channel could serve as a venue to document issues as they arose, in case issues were not mentioned at an ERES meeting. The channel was created with the understanding that it would facilitate conversation, but ERES members would not be responsible for answering questions.

Action Log

Action/Point Person

Notes

Status - Date of Discussion

Sarah Sheets (notes)

  • UCSB looking at AVON, http://Ancestry.com and ProQuest announces Clarivate products moving to ProQuest platform

  • UCR going live with Rialto in near future and currently testing orders

  • UCSD - Judy attending ERL and interest in creating series of status to manage work through the E-Resources Activation Task List

  • UCD assessing level of professional judgement required of staff to support Alma features including DARA, Alma Knowledgebase Updates and using software for E-Resources activation tasks - added complexity generated by network zone, Tier 1, 2, 3 analysis, and CDI.

  • UCM - as rep to UCOP Statistics, doing an environmental scan to try to identify different groups that might be trying to make the same types of assessments and how could this be more centralized (communication, data repository, etc??)

3-9-23

Michelle Polchow (notes)

  • UCSD - have periodic questions and would be helpful to have a wider audience to query for situations as they arise. Suggest a new ERES slack channel in the SILS Community so more input.

  • UCM - waiting on NZ task force for direction

  • UCB - also look forward to acquisitions standardization from NZ, having problems with new orders and wrinkles that make it problematic to fit into Alma. Also endorse idea to have open community slack channel ACQ/ERES.

  • UCLA - problem with ProQuest website, when you display “All databases” the historical newspaper titles are displaying duplicates. Would fixing this end up blocking access, if platform has odd way of turning these on?

  • UCD - implemented a ‘journal title transfer’ workflow as intermediary stop-gap when CDL package loses a title, but publication remains locally important.

5-4-23