There are two lists for testing Full Text e-resources migrated from SFX to Alma.
- The Task List includes includes items for e-resources that we know do not migrate from SFX to Alma and will need to be set up post-migration.
- The Check List includes items that should migrate from SFX to Alma but need testing to ensure the e-resources migrated correctly and are functional.
- Link Resolver Redirect URLs
- SFX Readiness includes information and guidelines for preparing SFX for migration to Alma. This will make the post-migration Task and Check lists faster to complete.
- Alma/Primo Pre Go-Live Task List Look at this list to be sure the migration is as clean as possible to speed up the post-migration lists.
Each lists has a Reference column with links to documentation, instructions or testing materials that can be used for the post-migration checks and tasks. Some of this information is available on the wiki under the ERM Task Force page, in the Alma ERM Resources section. Reminder that FULL TEXT SFX data was migrated at the end of March, any target or portfolio changes made to SFX after March will not be reflected in Alma.
Please use to test your Institutional Zone (IZ) and the Network Zone (NZ). Your inherited/merged FULL TEXT resources e-collections will only appear in the NZ, shared resources will not NOT appear in the IZ.
*Local SFX e-resources => IZ
*Inherited/Merged FULL TEXT e-resources (normally found in the SFX Chancellor's instance) => NZ (AVAILABLE FOR=electronic collection HELD BY=migrate ILS record)
*Not sure why some records landed where they did? Check Mallory's Migration Decision Tree diagram shows where records migrated.
*The Task Force will create finalized lists to be used for Go-Live from these two forms.
*Please return these two forms by July 29th, 2016.
We are asking libraries to fill out the lists and return both lists to the ERM Task Force chairs:
Jessica Hartwigsen and Stacy Magedanz
Check List: http://tinyurl.com/zcabem6
Task List: http://tinyurl.com/hwpzywx
Download a copy of the lists:
Go to: File > Download As > Microsoft Excel
...
Originating System ID: click on title link to see where a record originated.
ILS=migrated from local catalog
SFX=migrated from SFX
NON_SFX=migrated from Chancellor's SFX instance or Summon (non-ExL migration form)
01cals_network= a record number that includes suffix 'network', this is a record that originated in the NZ. (example: ocn843860400-01cals_network)
Check List: This checklist is for items and settings for e-resources that should have migrated from SFX. Make sure e-collections migrated and are working. This will take some time so may want to share the items on this list.
Task List: This list is for items that are known to NOT migrate from SFX to Alma and may need to be set up post-migration.
...
During technical freeze, Ex Libris recommends that users stay out of the production environment as much as possible.
The Ex Libris Migration Team deletes, loads, and re-indexes data on a continual, as-needed basis in order to meet the cutover schedule. Therefore, Ex Libris cannot warrant the uptime or the performance of Alma during config freeze -- though it will actually be up and running during most of that time.
If users do log into Alma during config freeze, they should be aware of these caveats (and potentially other inconsistent behavior):
* Any changes made -- to data or to config -- will be lost and have to be re-done after the official cutover delivery.
* User sessions may be interrupted without warning if Migration needs to continue work by restarting Alma for any reason.
* Data may change during a user's session, due to ongoing migration work.
* Temporary error screens may appear at unforeseen times, due to ongoing migration work.
...
Recommended Search for e-Resources in the NZ that were migrated from SFX:
- Alma Dropdown menu > Find Electronic Collection > where Electronic Collection > contains NAME OF eRESOURCE (this is for a single e-collection)
- Query to locate merged SFX targets in the Alma NZ:
- Do a Repository Search > Find Electronic Collection > click Advanced Search > Add Condition > check Collection Available ONLY For in Electronic Collection section > click on Add Condition button > equals > Choose Campus
Known issues: (to look up cases in SalesForce: Go to Search Cases > Choose MY CONSORTIUM under Case Options > type in Case # in Case Number field > Click on Search)
Case #00230491: unable to add linking parameters to Factiva target. CSU only uses SID parameter and according to notes, if you use SID, do not fill in the other parameters but Alma won't let use same parameters with only SID.
Case #00203808: ‘Available For’ groups for e-resources are not displaying consistently. UPDATE: is now missing for more NZ e-collections. Look at Collection Available For facet to confirm your library is sharing e-collection.
Case #00228090: Network Zone search displays duplicate results usually indicated by a greyed out icon (we are calling these "ghost" records in the NZ).
Case #00229102: depending on the type of search, the library doesn't appear in the list of CSU's in Collection Available For facet *UPDATE & Correction: Ex Libris re-indexed the NZ and thought they had fixed the facets but they haven't been corrected for all e-resource.
Case #00230721: Proxy login not appearing for e-resources in the NZ
Case #00230491: unable to set up linking parameters for Factiva *UPDATE: Ex Libris able to repeat error, issue sent to developers.
Case #00230811: Wiley Online Journal coverage dates in NZ are incorrect. *UPDATE: coverage dates were incorrect in the migration form. Form will need to be fixed before last migration.
Case #00231285: CSUN seeing No Full Text Available message when clicking on View It in NZ e-Resources. *UPDATE: Ex Libris is able to recreate the problem on their server, sending issue to developers.
Case #00234556: PLOS - Public Library of Science Free is a merged target in SFX but does not appear in the NZ and unable to locate in the CZ.
(not a CSU case): When setting ‘Available For’ groups in the NZ for the Service level and passing special parameters (like CUST_ID or CLIENT_ID) from the Available For group, the special parameter is not being passed to the service. The issue results in the following – for example, CUST_ID will not be copied from the Available For groups in the NZ to the parser URL.
See List of Known issues.