- You cannot have both a standard sandbox and a premium sandbox simultaneously.
- The cloud sandbox environments are updated with the new Primo release two weeks before the general release to the production environments (refer to the exact release schedule published by Ex Libris).
- The configuration can be copied from your Primo production environment or copied to your Primo production environment using the export/import tools (see Primo Tools).
- For more details on working with your sandbox and Alma, see Alma Sandbox Environments.
- As part of an Alma premium sandbox refresh, you may need to publish some of your records for testing purposes to your Primo sandbox. Note that you can publish installments of sets that include up to 10,000 records.
- If you are working with a Primo standard sandbox, you can publish up to 100,000 records only in total (all published sets combined).
- Your Alma premium sandbox environment is a full replication of your Alma production environment. It includes all of your institution's configurations and records. Your Primo sandbox environment may have only a partial representation of your institution's records (depending on your Primo sandbox model). So you may have records in your Alma sandbox that are not in your Primo sandbox.
- To test discovery of specific Alma records, you can publish a select set of records (up to 10k) from the Alma premium sandbox to the Primo sandbox.
- Primo sandbox is configured to work with Alma premium sandbox, so ensure that Primo configuration export/import is not done between Primo sandbox and Primo production or vice versa (the target Primo environment would then be—at least initially—working with the wrong Alma environment). If this must be done, reset the Primo-defined Alma URLs to the correct Alma environment immediately afterward (see Linking Primo Sandbox to Alma Sandbox below) to avoid any cross-sandbox/production mishaps.
- In your Primo sandbox environment, ensure a single ILS API base URL entry for the relevant Alma environment (Alma production if you have Alma standard sandbox or Alma sandbox if you have Alma premium sandbox) exists. If not, update or add a mapping row to the OPAC using Primo – ILS API Configuration mapping table (Primo Home > Advanced Configuration > All Mapping Tables) that specifies a single row URL for the relevant Alma environment. For example:
API Base URL configuration for communication with the Alma environmentThis page should already contain a mapping row for your Alma production environment (defined by Ex Libris), so institutions working with Alma standard sandbox may not need to update this table. Institutions working with Alma premium sandbox will likely need to update the ILS API Base URL with the Alma sandbox URL to replace the Alma production URL.
- In your Primo sandbox environment, edit the Institution Wizard (Primo Home > Ongoing Configuration Wizards > Institution Wizard) and ensure that the Alma, RTA, and API Delivery Base URLs reference the correct Alma environment (Alma production URL for Alma standard sandbox or Alma sandbox URL for Alma premium sandbox). For more information, see Configuring the Primo Institution.
Alma URL references in the Primo Sandbox Institution Wizard
- Ensure that the authentication setup in your Primo sandbox is pointing to the appropriate Alma environment (Alma production URL for Alma standard sandbox or Alma sandbox URL for Alma premium sandbox). If you are still using PDS, your authentication remains directed at Alma production, and authentication relies on your existing users from Alma production. For other institutions using Primo's authentication manager, ensure the parameters ALMA_LOGIN_URL and USER_INFO_URL on the Login Profile page (Primo Home > Ongoing Configuration Wizards > User Authentication Wizard) refer to the correct Alma environment (Alma production URL for Alma standard sandbox or Alma sandbox URL for Alma premium sandbox).
For more information on Primo authentication setup, see Primo User Authentication
- Ensure that a pipe definition exists on the Primo sandbox that connects to the appropriate FTP location where Alma publishes its Primo data (see Defining a Pipe). If not, and you are unable to set up the relevant credentials in the Primo sandbox pipe, open a support case with the title Credentials needed for harvesting published Alma records to Primo sandbox. For Primo sandbox pipe definition setup for working with Alma premium sandbox, add an additional sub-directory in the pipe definition as indicated in step 3 of Linking Alma Premium Sandbox to Primo Sandbox.
- Deploy any changes in the Primo back office by entering and choosing the deploy option from Primo Home > Deploy and Utilities > Deploy All.
Perform the steps in Linking Primo Sandbox to Alma Sandbox to enable the ability to link your Alma Premium Sandbox to your Primo Sandbox.
- In your Alma premium sandbox environment, configure Alma to use the same Primo URLs that the Primo sandbox uses (in order to enable successful communication between Alma and Primo):
For information on these two parameters and their syntax, see Configuring Other Settings.
- Enter the URL of the Primo sandbox login page in the primo_pds_url parameter.
- Update the primo_service_page_url parameter with the Primo sandbox service page URL (which also enables Leganto and course-related communication with the Primo environment denoted).
- Ensure that:
- The values of the above Alma parameters are restored to the values of the Primo production URL when your Alma premium sandbox environment is refreshed by your Alma production environment. To re-enable your Alma premium sandbox to work with your Primo sandbox, reconfigure these parameters following a refresh.
- After an Alma premium sandbox refresh, the Primo sandbox may become slightly out of sync with the newly refreshed Alma sandbox data. You may choose to publish additional representative records from the Alma premium sandbox to the Primo premium sandbox for testing. Alma premium sandbox allows the publishing of up to 10,000 bibliographic records using the on-demand job Primo Republish Set of Titles.
- The Primo publishing profile on Alma sandbox is active and configured like it is in production (by default, after a premium sandbox refresh, it should be identical to production). Although you cannot schedule publishing on the Alma sandbox, you can publish up to 10K records using the on-demand job Primo Republish Set of Titles.
- On the Alma sandbox, all relevant FTP hostnames/IP addresses are in the FTP Include List mapping table (see Configuring Allowed S/FTP Connections During Testing).
In your Primo sandbox environment, change the FTP location of the pipe from which to import records. The Primo publishing profile on the Alma sandbox appends /sandbox onto the subdirectory of the target FTP server; this ensures that the Alma and Primo production and sandbox servers publish and harvest to/from different locations. For example, if your Alma production environment exports MARC 21 data to the directory a/b/c, the Alma sandbox environment exports to the directory a/b/c/sandbox. You must define the Primo pipe definition with the same directory location (with /sandbox) for harvesting those Alma premium sandbox published records. For more information on how to export records to Primo and to load the records into Primo, see the following articles:
- Create a set of titles on the Alma sandbox.
- Run the Primo Republish Set of Titles publishing profile on the Alma sandbox.
- Harvest to the Primo sandbox by running the pipe (for example, with pipe name: <customer_code>_ALMA_sandbox) on the Primo sandbox.
- Wait until the indexing and hotswapping are complete.
- Test the data.