Timeline:
SFX Chancellor's instance freeze: May 5, 2017. All updates to the Chancellor's instance will stop, there will be no new targets added, no targets deactivated, no title list updates, no local changes to thresholds or parse params.
Data will be exported from the Chancellor's instance the week of May 7, 2017.
Group 1 local SFX instance data will be exported the weekend of May 6, 2017. Do not make any changes to local SFX instance after May 5, 2017.
Group 2 local SFX instance data will be exported the weekend of May 13, 2017. Do not make any changes to the local SFX instance after May 12, 2017.
Group 3 local SFX instance data will be exported the weekend of May 20, 2017. Do not make any change to the local SFX instance after May 19, 2017.
Recommended Tasks for SFX before freeze:
TASK | References | Examples | Priority |
---|---|---|---|
Enable Alma IPs / IP ranges to allow Alma access to and from your institution. Please NOTE, the IP ranges are in CIDR notation. | Technical Requirements for Alma and Primo implementation for more information about the IP ranges | In North America (refers to the Ex Libris Chicago data center): 66.151.7.128/26 [66.151.7.128-191] | Essential |
Check the list of merged targets and request changes to the list, merge or unmerge a target from the Chancellor's instance. | Essential | ||
Run Incomplete Activation report on server to see if any clean up is needed in the local SFX instance. If you do not have access to the server-side on SFX, please ask Jessica for the report. | Recommend | ||
Check local targets for correct proxy activation, auto-update and auto-activate setting. | Recommend | ||
Have Elsevier Auto-Update token ready. If using Elsevier auto-load target in SFX, locate token on the server-side and use in Elsevier auto-load in Alma. | Elsevier Auto-load configuration in Alma | Recommend |