name file like "...FieldMap_Reviewed_20May.xlxs"

•  reviewed. CMc

name like “…FieldMap_Raw_June6…”

Raw form, with UNLOCKED Bibs & Items tab:

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 6^th.

• 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)

 June 17: Carol McNabb I noticed you no longer had user stat categories mapped on the field mapping posted above. Was that intentional? Do you want to migrate those for Cutover?

Please note that that I expected the values we mapped would be present; they were not.

June 20: Carol McNabb , here is the form where the patron tab is unlocked, if you want to add the Sirsi user categories as note fields.

June 23: per discussion have added SIRSI USER_CATEGORY3 as a note.

name like "MigrationForm_Raw_May25.xlsm"

June 9, from Andrea: Carol McNabb , here is your subfield report, as mentioned in Basecamp:

Posting reviewed form

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

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 6^th.

• 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 17, from Andrea:

Carol McNabb I have updated your migration form draft:

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.

You can upload your next version below. Depending on your answer above about user stat category mapping, we may need to amend your migration form for that, but please attend to the comments below.

Changes

Alma Library tab

• The values you entered do not actually exist in Alma. (You listed “BA” but the code in Alma for Barrie is “BARRIE.”) I replaced them with the library codes that do exist in Alma. See below for location tab implications.

Action Items

Alma Location Tab

• For column C, you must use values from the “Alma Library” tab.

• Fill in the lines at the bottom--all columns. These values are in your data but weren’t on the form.

• Make sure that where you use the same Alma Library/Location pair in cols C/D that the rest of the cells are also the same. See the final tab of the migration form for a report of these errors. As an example, this is not allowed:

Item Type

• Different Alma codes can’t have the same description. See the report tab for a report, but here’s an example:

• 

(either map to the same code, or provide unique descriptions for the codes.)

User Groups tab

• Please fill this in, all rows. Not: you can use the User Groups that already exist in Alma, otherwise new user groups will be created to match your form entries.

Uploaded reviewed form. Please advise if further changes required. Thanks.

June 24:

Carol McNabb, I’m still seeing over 100 warnings like:

As the warning says, we can let this go, and all rows were a code is repeated will just inherit the settings of the first row where the pair appears. In the example below we would force a “no” value for the one marked in red.

That’s option 1.

Option 2 is for me to post the full list of the warning, so you can try to reconcile all of them. Please let me know as soon as possible what you would like to do.

Andrea: You can send me the warnings and I will edit and re-post asap.