Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page Properties
label

Status

Status
colourYellowGreen
titlein progressDEcided

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

Decision-making process

Due date

...

  • For test load all campuses (minus SCPCDL) 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. For During test load RMFG will look at standardizing 856 text for OA links.

  • 856 42 fields do not need to be removed after migration

  • Suppressed bibs with 856 fields can be sent through P2E if the portfolio information is needed at a campus

  • 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.

...