Legend:
Status | ||
---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Page Properties | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
Recommendations
If they are concerned about losing data, campuses should consider copying 856 fields into a 9XX field of their choosing (between 950 and 999) or into the 856 of a holdings record
It is unclear whether copying data into a holding record has any more value than leaving it in the bib. UCLA may be able to test a small set of records but there is no obligation to choose a bib or holding field.
SCP will copy their 856 data into a 946 field
Campuses should document where 856 data has been copied
Generally, campuses should not remove their data from existing 856 fields prior to submitting files to Ex Libris
Reasoning:
Since there is some uncertainty around how 856 data will migrate and what utility there will be for having that data available, campuses can decide for themselves what their preferences are. Some campuses may not have any need for that data at all while others may have vital information in fields that will not necessarily translate cleanly into portfolios during p2e. The Vanguard should be used to test various methods and provide insights into future harmonization and best practices for go-live.
...
RM FG will consult with the Discovery FG to test the statement below that “existing 856 fields will not populate into Primo” since current experience with Primo at some Alma campuses varies. In addition whether those fields wind up in Primo will affect specific 856 data like finding aid links, etc.
Background
It is unclear exactly what 856 data will be retained in bibs during migration and certain subfields will not map into portfolios during the P2E process. Coverage data from $3 cannot be used to populate coverage data in portfolios
...
See other decision pages: Field Mapping Bibliographic records 9xx fields mapping for Vanguard 9XX fields SCP, SFX, and related resource records handling for eResource records in NZ - VANGUARD Non-9XX local data for the Vanguard
Questions to consider
Some campuses have started moving data already, is it worth creating 1 prescribed field?
Is there any advantage to using a 9XX in a bib over a holdings field
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
---|---|---|---|
Draft proposal brought to FG meeting | 6/23/20 | ||
Final decision sent to PPC for approval/routing to ILSDC | 6/26/20 | ||
Final decision routed to ILSDC |