...
The SAD Subcommittee prepared two additional resources for colleges completing the mapping and migration forms. They may be helpful in completing your forms, but please note that the Subcommittee did not come to a final decision or recommendation in some areas. They found that recommendations varied depending on the system each college was migrating from. You will find these details in the comments seen when selecting text highlighted in yellow. explain that, “It should be made clear to Mohawk and Niagara that the cheat sheet linked to below focuses on patron data, whereas the migration and mapping forms have a broader focus on library, collection, users, etc. Patron fields labels coming from Evergreen won’t be the same as SIRSI….so the Symphony references won’t be useful.”
They added:
“I think if I were to update the page at all (if you are planning to keep the focus on patron data) I would be a little more specific about the goals for patron data in each form.
Field mapping form provides a place to:
Map patron data (email is mandatory)
Map fields to connect migrated user records to loans, bookings, etc., that are being migrated; For some systems , the USER_ID, UNIV_ID and the BAR may overlap with same data. Among other things, Boreal mapped incoming Evergreen fields: ‘id,’ ‘usrname,’ etc.
Map user stat categories
Migration form, questionnaire tab, provides a place to:
Designate a primary ID – mandatory with Alma; this may or may not be the same as #1 above
Work on SIS match and Authentication will come later.”
...