...
|
|
|
| ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name like "MigrationForm_Raw_May25.xlsm"
June 9, from Andrea: emcdonald , here is your item subfield report, referenced in Basecamp:
| name file like "...MigrationForm_DRAFT_date.xlxs")
| Andrea will post | ||||||||||||||||
Notes
| Notes
| Notes
| Notes
| ||||||||||||||||
|
| June 15, from Andrea 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. Changes Item Base Status
Action Items Item Type
Material Type
User Group
Andrea Bainbridge (Unlicensed) here is our Final Migration Form:
Andrea Bainbridge (Unlicensed) – there were three ‘errors’ in the last ‘Report’ tab: Line 9 we can ignore. Line 8 – there was no ALMAME_VAL_NOT_FOUND in the form delivered to us, so I didn’t enter it in that tab. If it needs to be there would you be able to add it for us? Anything ‘not found’ can be just mapped to Progress Reserve. Line 7 - That particular cell was already populated with PROGRESS as the Alma Library Code when the form was delivered to us, which is the correct code. However, I hadn’t populated the Alma Location Library tab yet (obviously), so I wonder if that is why this is showing up as an error. ~Katrina |
|