...

The recommendations below contain tips or suggestions for ways to tidy up your data before migration to Alma. This is not a ‘one size fits all’ guide – but a list of local considerations that you can begin to think about. Ex Libris suggests that local data cleaning may streamline the migration process and help to ensure to best possible outcomes. Read Getting Ready for Alma and Discovery Implementation, Appendix A - Fulfillment Simplificationto gain a fuller understanding. As you explore this information in the Ex Libris Knowledge Center, consider keeping the https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/120Alma_Glossary open in a new tab for quick reference.

Planning – Organization and Simplification of locations, patrons and item types:

Making sure that records and collections in your original source database are well organized is one thing you can do to ensure a best possible migration outcome. If there are small collections that no longer need to stand on their own, consider merging them into larger ‘locations’. Depending upon your system, you may choose to merge collections ahead of time OR simply choose to map two collections together upon migration. Note: In Alma, a location is defined as a “physical place where items are stored” that is “associated with a library.” Locationsthat have similar fulfillment (circulation) policies and blocks will become associated with your library’s fulfillment units.

• Consider categorizing locations into about five “location type categories” that share common circulation policies: For example: regular loan; limited loan, short loan/reserve, closed stack, and media.

• Ex Libris expects that most locations should fit into one of the above categories and recommends that libraries restrict the number of ‘item type’ circulation exceptions to five.

• The diagram below illustrates the relationship between the bibliographic record, libraries, holdings records, locations and item records.

  

• Visit https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/010Introduction_to_Alma_Inventory#Physical for additional information describing the relationship between ‘location,’ ‘holding’ and ‘item' in the institutional zone (IZ)

• Also consider amalgamating user groups that share common permissions

Tags and Identifiers:

To allow for clean migration, ensure collections are well identified. Consistent tagging is important for moving records from your source collection to Alma locations. From a consortium perspective, unique identifiers are essential for record matching in the Network Zone (NZ). In order to migrate your data:

...

It would be most helpful if all items belonging to a particular item group are consistently tagged with the same MARC field/subfield (e.g., subfield tag in 852 or 9XX). For some systems, this may best be accomplished upon export – other systems may need to have edits performed in advance.

...

Through the migration process, Ex Libris maps these MARC tags to an Alma “location” specific to your Institution Zone (IZ). The migration form used will depend upon your source system. For more information read the https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/Generic_Alma_Data_Delivery_and_Migration_Guide OR https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/Symphony_to_Alma_Data_Delivery_and_Migration_Guide.

Network Considerations:

...

Successful bibliographic matching in the Network Zone (NZ) is dependent upon accurate unique identifiers, such as SIRSI 035 | a; OCLC 035 | a, etc.

...

Data Preparations (Ex Libris)

The suggestions below are excerpts from Getting Ready for Alma and Discovery Implementation, Appendix B - Optional Data Preparations. This appendix can help you decide which clean-up efforts are a priority for your library – not everything will be relevant to all libraries. Examples of other data cleaning could work include:

• Library and collection identification tags:

• Bibliographic, holdings and item data

• Enumeration

