Readiness Evaluation

When you have completed the first three step of the Go VE process, refer to the following tools to make sure that you have not missed anything:

• Process tracking page – Make sure that all tasks leading up to going live have been completed and that there are no errors.

• Go live readiness checklist – Run the tasks on this checklist in your Primo VE environment.

• Customer checklist – We recommend that you prepare a list of tests for your unique features and needs.

When you are ready to Go Live, perform the following tasks:

1. Initiate the Go Live process at least three weeks prior to the requested Go Live date.

2. Configure the redirection of permalinks to Primo VE.

Initiating the Go Live Process

The Go Live phase of the process is initiated when you open a Support case to schedule the Go Live date. The case must be submitted at least three weeks prior to the requested Go Live date.
Prior to the Go Live date, you will receive a notification via your Support case letting you know that the Primo VE environment is ready for DNS simulation.

1. Open a Support case. The case should include the following information:

   • Subject: Go VE - Go Live {Alma institution code + institution name}

   • Description:

     • requested date for Go Live - this date must fall on a weekday (Monday – Thursday) or Sunday.

     • Primo institution code

     • Primo Front End domains in use

     • Primo VE domain that you intend to use after going live (such as Ex Libris CNAME or a local custom domain).

2. Once you have received notification that the DNS settings are in place, you will be able to simulate the redirection prior to the Go Live date. Note that this step is not mandatory, and will have no effect on the DNS switch itself. For full instructions, see DNS Switch Simulation.

Redirect Permalinks in Primo to Primo VE

Use the Primo Deep-Link Re-Direct Configuration page (Configuration Menu > Discovery > Other > Primo Deep-Link Re-Direct Configuration) to map the parameters used in Primo permalinks to the corresponding parameters used in Primo VE permalinks so that the system can redirect Primo permalinks to the correct page in Primo VE. For more information, see Configuring Redirection for Primo VE Deep Links.

On the Go Live day, a DNS switch will be executed to redirect traffic from your Primo base URL:

to your Primo VE base URL:

The following URL parameters will be translated as configured in the Primo Deep-Link Re-Direct Configuration table: vid, tab, search_scope, and docid (which will be transformed for records belonging to data sources defined in the configuration table). The DNS switch itself is seamless, and does not affect the performance of Primo.

If you are using a custom domain (a non-Ex Libris domain) to access the Primo Front End, the switch must be performed on your end by redirecting your domain to point to Primo VE instead of Primo.

If you are using an A record (which is a domain that is used by other institutions in your Primo installation—for example, https://primo-pmtna01.hosted.exlibrisgroup.com) instead of a CNAME (which is a domain that is uniquely used by your Primo institution), there will be no DNS switch. Your Primo VE environment will be prepared according to schedule, but the actual Go Live depends on you changing the library links to the Primo VE URL. In order to prevent patrons from accessing the old Primo after Go Live, perform the following actions in Primo once you switch to Primo VE: 

• Disable the silent login to Primo

• Hide the "sign in" buttons

• Change the "Sign in" banner message to something like the following:

  Library Search is moving to a new location. In order to get complete results and to request items, please go to XXXXX.