Humber

Yes > original
Yes > ACQ version > deleted line 39 in the Orders tab and line 51, 53-58 in the Invoices tab

Yes > original
Yes > ACQ version

Northern

Yes

Yes

Sheridan

Yes

Yes

Georgian

Yes

Yes

Fanshawe

Yes

Yes

Centennial

Yes

Yes

St. Lawrence

Yes

Yes

Fleming

Yes

Yes

Sault

Yes

Yes

George Brown

Yes; ACQ version loaded Nov 9 under Submitted Documents folder.

Yes; ACQ version loaded Nov 9 under Submitted Documents folder.

Algonquin

Yes

ACQ file loaded to MFT - small change on Orders tab

Yes

ACQ file loaded to MFT

Confederation

Yes

Yes

Conestoga

Yes

Yes

Humber

Yes

18 Nov: approved file is Humber_sirsi_migration_form__MASTER_updatedv004.xlsm

field mapping file:
*we did not make any changes to the master 20211118 version

17 Nov history: approved file is Humber_sirsi_migration_form__MASTER_updated20211117.xlsm

notes:
*we want to choose option 3 for the Item Material tab
*we made a change to the Questionnaire tab > row 21 > column B from 985## to 986## according to the Nov 16 meeting notes (949 to 986; 004 to 951; 536 to 590; 541 to 591)

16 Nov: from ExL: The validator flagged some errors in the migration form: See tab "Report 2021-11-16..." It will list lines of the form where we have broken some rules, like:
Holding Code: Lines 6, 11, 15 do not refer to an existing paring in Columns A/B on the location tab. Please review and fix.
Alma Location tab: where lines that are mapped to the same Alma Library/Location pair (columns c and d) the rest of the row must also be the same. Lines 12-15 are done correctly; lines 23 and 24 break this rule. Please review and make changes where flagged.
Alma Location tab: Column F, Alma Location Name can only be associated with a single location per library. E.G see lines 12 and 22, where they have different values in Column D, but the same value, For Review, in column F. Please review and make changes where flagged.

Also: Humber making changes to material type

Follow up question: for your UserStatCategories tab, I know you are interested in collapsing multiple lines into one, like “Nursing.” But thinking ahead to SIS: which value will be in your SIS load for Categorry 1…will it be “0351,” or will it be “LAW?” In Column C, you want to have a value that will also be in your SIS.
Humber Nov 17 response: we are going to be working on a completely new SIS integration that will replace many of these values entirely. The values in the current form such as LAW have been chosen deliberately in preparation for any new information what will be in the new integration. (ok. --AB)

18 Nov (from Andrea): You need to fix location errors like lines 15 and 42, where within the Alma NORTH library you have a location code ONLINE with location name “For Review” (Column F). But in line 42 you have a different location within NORTH, FORREVIEW where the description is also “For Review” (column F). Please see the final tab of the new migration form for a list of these errors, and review https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/Symphony_to_Alma_Data_Delivery_and_Migration_Guide#Alma_Location_Name_and_Alma_External_Location_Name .

18 Nov (Humber response): made all of the requested changes

La Cite

Yes

Yes

12 Nov: pending decision on additional ID

15 Nov: email added as an ID. new form on MFT.

18 Nov: we would like to choose OPTION 3 for the Item Material Tab.

Nov 19 (from Andrea): Forms updated for option 3. Pls update the Item Material” tab of the migration form, and reupload.

Note from La Cité : reuploaded under : LaCite_Sirsi_Migration_Form_MASTER_20211122

Northern

Yes

Yes

Notes from Andrea:

1. Based on the OCLS recommendation, instead of copying/moving your 004 to 954, I will move it to 951. (as we will for all sites). I have made the necessary change to your migration form.

2. Please let me know by Nov. 19 if there are any additional fields in the specified range that you want make local.

3. Are there any elements of your patron data that you would like to protect from being overwritten by SIS? This is not required. But for example, perhaps there is a certain email type, or phone type, that will not be in your Banner load. We can make it internal and it will stay in Alma, attached to the patron record, even if it does not exist in the SIS load.

