Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7

Introduction

The tables below will be used to capture important notes for Cutover including actions that must be taken prior to migration as well as your library’s data migration preferences. Please follow the instructions included with each table. Please complete sections for colleges by April 29th.

Notes for Cutover (For Ex Libris and Colleges to Complete)

Complete each action item assigned to the College below. Select the check box next to the action item when the item is complete. New items should only be added to this table by Ex Libris. Please contact Ex Libris via Basecamp for questions about these action items.

...

Issue Description

...

Action Items/Due Date (check when done)

...

Ready for Cutover?

...

TL users were missing “original ID”

Resolution Notes:

Per Katrina in Basecamp: data has been corrected; no need to update field mapping. https://3.basecamp.com/3765443/buckets/23965261/messages/4554663642#__recording_4746717058

Ex L

  •  [action]; due

College

  •  Review field mapping at Cutover; is there a better candidate for what to map to “USER_ID”, instead of USER_ALT_ID? And/or: review patrons who are missing whichever value is mapped to “USER_ID”. See https://3.basecamp.com/3765443/buckets/23965261/messages/4554663642
  •  See list of affected patrons here. NOTE: the tab is filtered to display only the missing USER_ALT_ID, but the other users are there. This way you can reference the same line numbers you see in stats:

...

Ex Libris has prepared pre-extraction baseline (“version zero”) forms based on your test load forms and changes discussed on the Centennial - Notes for Cutover page. The baseline forms, both Field Mapping and Migration, have been posted below. Please review these forms and follow instructions included in the Sirsi Field Mapping Form Version Tracking table and the Sirsi Migration Form Version Tracking table below.

Sirsi Field Mapping Form Version Tracking

Version | Drop-dead Due Date | Who Will Post

  1. Baseline/Version Zero | May 6 | ExL

  1. Field Mapping for Data Validation | May 20 | Colleges

  1. Raw Field mapping form from the validator | June 6 | Jennifer/Stacey

  1. Draft Form for ExL Review | June 14 | Colleges/Jennifer/Stacey

  1. Final Version for Migration | June 21 | ExL

 

View file
name01OCLS_CENTENN_CO_FieldMap_Baseline_6May2022.xlsx

View file
name01OCLS_CENTENN_CO_FieldMap_Reviewed_17May.xlxs.xlsx

name like “…FieldMap_Raw_June6…”

View file
name01OCLS_CENTENN_CO_FieldMap_RAW_30May2022.xlsx

name file like "...FieldMap_DRAFT_June11.xlxs")

View file
name01OCLS_CENTENN

_UsersIDanalysis

_CO_FieldMap_DRAFT_14June2022.xlsx

 

Use other data in the record, like USER_ID field to identify the patron.
  •  Yes
  •  No

Preferred name mapping for patrons

ExL

  •  Remove “USER_NAME” as preferred name on baseline migration form.

Only fields that contain personal/first names should be mapped as preferred.

USER_NAME includes user first and surname

  •  Yes
  •  No

migrated patron barcode made internal per request

College

ExL

  •  Mark Barcode as internal again at CO if requested.
  •  Yes
  •  No

Course unit mapping

At TL there was a bug in migration scripts that created multiple departments in stead of a single department, as requested on the migration form. ExL will fix for Cutover.

ExL

  •  Ensure migration form preferences for course unit mapping are applied
  •  Fix migration script
  •  Yes
  •  No

items embedded in shadowed bibs were not migrated

ExL

  •  Reason: shadowed bibs were not included in item extraction
  •  Cutover: migration analyst will extract items from all bibs

College

  •  Check that inventory from shadowed bibs exists in Alma at Cutover
  •  Yes
  •  No

CENTENN requests no resource be active for them in the NZ

College/OCLS

  •  Yes
  •  No

missing 360 selective titles

https://3.basecamp.com/3765443/buckets/23965261/messages/4667662902

ExL/College

  •  check for multiple “tracked resources” reports
  •  Yes
  •  No

change to patron email mapping at CO

