...
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. | Importing Elsevier Holdings - Auto-load configuration in Alma | Note: SJSU contacted Elsevier Tech Support for the token. SJSU then set up the integration profile for Importing Elsevier Holdings in Alma. It's also possible to retrieve a token from Elsevier's Admintool (instructions). The token is good for 3 years. | Recommend |
Create a spreadsheet that contains the linking parameters from SFX. Linking Parameters (L/P) contain linking data for SFX targets. SFX Linking Parameters are the same as the Library-Specific Parameters in Alma. | The document SFX Target and Alma E-Collections Configuration Guide provides details for linking information (parser, parse params, etc) by vendors | The L/P (found in the linking information tab from the Edit Service link for electronic material) should migrate correctly from SFX to Alma but if not, then you can extract the details from your spreadsheet. | Optional |
EBSCO API: used in SFX to check if there is fulltext available from EBSCO before displaying the EBSCO link in the SFX menu. In Alma, this is found in the Integration Profiles. Have this ID ready for input into Alma post-migration. | Link Resolver Plugin in Integration Profiles under the General Configuration > External Systems. | The API User ID needed for Alma can be found in the Linking Parameters (L/P) in the EBSCO targets. | Optional |
SFX and bX | bX has already been configured in Primo Central for Primo. Recommendations appear in Primo results, not in Uresolver menu. | Informational |
...