Legend: NOT STARTED IN PROGRESS STALLED DECIDED
Recommendation
Reasoning
“Course restricted field” Ex Libris recommended standardizing this across the consortium but 2 Vanguard campuses already had conflicting data coming over in different fields. The group will assess any impacts on staff workflows and Primo for go-live
Brief level:
Working copy lock timeout:
9XX fields:
Background
CARLI guide: https://www.carli.illinois.edu/sites/files/i-share/documentation/CARLI_Alma_Config_form_Guide_Final.pdf
Dependencies
Any areas mandated or recommended by ExLibris
Questions to consider
ExLibris Recommends to leave as default:
Cataloging level available (should be FALSE)
Subfield separator ($$)
Match profiles (ExLibris has a recommended profile but this will be set in the NZ and filter down so campuses can leave whatever default comes through their pre-populated form)
Areas for standardization
Brief level (recommend 3)
Retrieve from NZ (True)
Authority names (ExL suggestion=LCNAMES)
Working copy lock timeout (recommend 1 hour)
System date format (MM/DD/YYYY)
there are only 2 options: MM/DD/YYYY and DD/MM/YYYY; the latter causes problems for Acquisitions
Course reserved field (agreed to use 969 already)
Areas that can stay fully local
Call number parsing
Authority usage (must select “local” if using any local authorities)
Barcodes
Metadata registry (only MARC21 is required, choose “Yes” and “Yes”)
Call number type
Use holdings form
Local field names
this is not the same as the standardization of the content of those fields, that decision is recorded here: (Test load) Local bibliographic data (5XX-9XX)
590: Label: Local public note (590)
690: Label: Local subject--Topic (690)
691: Label: Local subject--Geographic (691)
908: Label: Shared NZ processing note (908)
956: Label: Local URL (956)
970: Label: Local personal name (970)
973: Label: Local collection name (973)
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
|---|---|---|---|