| 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")
|
|
June 27: final migration form for Cutover, approved by Carol in comment thread below. --Andrea | |||
Notes
| Notes
| Notes
| Notes
|
|
|
Andrea |
Carol McNabb I have updated your migration form draft:
| View file | ||
|---|---|---|
|
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.
- when I try to “edit” this page and attach the file it won’t open the table properly so posting here
|
|
|
|