Versions Compared

Key

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

...

Page Properties
label

Status

Status
colourYellow
titleIn progress

Scope

Test load

Description

Determine how MARCIVE records should be handled in the NZ

Decision

Owning group

TESLGTSELG

Approver

PPC

Stakeholders

R = TSELG
A = ILSDC, Resource Management FG
C = PPC, CDL Acquisitions, CDL in the NZ subgroup, RMFG
I = ILSDC

Decision-making process

Priority

Mandatory for go-live

Due date

17

Recommendation

SCP will use UCSD’s MARCIVE bibliographic records for electronic resources (not composite records) as a basefile base file for the entire system. The records will be loaded directly into the NZ along with several other SCP collections that have been outlined on this page: SCP, SFX, and related resource records handling for eResource records in NZ - TEST LOAD

Campuses do not need to migrate their TSELG suggests that, to the extent possible, campuses not migrate their non-composite e-resource MARCIVE records. If non-composite e-resource MARCIVE records but are not prohibited from migrating them for test loadneed to be migrated for any reason, they should not be migrated into the NZ. ILSDC can provide guidance on how to prevent records from coming into the NZ. Campuses can also choose to migrate only bibliographic records for tangible resources. The questions around processing updates (who will load files and how will holdings be set) will be explored during test loadtheir composite MARCIVE records and those can be added to the NZ but campuses should be aware that they will not be part of system-wide maintenance. RMFG will create import profiles and processing guidelines during test load, go-live and in the remaining months of Phase 4.

Reasoning

UCSD is able to identify their MARCIVE records and they are the easiest for SCP to use since they are in the same Millennium ILS. Purchasing a base file directly from MARCIVE is not only more expensive but actually creates more work for SCP since that file would have to be processed separately from the other SCP extracts and then incorporated into them for delivery to Ex Libris. Loading a base file after migration also creates a large workload for SCP and they will be extremely busy with cleanup and other new purchases. The decision to only use non-composite e-resource records was made because, while MARCIVE does use some “composite” records (records for print or microform resources with URLs added), SCP no longer uses those records and will not load them into the system. Most (all?) campuses have also already started switching away from composite records. In addition, Alma does not always handle composite records well in terms of search results for staff or users in Primo. Best practices dictate that only non-composite e-resource records should be used. Staff at UC libraries can request that GPO catalog the electronic version of a resource as they come across gaps in the collection.

...