Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Attendees

Erica Zhang (co-chair)

Carla Arbagey (co-chair)

Yoko Kudo

Jared Campbell

Lisa Mackinder

Nicole Arnold

Rebecca Culbertson

Regrets:

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

1

Gather & Announcements

Assemble as a group and share info

5

Team

  • May 16th meeting

Okay to skip this meeting; use the time slot for others to discuss on Slack if needed

2

OA activation/activity spreadsheet

Determine if we need any additional information

5

All

Share with RM during their meeting today

Yoko Kudo Will share the spreadsheet with RM

3

Work plan goal discussion: Provide recommendations for models of work

Continue discussion of models of work for OARM; start to develop recommended workflows to propose to stakeholders

40

Carla/All

Notes:

  • Becky: have SCP continue to process collections and single journals

    • Is there a capacity issue? SCP will still have representation in any group/workflow we recommend

  • Proposed group adds flexibility for campuses or SCP to process collections

  • How to handle transformative agreements with an OA component?

  • Group should include liaising with those working in analytics so we can assess transformative agreements - assessment is done only for content with a paid component

  • JSC provides guidance on priority of processing the OA resources they approve

  • How does this group make a determination to activate a large collection?

4

Report back from SILS groups

Understand what other SILS groups and campuses are doing in relation to OA

3

All

5

Wrap up & Homework

Review actions and decisions

2

Team

6

Parking Lot

Capture important topics for future discussion

Team

  • How to find items that are OA but have slipped thru the cracks, not being labeled OA?

  • Something coming from Discovery group

  • Another area is to rethink JSC and whether they want to continue approval role.

  • Considering ongoing maintenance of OA in Alma/Primo - who is responsible?

    • Because OA would be in the NZ, most maintenance requests would go through CDL Helpline - where in CDL would these requests go?

      • From CDL: With broken links, Helpline will route the issue to the CDL Acq staff, in some cases we may loop in SCP, to review what needs to be done in Alma.

      • For troubleshooting OA:

        With collections like ROAD, DOAJ, or Free e-Journals, those are turned on in bulk with thousands of titles -- and the titles are not individually requested by users either. If we can’t immediately find a correct URL or the user doesn’t suggest one when reporting the issue, we will just deactivate the portfolio. In short, not a lot of time is spent trying to fix a problem with one of those types of collections. With a collection like this, the titles are all coming from individual publishers and it will more often be the case that there is a problem with a single title and not the full collection, such as a small OA website disappearing from the internet.

        If there is a problem with an entire CZ-collection, we can report it to Ex Libris to resolve. 

        For OA collections maintained locally, SCP may batch update the URLs too.  

        Of course there are also OA materials that we pay to support. Generally speaking, those would be treated as if they are paid collections and we would work with the publisher to resolve any issues there.

  • Statistics/Resource Management as related to the workflow

  • Related to CZ Updates Task List: Consider a cleanup project to compile a list of open access collections in the IZ that are already activated in the NZ. Deactivate and delete those collections from the IZ. This would help with maintenance since we would not have to sift through redundant data if we decided to use the CZ updates task list.

  • “OA cooperative”

  • Solving the missing OA links issue: determine what is within our scope:

    • From Becky: UCSD’s Serials Cataloging Group has the following info as to how UCSD is handling this. Please read the following especially the Content Corner Update:

      1. “Are we doing anything with the Community Zone Updates Task List at the moment? When a portfolio is deleted from a community-managed CZ collection, the IZ copy of the portfolio is deactivated and unlinked from the CZ and becomes a "local" portfolio. We currently have no way of being notified of these changes except via targeted periodic sweeps. Using the CZ updates task list would give us a list of updates that directly affect our resources.  Who would review the updates, how often, etc.? Who would take care of cleanup?”

      a.      Content corner: 2022 Alma CKB Release Notes: September-December

      b.     [Moved to Parking Lot]

      c.      Who would review the list of the updates and do the cleanup? TBD.

7

Total

60/60

  • No labels