Question

Is there any checklist we can use, in order to test EasyActive CDI resources in our premium sandboxes? 

Answer

By default, the sandbox uses the same CDI key as your production environment.

If you wish to test CDI and avoid affecting the Production environment, you need to generate a separate CDI key for the sandbox environment. This will ensure that production data is not inadvertently published in the sandbox, which could disrupt the production environment. 

If you wish to test CDI in your PSB, please consider the following points:

1. The steps to register the CDI key for PSB are explained here: "Registering Institutions for Central Discovery Index". 

2. Please contact support if the job "Publish electronic records to Central Discovery Index" should run.

3. Configuration in the Institution Zone (IZ), when linked to a Network Zone (NZ):

• cdi_consortia_inheritance: defines whether the Institution Zone can inherit CDI records from the Network Zone. This parameter is found in: Configuration Menu > Resources > General > Other Settings.  Documentation is here: "Collaborative Networks (with a Network Zone and Institution Zones)"

• retrieve_services_from_NZ: defines whether the IZ inherits Link Resolver services from the Network Zone.  Found here: Configuration Menu > General > General Configuration > Other Settings. Documentation: "Configuring Other Settings (General)"

4. Sandbox Environment provisioning of the CDI Key is found in: Configuration > Discovery > Other > Central Index and proxy set-up

• .PPRD = Pre Production. This is a Production Key.
• .PSTG = Pre Staging. This is used for Sandbox Environments.

5. Please copy and store the CDI key for PSB outside of Alma. The sandbox refresh process will replace the sandbox key with the production one, necessitating a manual switch back to the correct key after each refresh. Click here to find the semiannual refresh dates: "Release and Maintenance Schedule". 

• Article last edited: 7-JAN-2026