Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

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:

TASKReferencesExamplesPriority

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]
66.151.7.192/28 [66.151.7.192-207]
74.217.12.128/27 [74.217.12.128-159]
66.151.14.129
64.74.237.229
64.74.237.233
64.74.237.221

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.The Incomplete Activation report can help with some of this. It is important that these are correct in SFX, if not, it will affect the updates to the Alma e-resource.


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 AlmaNote:  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:

Alma supports the ability to check the validity of the full-text URL before presenting it to the end user through the View It services menu. This functionality is only available for EBSCOhost Full-Text URLs.  The EBSCO Link Resolver Plugin performs external checks using an API that determines the most accurate available URL for the full text.  This is set up in your IZ.  It only works for those EBSCO databases you manage.  The plug in you set up has no impact on the shared  NZ EBSCO collections.  At this time,  it is unclear whether Jessica can set up a profile for the merged EBSCO collections in the NZ.  We still suggest you implement it if you have EBSCO collections in your IZ.

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 bXbX has already been configured in Primo Central for Primo. Recommendations appear in Primo results, not in Uresolver menu.
Informational

During the ULMS implementation, SDLC has set the following timelines:

Before April 30, 2017

  • All FY 16/17 Subscription Memos will be released.
  • SDLC will provide CPO values to campuses.

After April 30, 2017

  • Regarding year end add-on subscriptions and purchases, be aware that CPO values may not be captured during the ULMS migration and may need to be entered into the system manually.
  • No Trial Offers will expire during the ULMS implementation.  


July 2017 (FY 17/18) SDLC Renewal Update: 

SDLC has begun releasing Subscription Memos for fiscal year 2017/18.  

Subscription Memos released:

  • 17-01 Berg Fashion Library  
  • 17-02 Sage CQ Roll Call Weekly
  • 17-03 Elsevier EiVillage
  • 17-04 Mergent D&B/Intellect
  • 17-05 Oxford Grove Art Online
  • 17-06 Elsevier GeoBase

Subscription Memos to be released within the next few weeks:

  • EBSCO AnthroPlus, Chicano and AP Images
  • EBSCO Databases
  • Encyclopedia Britannica
  • CCC – Get it Now
  • IEEE
  • Lexis Nexis
  • NBC Learn
  • OCLC
  • OCLC Question Point
  • Oxford Databases
  • ProQuest Databases
  • ProQuest Pivot
  • Thomson Biosis

 

Campuses will receive Cash Posting Order’s (CPO’s) for the above listed renewals, after July 1, 2017

  • No labels