(Go-live and beyond) Migrating/managing local Open Access (OA) bibliographic records
Legend: not started IN PROGRESS STALLED decided
Status | decided |
---|---|
Scope | GO-LIVE and beyond |
Description | Decide whether to standardize campus practices around adding 506 notes for OA and whether to add 856 $7 data to OA links |
Decision | See below |
Owning group | RMFG |
Approver | PPC |
Stakeholders | R = RMFG |
Decision-making process |
|
Priority | Medium |
Due date | Mar 30, 2020 |
Recommendation
For 506 fields: post-migration campuses are strongly encouraged to add the standard Alma 506 field for OA to records in Alma during the course of regular cataloging to any bibliographic record where at least one portfolio is for an Open Access version of the resource. Campuses do not need to add this field retroactively (but can if they prefer).
Alma 506 field for OA: 506 0_ $f Unrestricted online access $2 star
For 856 $7: Campuses should continue their current local practice, this will not be standardized for migration
RMFG should also consider drafting an enhancement request that would use portfolio information to generate the OA icon instead of information in bibliographic records
Reasoning
Since there are so many open questions around how to manage OA resources in Alma, including possibly using CDI, RMFG did not feel the need to standardize the use of the relatively new 856 $7 in bibliographic records. The group got strong feedback from Discovery that it’s useful to have the OA indicator show up in Primo any time at least one portfolio associated with a title is OA and so RMFG agreed that campuses should be encouraged to do that in order to keep practices consistent without creating overwhelming need for pre-migration cleanup. One concern that RMFG had is that the 506 fields violate certain national cataloging standards and are also inconsistent with the notion of using one bibliographic record with multiple portfolios. It would be more useful if Primo generated the OA indicator from portfolio information but since that will not be changed prior to migration, the group recommended that RMFG draft an enhancement request to send through the Idea Exchange.
Background
Dependencies
PSELG decision: CDI to manage OA resources (Implementation+Post-live)
Questions to consider
Are local e-resources visible to other campuses via Primo? Can they be?
How difficult is it to add the OA 506 field after migration?
When should it be added?
What about hybrid OA/licensed items?
Should 856 fields for OA materials be retained?
Input from Discovery
Pending decisions from PSELG
Mixed practice over time, possibly need to make a decision with a “start date”
CZ bibs are harder to edit in batch
Differing ability to find OA resources in current ILS
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
---|---|---|---|
RMFG vote | 3/30/21 |
| Done |
Routed to PPC | 3/31/21 |
| Done |
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu