...
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
Recommendations
...
Generally, campuses should manage all of their records from within their own IZ, including NZ-linked bibs with a few exceptions. Use cases should be developed over the course of the Vanguard.
Generally, records should be imported into the NZ (through a campus IZ) by default unless they belong to a category expressly prohibited from being added to the NZ. See Bibliographic records to leave out of the Vanguard NZ Different import profiles should be used to ensure different categories of records are handled appropriately. RMFG will work to develop some of these import profiles (and related rules) to address shared import scenarios and concerns.
For Vanguard there is no reason to use an “enforced network zone.”
...
SCP local fields should be protected during overlay since import profiles should not erase local data.
...
Campus catalogers should not delete CDL/SCP bibs. Most cohort members will not have permissions that even allow deletion of NZ bibs and can avoid doing so by checking the 930 field in the NZ for SCP informationAlma has several layers of protection in place to prevent bibs with inventory from being deleted. RMFG can discuss further as examples turn up in the Vanguard.
Background
ExLibris documentation: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/100Managing_Multiple_Institutions_Using_a_Network_Zone/03_Managing_Records_in_Consortia/010Network-Managed_Records_in_a_Network_Zone)
...