Table of Contents |
---|
Introduction
Ex Libris has prepared pre-extraction baseline (“version zero”) forms based on your test load forms and changes discussed on the Georgian - 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
|
|
|
|
| |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name file like "...FieldMap_Reviewed_20May.xlxs"
| name like “…FieldMap_Raw_June6…”
Raw form, with UNLOCKED Bibs & Items tab:
| name file like "...FieldMap_DRAFT_June11.xlxs")
|
June 27: Final field mapping posted above. Approved by Carol in comment thread below. --Andrea | |||||||||||||||||||||||||
Notes
| Notes
| Notes
| Notes
| Notes
| |||||||||||||||||||||||||
|
|
| 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.
|
Sirsi Migration Form Version Tracking
Version | Drop-dead Due Date | Who Will Post
|
|
|
| Final Version for Migration | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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
June 27: final migration form for Cutover, approved by Carol in comment thread below. --Andrea | |||||||||||||||||||||
Notes
| Notes
| Notes
| Notes
| |||||||||||||||||||||
|
|
| 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
Action Items Alma Location Tab
Item Type
(either map to the same code, or provide unique descriptions for the codes.) User Groups tab
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. >> Carol McNabb , here is the form. If you don’t catch all the warnings after this go-round, we may just have to let it fly. --Andrea- when I try to “edit” this page and attach the file it won’t open the table properly so posting here
|