Skip to end of banner
Go to start of banner

Humber College - Mapping & Migration Forms

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 21 Next »

Introduction

Ex Libris has prepared pre-extraction baseline (“version zero”) forms based on your test load forms and changes discussed on the Humber - 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

 

name file like "...FieldMap_Reviewed_20May.xlxs"

Stacey Boileau - file done

name like “…FieldMap_Raw_June6…”

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

Andrea Bainbridge (Unlicensed) - file done

 

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) > Lisa Di Barbora
  • Submitted to migration (Andrea will check this box)

 

 

 

June 14, from Andrea

 Lisa Di Barbora , I have updated your field mapping form, with a few changes. DOWNLOAD THIS VERSION to review and use as the basis for changes if needed.

Changes

  1. I updated the form to include mapping for funds--which was not present. Please review tat tab. No action needed if it looks ok to you. ALSO NOTE: your find file was not in csv format so I have reformatted and uploaded it to MFT. Please review it.

  2. I know you updated your serial control bib matchpoint to be SISAC_ID. Did you want to preserve the Sirsi SERC_TITLE_KEY in a note? I unlocked the “serial control” tab in case you do.

  3. I removed mapping for Sirsi “Current Location”/999$k from “Bibs & Items” since you do not want to use the “Item base Status tab of the migration form.

June 16 from Lisa

Andrea Bainbridge (Unlicensed) - our responses to your change questions.

  1. The .csv version of the Funds file looks good and we are okay with the Funds tab mapping.

  2. We do not want to preserve the Sirsi SERC_TITLE_KEY.

  3. Thanks for removing 999$k


June 16: Lisa Di Barbora , since you had no changes, I posted the field mapping as final. It's posted above for your final approval.

--Andrea

 

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

 

name like "MigrationForm_Raw_May25.xlsm"

June 9, from Andrea: Lisa Di Barbora , here is the item subfield report I mentioned in Basecamp:

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

Andrea Bainbridge (Unlicensed) - file done. A few notes:

  • Humber doesn’t want/need the content in the 3 red tabs (holding code, item base status, currency code)

  • we were unable to delete the content ourselves so asking you to do it for the final version


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)
  • Submitted to migration (Andrea will check this box)

 

 

 June 14 from Andrea:

Lisa Di Barbora , here is an updated draft of your migration form:

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

Questionnaire Tab

  • I added 950## as a local field in line 21, to preserve your Sirsi catkey.

  • Changed Line 37 to be “Yes”

  • Changed line 19 to “No,” otherwise alt call number will appear with the “$” like

  • Line 28: set default currency to CAD

Alma Location Tab

Line 5: replaced “EMPTY” with t “NORTH” as the default library for UNASSIGNED location, as it was at Test Load.

Item Base Status

  • I have removed mapping for this, but am leaving the default on this tab of the migration form.

Item Material

  • I had to set a default value, in case it can’t be determined via the bib.

Action Items

Alma Location Tab

  • I added line 55--please fill this out.

Holding Code

  • Holding code is required, since we use this in creating holdings. I have filled it out based on your Test Load form, but need your input on lines 5, 6 and 9. The pair in columns C/D must exist in the Alma location tab in columns A/B.

June 16 from Lisa

Andrea Bainbridge (Unlicensed) , we completed the requested action items so here is updated draft.

In addition, we agree with all of your changes.

 June 16: Lisa Di Barbora , I have validated your migration form and reposted above for your final review. Thanks!

--Andrea

Andrea Bainbridge (Unlicensed) - is this the correct version? I expected the file name to have “Final” like the field mapping name does. I just want to ensure that we are approving the correct one. Thanks, Lisa

June 16: 2:30 EST Andrea Bainbridge (Unlicensed)

We looked at the “Report 2022-06-16 15.34.20” tab and saw the following

  • Alma Library Cell <A9> must not be longer than 10 characters

  • Alma Library Cell <A10> must not be longer than 10 characters

  • Course Unit Cell <A5> value must be <ALMAME_VAL_NOT_FOUND>

For the Course Unit tab, I can’t insert the “val not found” line. So can you add it for us and use TEXTBOOK in col C?

Also, we believe that our Alma Library name lengths are acceptable because they have already been created in Alma.

  • No labels