Skip to end of banner
Go to start of banner

Fanshawe 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 11 Next »

Introduction

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

name like “…FieldMap_Raw_June6…”

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

 

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

 

 

 

 


 

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:

aonorato (Unlicensed) , here is your item subfield report I mentioned in Basecamp:

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

Andrea Bainbridge (Unlicensed) we’ve found a few records in Sirsi that are incorrect and have the library/location Londonmain and Reference, but they should be Cuddy Reference. Are we able to collapse both Reference locations into the Cuddy library during cutover, or will we have to update the location of these items in Alma after go-live?

aonorato (Unlicensed) , you can map those locations to an existing Alma location via the migration form mapping.

Andrea will post

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)

 

 

 From Andrea, June 14:

aonorato (Unlicensed) 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 Andrea Made

Questionnaire Tab

  • I added 950 as a local field, which is where your Sirsi catkey will be preserved.

Location Tab

  • I made “london” the default library for the “UNASSIGNED” location, as it was at Test Load. Line 5.

Item Type

  • Different codes can’t share the same description, so I changed Column D for lines 11 and 12, so they wouldn’t repeat the value from Column D, line 5.

Item Material

  • This tab needs a default value in line 5, so I chose “BOOK” for you in line 5.

Action Items for You

Questionnaire tab:

  • Review line 19. This was “no” for Test Load, but you listed “Yes.” Do you really want subfield indicators to appear in your item level/alt call numbers? If yes, that means the call nos will appear with the “$h” etc. like:

 

  • No labels