• Statuses and codes (as discussed under #1 above)

• Old/inconsistent data (includes old patron records, fines beyond a certain date and/or less than a certain amount; etc.)

• Review of old, unclosed orders

• Library and collection names

• Patron, vendor, library contact names

• E-resource and package resources

Tags and Identifiers:

To allow for clean migration, ensure collections are well identified. Consistent tagging is important for moving records from your source collection to Alma locations. From a consortium perspective, unique identifiers are essential for record matching in the Network Zone (NZ). In order to migrate your data:

• It would be most helpful if all items belonging to a particular item group are consistently tagged with the same MARC field/subfield (e.g., subfield tag in 852 or 9XX). For some systems, this may best be accomplished upon export – other systems may need to have edits performed in advance.

• Through the migration process, Ex Libris maps these MARC tags to an Alma “location” specific to your Institution Zone (IZ). The migration form used will depend upon your source system. For more information read the https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/

  010Alma

  Generic_

  Migration

  Alma_

  Considerations

  Data_

  for

  Delivery_

  Consortia#Extraneous

  and_

  Identifiers_2. At the local level, Ex Libris recommends: “that the NZ use fields 900-949 and the IZ uses 950-999. This way the local NZ fields (900-949) are those that are local to the entire consortium where every institutional member uses them, and the local IZ fields (950-999) are those that are local

  Migration_Guide OR https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/Symphony_to_Alma_Data_Delivery_and_Migration_Guide.

• Network Considerations:

  • Successful bibliographic matching in the Network Zone (NZ) is dependent upon accurate unique identifiers, such as SIRSI 035 | a; OCLC 035 | a, etc.

  • Extraneous identifiers may interfere with proper matching. Suggestions from Ex Libris are addressed in https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/010Alma_Migration_Considerations_for_Consortia#Extraneous_Identifiers_2.

  • At the local level, Ex Libris recommends: “that the NZ use fields 900-949 and the IZ uses 950-999. This way the local NZ fields (900-949) are those that are local to the entire consortium where every institutional member uses them, and the local IZ fields (950-999) are those that are local only to the single institution. This is recommended because it is important to be able to retrieve groups of records based on data in specific local fields, and having the same local field used for two different data elements may cause problems in retrieval. During migration, if a 900-949 tag has $9 LOCAL subfield, it is removed and the tag is kept in the NZ.” For additional context, visit THE Local Extensions (MARC) https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/010Alma_Migration_Considerations_for_Consortia#Local_Extensions_(MARC) section of https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/010Alma_Migration_Considerations_for_Consortia.

  • Network Zone Resources:

    • https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/100Managing_Multiple_Institutions_Using_a_Network_Zone/01_Overview/01_Overview_of_Collaborative_Networks for an overview of Network Zone (NZ) functions.

    • https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/010Alma_Migration_Considerations_for_Consortia describes the process for providing and processing records into a shared consortial environment in Alma from various legacy ILS systems.

    • Videos to provide insight into functions available through the broader Network Zone (NZ): http://exl-edu.com/01_Alma/Alma_Collaborative_Networks_(Alma_Consortia)/Alma_Collaborative_Networks-Introduction/story_html5.html?lms=1 and http://exl-edu.com/01_Alma/Alma_Collaborative_Networks_(Alma_Consortia)/Shared_Bibliographic_Records_in_the_Network_Zone/story_html5.html?lms=1

    • https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/100Managing_Multiple_Institutions_Using_a_Network_Zone/Discovery_when_Using_a_Network_Zone provides insight into publishing records to Primo. According to https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/100Managing_Multiple_Institutions_Using_a_Network_Zone/Discovery_when_Using_a_Network_Zone/010Overview_of_Discovery_when_Using_a_Network_Zone, “availability and delivery for physical resources harvested from Alma are relative to the institution of the view.” 

Additional Data Preparations (Ex Libris):

The additional suggestions below are from Getting Ready for Alma and Discovery Implementation, Appendix B - Optional Data Preparations. This appendix can help you decide which clean-up efforts are a priority for your library – not everything will be relevant to all libraries. Examples of other data cleaning could work include:

• Library and collection identification tags:

• Bibliographic, holdings and item data

• Enumeration

• Statuses and codes (as discussed under #1 above)

• Old/inconsistent data (includes old patron records, fines beyond a certain date and/or less than a certain amount; etc.)

• Review of old, unclosed orders

• Library and collection names

• Patron, vendor, library contact names

• E-resource and package resources

  • • provides insight into publishing records to Primo. According to https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/100Managing_Multiple_Institutions_Using_a_Network_Zone/Discovery_when_Using_a_Network_Zone/010Overview_of_Discovery_when_Using_a_Network_Zone, “availability and delivery for physical resources harvested from Alma are relative to the institution of the view.” 

Electronic Resource Handling in Alma Migration:

...

Consider running past loan/usage statistics/analyses prior to migration, as only key fields/subfields will be migrated. More to come….

ExLibris Migration Resources - Getting Ready

...