4. Your P2E has two lines for bib ID 129195. In one line it is identified as a database, and as a portfolios in another. Which is correct? Only one entry is allowed.

Sheridan

yes

yes

15 Nov: posted, pending review by ExL (scripts for value extract--all bibs reviewed?) and Sheridan (Base Status, Item Type, Item Material)

16 Nov: ExL confirmed that all bibs were checked when extracting values for migration form tabs (e.g for Item Type tab & Base Status tab) .

18 Nov (from Sheridan): Andrea Bainbridge (Unlicensed) Our team wants to go with Option #3, outlined on this BC page: https://3.basecamp.com/3765443/buckets/23965261/messages/4361906962

18 Nov (from Sheridan): Andrea Bainbridge (Unlicensed) we uploaded the revised forms to MFT folder for you to review and prepare for tomorrow’s session at 2pm. Both file names are suffixed with ‘Sheridan Updates’. The tabs in Blue color are ones we made changes.

19 Nov (from Andrea): latest forms are on MFT, with changes discussed in the meeting. Ready for Stat category corrections. Pls change the file name in some way when you reupload. Thanks!!

19 Nov (from Sheridan): the latest migration form file (Sheridan_Sirsi_Migration_Form_MASTER_2021119__v004_SheridanUpdated.xlsm) is on MFT. For the error about course unit, we couldn’t update A5, so please insert ' ALMAME_VAL_NOT_FOUND’ in A5, and ‘NOT_FOUND’ in C5. For the warning about B13, we left empty bacause we don’t use SFX.

There is no changes required for mapping form so we didn’t upload a new version.

Georgian

Fanshawe

Yes

we would like to switch to option 3 for Item Material

Stat Category descriptions have been added - updated form uploaded to MFT Fanshawe_Sirsi_Migration_Form_MASTER_updated_20211117

Note from Andrea: forms on MFT and final, pending email username as ID type--instructions sent via email to Tony.

Nov. 16: please populate column D of the UserStatCategory tab, and reupload the form

Nov. 17 (from Andrea): migration form that allows for Item Material mapping is now on MFT. New field mapping also uploaded, to reflect the change. November 19 (from Tony): updated/final migration form uploaded to MFT Fanshawe_Sirsi_Migration_Form_MASTER_updated_20211119

Dec. 11 (from Andrea): For user stat categories, you can’t have two different codes (Column C) with the same description (Column D).

Option1)

I can append the code value from C to the value in column D, like:

2) or: are you trying to collapse several rows, like 5-12, into a single Alma stat category?

To do that, the form would look like:

You can do this, but you want to make sure you maintain codes that will be coming from your SIS.

Let me know. If you choose option1 I can make the change. If you choose #2, please make the change and submit a new form. Thanks!

Centennial

Yes

Yes

17 Nov (Andrea note): Centennial staff should: fill in Item material tab and review errors from the validator, e.g. making User Stat Category descriptions unique. Use the files posted to MFT as your starting point. Upload edited forms to MFT with new data in the file name.

19 Nov (from Katrina): form edited/completed and file with date of 20211119 uploaded to MFT

30 Nov (from Eva): Two 360 reports uploaded to MFT: Database_Details_Report_CC.-2021-11-20-92127.csv
Tracked_Resources_CC.-2021-11-20-92128_2.csv

St. Lawrence

Yes

15 Nov: ExL: checking on patron validation; St.Law: check Stat category descriptions (see error tab)

16 Nov: from ExL: no issue with patron validation; file and mapping are ok

17 Nov: from Brenda: Stat Categories corrected and file reloaded with new date in MFT.

Fleming

Yes

Yes

Sault

Yes

Yes
file is called: Sault_Symphony_Sirsi_Migration_Form__MASTER_20211117.xlsm

16 Nov: ExL posted to MFT; needs mig form change for UserStat Category descriptions

17 Nov: from Jenn: UserStat Category descriptions added. Corrected file has been uploaded to MFT

George Brown

Yes

yes.

For Item Material mapping, we chose option 3, as been discussed in the meeting.

