Note |
---|
We will continue adding new resources and recommendations to this guide as we learn more. Remember to check back regularly for new information, or start “watching” this page to receive a notification email whenever there are updates. To start watching this page, choose the “watch” icon in the upper right of your screen and select the relevant check box. To stop watching the page, deselect the relevant check box. |
...
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 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.
...
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 broader 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.
During 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: Visit 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.
Successful bibliographic matching in the Network Zone (NZ) is dependent upon accurate unique identifiers, such as SIRSI 035 | a; OCLC 035 | a, etc. 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.
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 Local Extensions (MARC) section of Alma Migration Considerations for Consortia
Ex Libris Knowledge Center 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.
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.”
Extraneous identifiers
Additional Data Preparations (Ex Libris):
...
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
...