(Test load) Local 856 bibliographic data
Legend: not started IN PROGRESS STALLED decided
Status | DEcided |
|---|---|
Description | Determine whether campuses should copy 856 data in their bibliographic records into another field/record for future reference and what to do with different types of 856 field after migration |
Decision | See below |
Owning group | Resource Management FG |
Approver | PPC |
Stakeholders | R = Resource Management IG |
Decision-making process |
|
Due date | Oct 13, 2020 |
Recommendations
For test load all campuses (minus CDL) should copy their data into a 956 field if at all possible. If a 956 field does not work, use any 9xx field in the 950-999 range. RMFG would like to standardize this for cutover if at all possible.
SCP will copy their 856 data into a 946 field
Links in 956 fields can be made actionable in Primo using html tags.
Generally, campuses should not remove their data from existing 856 fields prior to submitting files to Ex Libris
856 40/41 fields that can be easily identified as restricted to a given campus should be removed as soon as possible after migration. Other types of 856 40/41 can be examined over time. Pre-migration: campuses should consistently identify restricted content in their 856 fields. During test load RMFG will look at standardizing 856 text for OA links.
856 42 fields do not need to be removed after migration
There is no prohibition or prescription around creating portfolios out of finding aids but bibliographic records that only have 856 42 fields (and no other 856 fields) should not be sent through P2E.
Suppressed bibs with 856 fields can be sent through P2E if the portfolio information is needed at a campus
Reasoning:
856 fields are needed during the P2E process to generate portfolios. However, they also risk being wiped out during NZ linking and so campuses should copy that data to a local field to keep it safe. The 956 field is set up in OCLC to be a local e-resource field already. RMFG would like to standardize this for cutover but recognizes that non-VG campuses may not be 100% sure if the 956 will work for them. Since a lot of campuses have locally cataloged OA resources and since Primo will not make those local portfolios visible to other campuses, the 856 links for OA resources should stay in the records after migration. Since 856 42 fields contain finding aids and other resources that campuses want to keep, they do not need to be deleted after migration.
Background
From ExLibris CDL Q&A 6/16/2020: migrated bibs will retain 856 fields so long as the bib is not overlaid. This also means it is likely that IZ bibs will lose their 856 fields if the bib matches an NZ record. 856 fields also do not populate Primo, all links com from the portfolios created during migration.
ExLibris documentation: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/070Alma-Summon_Integration/050Display_Configuration/030Managing_Display_and_Local_Fields
See other decision pages: https://uc-sils.atlassian.net/wiki/spaces/RMF/pages/510132580 https://uc-sils.atlassian.net/wiki/spaces/PPC/pages/493814340 https://uc-sils.atlassian.net/wiki/spaces/RMF/pages/521437842 Local 856 fields in the Vanguar
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
|---|---|---|---|
FG vote | 10/13/20 |
|
|
Final decision sent to PPC for approval/routing to ILSDC | 10/13/20 |
|
|
Final decision routed to ILSDC | 10/16/20 |
|
|
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu