This section contains the following topics:
- Network-Managed Records in a Network Zone
- Repository Search when Using a Network Zone
- External System Search when Using a Network Zone
- Creating Import Profile Templates in the Network Zone
- Deleting Unused Bibliographic Records in the Network Zone
- Managing Representation Label Generation Rules Using a Network Zone
- Combining Institution and Network Zone Search Results
- Configuring Distributed Access to Electronic Resources from the Network Zone
Additional resource management features for collaborative networks include:
For videos describing cataloging in a Network Zone, see:
- See Cataloging Privileges for information about cataloging permission levels and any special considerations for the Network Zone.
- To create a Network Zone authority record, edit a Network Zone record and derive the authority record from it. For more information, see Deriving an Authority Record from a Bibliographic Record.
- Holdings are linked to a bibliographic record. When relinking holdings, you can select to relink the holdings to a Network Zone bibliographic record. See Moving Holdings Between Bibliographic Holdings (Relinking). Similarly for standalone portfolios; see Linking a Portfolio to a Different Record.
- When searching external resources, the list of available external search resources reflects those that are enabled in the Network Zone. See Searching External Resources.
- Importing: When checking whether to delete records during match/overlay, the record cannot be deleted if it is linked to another record/another record links to it. In addition, one of the options for handling merge/overlay is to unlink the records (leaving copies in both the institution and the Network Zone). See Managing Import Profiles.
- Publishing (see also Publishing Bibliographic Records to Primo When Working with a Network Zone):
- When you export bibliographic records from an Alma institution (or use Alma general publishing or an API GET bib), Alma returns the MMS ID of the institution’s record in the MARC 001 field. In addition, Alma returns the associated MMS ID from the Community Zone and/or Network Zone in a MARC 035 field (when they exist). See Exporting Metadata.
- A Link Resolver Plugin integration profile (to check the validity of EBSCOhost Full-Text URLs) must be created for the Network Zone and for all the member institutions. See Configuring the Link Resolver Plugin for Checking EBSCOhost Full-Text URLs.
- When configuring a Z39.50 integration profile, you can include the member institutions at which resources are available. See Z39.50 Search.
- Publishing to OCLC is processed at the local institution level since this process is used to expose institutions' physical holdings. Each institution in a collaborative network determines how bibliographic and holdings records are published based on their requirements, regardless of any links to corresponding records in the Network Zone. This means that the management tag – "Export to WorldCat" is managed by each institution, and is not controlled by the Network. Changes to the Network Zone, such as adding new bibliographic records, are independent of each institution’s record management and OCLC processing. Publishing to OCLC, whether or not in a collaborative network, is determined and processed as described in When Records are Exported.
- When publishing to Google Scholar in a collaborative network, the export process must be run at the Network Zone the day before it is run at each member institution. The process includes the ability to configure parameters for groups of libraries and campuses. For more information, see Adding a Profile for a Multicampus Environment.