| Policy | Description | Status |
|---|
| There are several functional implications related to the choice of Primary ID for Alma, particularly with regard to Shibboleth. This document outlines the rationale for campuses to choose, when possible the Employee ID (calstateEduPersonEmplID) from PeopleSoft as the Primary Identifier for External (SIS / PeopleSoft) loaded patrons. | |
| WorldCat (OCLC) Search External Resources for Network Zone Configuration | In order to use the "Search External Resources" function in the Alma Metadata Editor in the Network Zone, the external search profile must be set up in the Network Zone, which then makes the profile available to each institution. The NZ configuration is documented here for reference. Optionally, each institution can set up local credentials for using the Search External Resources function for importing records directly to their Institution Zone via Search External Resources. | |
| OCLC Connexion - Alma Export Integration for Network Zone | In order for records to be exported from Connexion into the Network Zone (NZ), there must be an Integration Profile set up in the Network Zone instance. Each institution then must add a Gateway Export in Connexion using the NZ credentials to enable export and overlay of records in the Network Zone. This will mean that all institutions across the CSU will be using the same match and merge methods, normalization, and management tags, which are set in the NZ Instance of Alma. This page will document the settings used in the NZ instanced of Alma. Optionally, an institution may choose to configure an OCLC Connexion Integration Profile in Alma that will enable the export of records from Connexion directly to their Institution Zone (IZ). | |
| Alma Daily OCLC Bib Record Updates & OCLC WorldShare Collection Manager | A policy / procedure document of the Tech Services Working Group Leads, with input from the joint Systems / Tech Services Working Group regarding import profiles used for daily bib updates. | |
| Shared Import Profiles / Normalization Rules Naming Conventions | Outlines naming convention best practices to reduce confusion when sharing import profiles and normalization rules with the network zone. | |
| To avoid this imprecise matching method, the recommendation is to use "com.exlibris.repository.mms.match.uniqueOCLC" because these records are being imported from OCLC and have a OCLC number and therefore should be matched by unique OCLC identifier. The match method is set at each campus' instance of Alma. | |
| Recommended Merge Methods | Recommended merge methods for working with the Network Zone. | |
| Network Zone Normalization | The current normalization process, CSU Remove 029,938,948 removes the 029, 938 and 948 Marc fields from the NZ record. The 029 is removed because it is a vendor control number and serves no function in Alma. Futhermore, the Orbis Cascade Alliance found that numerous 029 fields caused problems with record processing. The 938 and 948 Marc fields are also vendor-specific data with no function in Alma. | |
| Brief Record Level Configuration | This document describes the current configuration and default Brief Record Level rule being used in the CSU NZ account. | |
| Alma Letters Central Repository | While we understand that everyone has differing ideas of what their letters should look like, we recommend that everyone use this repository for help in editing their letters as it will provide a more cohesive look and feel for all CSU Libraries. This will make it easier for the group to troubleshoot any potential issues and provide resources for those who are not comfortable editing the letters on their own. | |
| Alma and Bursar Integration for Exchange of User Fine/Fee Data | Some CSU libraries export user fine/fee data to campus bursar systems. Creating an automated process allows for greater efficiency and provides the opportunity for integration of online payment through a campus payment processing system. | |
| Illiad Account Registration for New Borrowers | In order for the Illiad / Alma plugin to work, the Illiad user account must match the Primary Identifier in Alma (or at minimimum must map to a designated identifier in Alma). | |
| Illiad NCIP Plug-in Set Up Procedure | A description of best practices for installing and configuring the ILLiad NCIP plugin for integration with Alma. | |