See Basecamp: https://3.basecamp.com/3765443/buckets/23965261/messages/4853790805#__recording_4864624909

ExL

  •  Amend baseline form per college preference

Image Removed

College

  •  Confirm changes needed
  •  Review when baseline form is released during week of May 2
  •  Yes
  •  No

 Migration Preferences (For Colleges to Complete)

Indicate your library’s migration preferences by selecting the appropriate check boxes below. Use the links in the header row to find background information and documentation to assist with each decision.

...

Confirm Serial Control - bib matchpoint

Backgrounder

Sirsi Item Material Type Mapping

See Basecamp FAQ

...

Retain at Cutover

ExL Documentation;

See #13 of Cutover Prep slides

Acquisitions Options at Cutover

...

Do you want PQIS enrichment and/or EBC run for you at Cutover, in addition to your 360 or LR form activations?

Troubleshooting E-Resource Duplication Issues

...

Will you participate in Fulfillment Cutover?

ExL Documentation

...

Will you use the Alma offline Circ Utility during Fulfillment Freeze?

ExL Documentation

...

  •  SERC_TITLE_KEY
  •  SISAC_ID
  •  OTHER:
  •  I do need to identify specific parameters for SERC_TITLE_KEY or OTHER as described in the Backgrounder (OCLS and Ex Libris will follow up with you)

...

  •  Map nothing (items inherit material types from bibs)
  •  Map to same field as item type (usually Sirsi 999$t)
  •  Map to 999$x

...

  •  Courses & Reading List Headers
  •  Ledgers and Funds
  •  Licenses
  •  COUNTER data

...

PQIS Activations

  •  I want PQIS at Cutover
  •  I do NOT want PQIS at Cutover

Ebook Central Integration (Ebook Central Perpetual, DDA and Subscription)

  •  I want E-Book Central Pro Integration (EBC) run at Cutover
  •  I do NOT want EBC at Cutover

...

  •  Yes
  •  No

...

  •  Yes
  •  No

Data Preferences (For Colleges to Complete)

Check all that you are submitting again for Cutover.

...

Scope

...

  •  Bib Records (Shadowed)
  •  Bib Records (Unshadowed)
  •  Course/Reserves
  •  Patrons
  •  Fines and Fees/Active Bills
  •  Active Loans

...

  •  Requests/Available Holds
  •  Serial Control
  •  Issue
  •  Funds
  •  Orders (>2011)
  •  Invoices (>2011)

...

  •  E-resource Activation Form
  •  P2E

...

Data Extract Tracking (For Sirsi Colleges and OCLS to Complete)

This table will be used to capture details of the data extract scope indicated above in the Data Preferences table. You may prefer to exclude records from the data extracts that OCLS will complete on your behalf. Use the second column of this table to provide the details OCLS will use to exclude data from your extracts if this is your preference. For example, indicate “exclude bib records that contain 996=Proquest. You will find examples of exclusion identifiers in the third column. Please provide whatever information will be necessary to identify records for exclusion.

...

Data Type

Exclusion Identifier

...

Exclusion Identifier Examples

...

Notes

...

Status (For OCLS to Complete)

...

Bibliographic Records (Shadowed records)

...

Exclude bib records that contain certain MARC fields such as 996=Proquest, or 856=www.nfb.ca

...

Do you want Multi-volume custom script?

Background information

  •  Yes
  •  No

...

Bibliographic Records (unshadowed records)

...

Sirsi Home Location = E_RESOURCE (same as test load)

...

Exclude bib records that contain certain MARC fields such as 996=Proquest, or 856=www.nfb.ca

...

Courses/Reserves

...

Exclude Item Type=LAPTOP (Laptops or other equipment items can be put into another location in Alma.)

...

Patrons

...

Exclude User Profile=ADMIN

...

Fines and Fees/Active Bills

...

Exclude Bill Reason=PROCESSFEE

...

Active Loans

...

Exclude all loans for the the pseudo user=MISSING

...

Requests/Available Holds

...

Not applicable

...

Serial Control

...

Exclude Serial Control Created > , or < DATE

...

