Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Legend:
Status
titlenot started
Status
colourYellow
titleIN PROGRESS
Status
colourRed
titleSTALLED
Status
colourGreen
titledecided
Page Properties
label

Status

Status
colourGreen
titledecided

Scope

Go-live

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
A = ILSDC, AEFG
C = ILSDC
I = PPC, ILSDC

Decision-making process

Due date

Recommendations

  • For go-live all campuses (minus CDL) should copy their data into a 956 field if at all possible and they are concerned about losing it.

  • 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

  • For NZ-linked records, RMFG will request that CDL remove 856 40 fields on or shortly after August 15 (to allow for data checking and the other stuff we have to do for go-live before Ex Libris considers us migrated)

  • For NZ-linked records, RMFG will check with campuses on September 1 about the status of their 846 41 fields and will request that CDL remove them from any campuses that are ready (based on “originating system ID”)

  • For NZ-linked records, RMFG will request that CDL remove most remaining 856 41 fields starting September 15. UC Santa Barbara has requested permission to retain 856 41 links for some specific situations in which they have non-restricted links to Special Collections content in 856 41 fields.

  • 856 42 fields do not need to be removed after migration, campuses can choose which ones to retain

    • Campuses should be aware that 856 42 fields can be lost during NZ build/matching like all other non-local data.

  • 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. Portfolios for those fields would have to be generated after migration.

  • AEFG concurs with this recommendation for P2E with respect to the 856 42, and advises local discretion regarding using the 856 42 for finding aids and other applications. The option of creating portfolios for finding aids post-migration is possible, and AEFG would recommend ensuring that these do not unduly interfere with other e-inventory management or discovery outcomes in Primo (e.g., an indicator that item is "Available Online"). Creating a designated local e-collection could assist in managing these portfolios. AEFG is considering additional approaches for this functionality to be out of scope for preparing migration data for go-live and immediate post-go-live, and will likely entail cross-functional discussion after the end of Phase 4.

  • Suppressed bibs with 856 fields can be sent through P2E if the portfolio information is needed at a campus but need to be left out of the NZ.

...

See other decision pages: Bibliographic records 9xx fields mapping for Vanguard SCP, SFX, and related resource records handling for eResource records in NZ - VANGUARD Non-9XX local data for the Vanguard Local 856 fields in the Vanguar

Action Log

Action/Point Person

Expected Completion Date

Notes

Status

FG vote

3/30/21

Done

Final decision sent to PPC for approval/routing to ILSDC

3/31/21

Final decision routed to ILSDC

4/2/21