Introduction
Ex Libris has prepared pre-extraction baseline (“version zero”) forms based on your test load forms and changes discussed on the St. Lawrence - 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
0. Baseline/Version Zero | May 6 | ExL |
| 2. Raw Field mapping form from the validator | June 6 | Jennifer/Stacey | 3. Draft Form for ExL Review | June 14 | Colleges/Jennifer/Stacey | 4. Final Version for Migration | June 21 | ExL |
---|---|---|---|---|
name file like "...FieldMap_Reviewed_20May.xlxs" | name like “…FieldMap_Raw_June6…” | name file like "...FieldMap_DRAFT_June11.xlxs") | ||
Notes
| Notes
| Notes
| Notes
| Notes
|
From Andrea, June 13: Brenda Stull Desjardins , a few questions. Just confirming your intention: Serial control I know you are using SISAC_ID as your bib matchpoint. Do you want to preserve the old Sirsi SERC_TITLE_KEY as a note? Your current mapping indicates “Do Not migrate.” this is fine, if you don’t think you will need it. Hi Andrea Bainbridge (Unlicensed) Yes, I’d like to preserve the old Sirsi SERC_TITLE_KEY. To understand what happened is it because the SERC_TITLE_KEY is mapped to SISAC_ID and it isn’t listed anywhere else on the mapping? Brenda Stull Desjardins , you are correct. When we swapped in SICAC_ID as the bib matchpoint, the Sirsi field “SERC_TITLE_KEY” was no longer mapped to anything. I made the change to line 27 of the serial control tab for your review. (New version below) Loans I see that you chose not to map NUM_RENEWALS and RENWEAL_DATE. Was this intentional? Hi Andrea Bainbridge (Unlicensed) I believe this is is a mistabke please ensure they are mapped. Not sure how these got moved. Brenda Stull Desjardins , it’s fixed. See below. Please consider this version as your current draft. Please review my changes. and if you approve, you can resubmit as your final field mapping. |
Sirsi Migration Form Version Tracking
Version | Drop-dead Due Date | Who Will Post
0. Baseline/Version Zero | May 6 | ExL |
| 2. Draft Form for ExL Review | June 14 | Colleges | 3. Final Version for Migration | June 21 | ExL |
---|---|---|---|
name like "MigrationForm_Raw_May25.xlsm" June 9, from Andrea: Brenda Stull Desjardins here is the item subfield report I mentioned in Basecamp | name file like "...MigrationForm_DRAFT_date.xlxs") | Andrea will post | |
Notes
| Notes
| Notes
| Notes
|
From Andrea, June 13: Brenda Stull Desjardins , I made some updates to your draft migration form. See below for a list of the “Changes” I made, and “Action Items” for you. 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 Alma Location Tab
Item Material Tab
Thank you Andrea Bainbridge (Unlicensed) 06/15/2022 Action Items Item Type Tab and Item Material Tabs
Holding Code tab
Hi Andrea Bainbridge (Unlicensed) this is a funny one. Can it be removed completely for Kingston and Default? Item Base Status I don’t see Sirsi value “INTRANSIT,” listed here. Do you want to map it? If not, it will receive the default status of “in place” with no item note. (This might be what you wanted, but just checking.) Hi Andrea Bainbridge (Unlicensed) I have re-added “INTRANSIT” Brenda | |||