Issue

...

Exclude Issue Created > , or < DATE

...

Funds

...

Exclude Funds Created > , or < DATE

...

Orders (>2011)

...

Exclude Closed Orders

...

Invoices (>2011)

...

Exclude Invoices Created > , or < DATE

OCLS Assistance with P2E (For Colleges to Complete)

Do not include collections in P2E that will be activated by other means. See the Troubleshooting e-Resource Duplication Issues note for more information.

Use the table below to identify collection titles that can be extracted in batch by OCLS for your P2E files. Include information OCLS staff can use to identify the collection records.

...

Collection Title

...

Collection Identifier (For example, 996=Curio, or 856=https://www.nfb.ca)

...

Indicate if this collection is a Database or Portfolio

Ex Libris Documentation

...

***As we did for test load, Centennial will again create our own short P2E file of bib records for physical items which also contain links to online versions of the resource. We will not need OCLS assistance. (MM)

...

N/A

...

N/A

...

Add additional Rows as necessary

Test Load Environment Release Notes (For Ex Libris to Complete)

...

View file
name01OCLS_CENTENN_CO_FieldMap_Final_June20.xlsx

June 20, from Andrea: Katrina Hansen , Mary-Margaret Mirtsos , emcdonald

Apologies, here is the form where SERC_TITLE_KEY is mapped. Please review and indicate your approval below. If you do approve, this will be the final version of your field mapping form.

Notes

  • This is an unlocked copy of the Test Load (TL)  form that includes changes discussed in Notes for Cutover.

  • Make changes in the form if necessary by May 20th.

  • Communicate changes you make by posting comments on this page.

Notes

  • If no changes were required to the Baseline form at left, repost the form above, or...

  • ...post amended form with required changes above by May 20.

  • Jennifer and Stacey will  use this version when they validate your data.

Notes

  • Jennifer and Stacey will post your copy of the raw field mapping form from the validator here by June 6th.

  • This version of the form is locked. You cannot make changes to this version.

  • Communicate changes needed by posting comments on this page before June 14th if necessary.

  • If no changes are needed, re-post the form at right by June 14th.

Notes

  • If no changes are needed, this may be the final version of your field mapping form.

  • Andrea will post comments or questions to this page if needed.

  • Versions under discussion can be posted below, if needed.

Notes

  • **No Further Changes**

  • Andrea will post the final version of your form here by June 21st.

  • Select the “Approved by College” option below and “@” mention yourself to confirm.

  •  Approved by College /("@" mention yourself to confirm – approved by Katrina Hansen
  •  Submitted to migration (Andrea will check this box)

 

 

 

From Andrea, 6/15:

 emcdonald Katrina Hansen , I updated your field mapping with a single change:

  • I mapped the old Sirsi SERC_TITLE_KEY to a note field (otherwise it wouldn’t migrate anywhere, since you switched to SISAC_ID as a matchpoint)

Andrea Bainbridge (Unlicensed) Mary-Margaret Mirtsos It looks like that SERC_TITLE_KEY is not mapped to a note field? I tried to map it myself but cannot. I tried to unprotect the sheet but it requires a password.

Image Added

Here is that updated form:

View file
name01OCLS_CENTENN_CO_FieldMap_ExL_DRAFT_15June.xlsx

Download this form and review it. If you approve of the change and have no further changes of your own, this may be considered your final field mapping form, and can be re-uploaded in the column to the right.


 

Sirsi Migration Form Version Tracking

Version | Drop-dead Due Date | Who Will Post

  1. Baseline/Version Zero | May 6 | ExL

  1. Raw Output from the Data Validator | June 6 | Jennifer/Stacey

  1. Draft Form for ExL Review | June 14 | Colleges

  1. Final Version for Migration | June 21 | ExL

 

View file
name01OCLS_CENTENN_CO_MigrationForm_Baseline_3May2022.xlsm

name like "MigrationForm_Raw_May25.xlsm"

View file
name01OCLS_CENTENN_CO_MigrationForm_RAW_30May2022.xlsm

June 9, from Andrea:

emcdonald , here is your item subfield report, referenced in Basecamp:

View file
nameCentennial.xlsx

name file like "...MigrationForm_DRAFT_date.xlxs")

View file
name01OCLS_CENTENN_CO_MigrationForm_DRAFT_14June2022.xlsm

View file
name01OCLS_CENTENN_CO_MigrationForm_FINAL_June22__v004.xlsm

June 22: Katrina Hansen , I made no changes to your last version of the form, other than to run it thru our internal validation. Please review and indicate your approval below. Thanks!

--Andrea

June 23:

Version with additional locals added.

View file
name01OCLS_CENTENN_CO_MigrationForm_FINAL_June23__v004.xlsm

Notes

  • This document is FOR REFERENCE ONLY.

  • This is a copy of Test Load (TL) form that includes changes discussed in Notes for Cutover.

  • On many tabs it also still contains TL mapping preferences. Use this as a reference for filling out the CO form produced by the validator after June 6th, but DO NOT COPY/PASTE from this form into the CO form.

Notes

  • Jennifer and Stacey will post your copy of the raw migration form from the validator here by June 6th.

  • Colleges: download this form and fill out all tabs manually by June 14.

  • Use the baseline form posted at left as a REFERENCE ONLY.

  • Be sure to fill in all tabs, including the Questionnaire Tab.

  • When complete, post the new version in the column to the right.

Notes

  • Post your approved draft here by June 14.

  • If no changes are needed, this may be the final version of your migration form.

  • Andrea will post comments or questions to this page if needed.

  • Versions under discussion can be posted below if needed.

Notes

  • **No Further Changes**

  • Andrea will post the final version of your form here by June 21st.

  • Select the “Approved by College” option below and “@” mention yourself to confirm.

  •  Approved by College /("@" mention yourself to confirm)

Approved by Katrina Hansen

  •  Submitted to migration (Andrea will check this box)

 

 

June 15, from Andrea

emcdonald , Katrina Hansen

 I have updated your migration form draft:

View file
name01OCLS_CENTENN_CO_MigrationForm_ExL_DRAFT_June15__v002.xlsm

Download THIS VERSION of the migration form in order to make the changes requested in “Action Items” before you submit your final migration form.

For “Changes” listed below, there is no action needed unless you want to make a different choice than I did.

Changes

Item Base Status

  • I removed lines for HOLDS and CHECKEDOUT, since these statuses will be accounted for in your loans and requests extracts.

Action Items

Item Type

  • I did not make any changes here, but just want to make sure you have made all the changes you had mentioned on your Notes for Cutover page for this tab. Pls review. Thx!

Material Type

  • I added two lines, based on your item subfield report. Please provide mapping for these 2 additional types.

User Group

  • I added several lines for values I saw in your data that weren't accounted for. If you had left them off intentionally, because they are unneeded in Alma, just map these lines to the default User Group., and you can review th4ese users later.

Andrea Bainbridge (Unlicensed) here is our Final Migration Form:

View file
name01OCLS_CENTENN_CO_MigrationForm_ExL_FINAL_June21__v002.xlsm

Andrea Bainbridge (Unlicensed) – there were three ‘errors’ in the last ‘Report’ tab:

Image Added

Line 9 we can ignore.

Line 8 – there was no ALMAME_VAL_NOT_FOUND in the form delivered to us, so I didn’t enter it in that tab. If it needs to be there would you be able to add it for us? Anything ‘not found’ can be just mapped to Progress Reserve.

Line 7 - That particular cell was already populated with PROGRESS as the Alma Library Code when the form was delivered to us, which is the correct code. However, I hadn’t populated the Alma Library tab yet (obviously), so I wonder if that is why this is showing up as an error.

~Katrina

June 22:

Katrina Hansen , I’m looking over your latest version. Thanks! About the errors: you can ignore them. I had made the location correction before giving you the form. After I review your form I’ll let you know if we can call it final (and I’ll ask for your formal approval) or if I have any other questions. Thanks!! --Andrea

Excellent! ~Katrina