Mapping Form Instructions & Tracking - Fleming College
- Liana Giovando
- Justin Johnston (Deactivated)
Overview
Download your Mapping Form from OCLS FTP.
Review these Mapping Form Instructions for your college.
Review and remove values from your Mapping Form as per these instructions.
Use the table on this page to track changes you make in your forms.
Save new file as “collegename_field_mapping_UNLOCKED_YYYYMMDD.xlsx” and upload to your college’s MFT folder with Ex Libris.
Advise Ex Libris your files are ready for review by updating the table on the Symphony Data Mapping & Migration Form.
Introduction
OCLS extracted and validated your files and provided your data files to Ex Libris already. Mapping and Migration Forms were created in the validation process based on the data files extracted. Most of the data in your Mapping Form has already been identified and mapped during this process.
Information without an equivalent mapping to Alma was mapped to a Note field. It is up to you to decide whether the information is useful to keep as a note. The instructions below relate the final step to remove notes from your form if you choose to do so.
Please note, when a Symphony field did not have an equivalent in Alma and only referred to functionality in Symphony, the OCLS approach was to mark ‘Do not migrate’. For example, ‘Y’ to display in OPAC or ‘1’ to turn on a feature in Symphony.
Instructions
Use the table below to identify tabs and cell ranges in your mapping form with notes and to record your changes.
Review
Please review the mapping form with special attention to the notes and decide what notes you would like to carry over in Alma. Use your data extracts found in OCLS FTP for reference to assist in decision-making.
Remove
Remove notes only. Cell ranges for notes are indicated in the table below. Delete values in each cell, not the row. That way you will keep the row numbering with no content. Do not edit other fields.
Record
Record any removals in the column below called “Removals”. We expect there will be information you want to remove from your Mapping Form but it is not likely you will find formation missing.
You must log in to Confluence and select the “edit” icon on this page to track removals in the table below.
Tab | Instructions | Notes | Removals (Please use this column to indicate if you have removed values from cells in this tab. Indicate Yes/No) |
|---|---|---|---|
Bib Items | No action needed | Defined by Sirsi | No |
Holdings | No action needed | No college has Marc Holdings | No |
Boundwith | No action needed | No college has boundwith records | No |
Serial Control for Issues | Look at NON_PUBLIC_NOTE. Remove anything you do not want to carry over. ** Could be cell ranges: B20-B32,C20-C32 but may differ depending on your data. | Keep in mind, notes are not attached to any functionality in Alma. They will appear all in one field, separated via pipe. | No |
Issues | Look at NON_PUBLIC_NOTE. Remove anything you do not want to carry over. ** Could be cell ranges: B17-B37, C17-C37 but may differ depending on your data. | Keep in mind, notes are not attached to any functionality in Alma. They will appear all in one field, separated via pipe. | No |
Patrons
| Look at LIBRARY_NOTE. Remove anything you do not want to carry over. ** Could be cell ranges: B103-B123, C103-C123 but may differ depending on your data. | Keep in mind, notes are not attached to any functionality in Alma. They will appear all in one field, separated via pipe. | No |
Patrons - ##User Identifiers | UNIV_ID, under ##ALma identifier type## should map to USER_ALT_ID under ##Symphony local field## Example  | UNIV_ID is mapped to USER_ALT_ID as recommended. | No |
Patrons - ##User Identifiers | BAR, under ##ALma identifier type## should map to USER_ID under ##Symphony local field## Example | BAR has been mapped to USER_ID as per the recommendation. | No |
Use the following mapping if you have additional user information in your current ILS. Statistical data is contained in the user category fields within Symphony. To map these cells, select the correct stat category label below and insert it into the matching field. USER_CATEGORY1 USER_CATEGORY2 USER_CATEGORY3 | |||
Patrons - ##Patron Statistical Categories
| The first field in USER_STAT_CATEGORY should be mapped to your Sirsi field that currently contains the most relevant program data. (For example, the default is USER_CATEGORY1, but if your college uses USER_CATEGORY3 for program data, change it. ) **Could be B98 but may differ depending on your data. | This isn’t required. We do not keep program data for students. | No |
Patrons - ##Patron Statistical Categories | Insert an additional row here if you have Faculty or School data to migrate. Include the Sirsi field name for that data here. | USER_CATEGORY2 is used for campus location. | No |
Patrons - ##Patron Statistical Categories | Insert an additional row here if you have specific department information for faculty data to migrate. Include the Sirsi field name for that data here. |
| No |
Patrons - ##Patron Statistical Categories | If there is something else that you currently have and you want it mapped, continue this process by adding rows. |
| No |
Blocks | No action needed |
| No |
Loans | Look at LOAN_NOTE. Remove anything you do not want to carry over. ** Could be cell ranges: B16-B19, C16-C19 | Keep in mind, notes are not attached to any functionality in Alma. They will appear all in one field, separated via pipe. | No |
Fines & Fees | Look at FINE_FEE_COMMENT Look at non-public notes. Remove anything you do not want to carry over. ** Could be cell ranges: B13, C13 | Keep in mind, notes are not attached to any functionality in Alma. They will appear all in one field, separated via pipe. | No |
Requests | Look at NON_PUBLIC_NOTE Remove anything you do not want to carry over. ** Could be cell ranges: B12-B13, C12-C13 | Keep in mind, notes are not attached to any functionality in Alma. They will appear all in one field, separated via pipe. | No |
Vendors | Only for those colleges that wanted Acquisitions Data Look at VENDOR_NOTE Remove anything you do not want to carry over. ** Could be cell ranges: B57-B62, C57-C62 | Keep in mind, notes are not attached to any functionality in Alma. They will appear all in one field, separated via pipe. | No |
Orders | No action needed (for now) |
| No |
Funds | No action needed (for now) |
| No |
Invoices | No action needed (for now) |
| No |
Hol Form Bib | No action needed |
| No |
Courses | Only for those colleges that wanted course data. Look at COURSE_NOTE Remove anything you do not want to carry over. ** Could be cell rages: B17-B18, C17-C18 | Keep in mind, notes are not attached to any functionality in Alma. They will appear all in one field, separated via pipe. |
|
Suppressed Bibs | No action needed |
| No |
Item Secondary File | No action needed |
| No |
P2E | No action needed | Your P2E items are processed in a separate file. | No |
Remember to save your new file as “collegename_field_mapping_UNLOCKED_YYYYMMDD.xlsx”, upload to your college’s MFT folder with Ex Libris, and advise Ex Libris your files are ready for review by updating the table on the Symphony Data Mapping & Migration Form.
Keep in mind that these Mapping Forms will be redone at cut-over. There will be an opportunity to make changes before cut-over.