16 Nov (from Andrea): a few holdings codes still aren't mapped to real Symphony library/location pairs--pls review this tab. These are also noted on the error tab of the migration form. Pls populate the Item Material tab, and fix descriptions as needed on the User stat category tab.

November 19 (from Joy ): Final migration form uploaded to MFT. Made changes as requested (holding codes; Item material tab, user statsCat, also changed one library code to conform to the 10 character limit).

Algonquin

Yes

Updates made to migration form and loaded to MFT with new date. Can you populate the item materials tab?

*Also the Master Mapping file does not have the Acquisitions tabs included - the files were not merged. Thanks!

Current Mapping form on MFT is approved. Algonquin_Field_Mapping_MASTER_20211119

Final Migration form uploaded to MFT, file ending _20211119-v3

19 Nov (from Andrea): please let me know your decision about Item Material as soon as possible.

I added some lines to the Alma Location tab which you need to fill in--locations in your data that our validator had missed. Likewise: there are extra lines for you to populate on the Item Type tab.

From Maureen: We would like to try option 3 for Item Material. How should we fill in the Item Material tab in that case?

19 Nov (Andrea): YIKES! Field mapping form has been corrected and uploaded, per your note.

I populated the “Item Material” tab. For each row you must choose an option from the drop-down menu to populate Column C. My file name ends like “…20211191-b,” so just make some change to the file name when you upload the new one.

Confederation

Yes

Note from Andrea: Are there any patron data fields that you would like to protect from being overwritten by SIS? For example, if there is a certain patron ID in Symphony that would not be part of your Banner load, we can mark it as internal so that you don’t lose it when the record is updated by SIS.

Conestoga

Yes

Chris: let me know if there are tags that should move to a 9xx in the 950-999 I will do the 004 From Chris, Nov 19: Can you move 949 to 988? We’re not exactly sure what 949 has been used for in the past but some records have Conestoga specific details in them in 949. 988 is unused by us. If this can be done, then we don’t need to protect 949 as per the instruction in Questionnaire Row 21 in my 20211119 Updated form.

Nov 16: please populate Column D of the UserStatCategory tab, and reupload. From Chris, Nov 19: Done. If it’s possible to remove the words “course code” from the value and description, I’d rather that. I just couldn’t seem to enter our 00XX style codes witout the zeros dropping due to excel’s wizardry.

Chris, Nov 19: Migration Form resubmitted to MFT with changes noted above, as well as:

• Revisions to Questionnaire Row 21

• Item Material tab mapped

• Further categories set to “not found” on User Group Tab.

Mapping Form not resumbitted; no changes.

Andrea, Nov 22: Chris Woodley , you listed 949 as a desired local tag. In the IZ your 9xx local fields must be between 950-999. I will move 949 to 959, and make 959 local on the migration form--so the 949 tag data will still be preserved, but in 959. After this, no further changes will be needed to forms. I’ll indicate here when I’m done.

Georgian

Yes -

OM_Georgian_Field_Mapping_UNLOCKED_Oct24

OM_Georgian_Symphony_Sirsi_Migration_Form_v001

Yes - have uploaded to MFT the revised Symphony mapping form including changes made to reflect Option 3 for Item Type.

Note: Olivia made whatever changes necessary on the Field Mapping_Unlocked form at the time of our meeting (Nov. 18)

Notes from Olivia:

Based on call - make recommended changes to item type and material type tabs. UPDATE from Carol: choosing Option 3 and will update appropriate tabs as necessary (Nov.17)

Forgot to say that I will copy 004 (Sirsi cat key) to 951 and marking as local on Migration Form.

If there are any patron data fields you would like to protect from being overwritten by SIS? UPDATE from Carol: do not believe so; will review once we have test environment (Nov. 17)

Nov 19 (from Andrea): new forms on MFT. Pls review migration form errors in the final tab. Revise form and reupload (change file name slightly if needed.)

Nov 21 (from Carol):: revised and uploaded ; file ends in 20211121_CM Note: re last issue on list re COURSE UNIT - I could not unprotect A5 to change what was populated there