Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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 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 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

...

Note: Insight into amalgamating St. Clair’s two Centriva databases into one IZ may be gained from this ExLibris Knowledge Center link: Combining Source Databases into One Alma Institution

 

Data cleaning hindsight - past experiences for review

Notes from Novanet

https://www.novanet.ca/adventures-in-alma-issue-2/

Cleanup Progress

The Advisory Group and members of the Acq, Cat and Access Service groups have been busy with the first round of Aleph Cleanup. As you’ll recall, the purpose of this work is to do as much as we can to the data in Aleph so that we’ll have less cleanup to deal with when we start on Alma.

Current cleanup projects include:

  • Barcodes that cannot be searched or scanned in Aleph (and probably Alma) because they contain symbols, spaces and other oddities.

  • Collections with multiple item statuses, these need to examined and edited so there is one collection per item status.

  • No Collection – item records without collection codes

  • Item Process Status report – these will be reviewed to identify item process statuses no longer in use and clean up records that have old item process statuses that may need to be removed or changed.

Clean up projects on the horizon:

  • Suppressed records clean up – we’ve learned that suppressed records in Aleph can be migrated to Alma but we need to identify if there suppressed records that do not need to be retained.

  • Unclosed Orders – Acquisitions Service Group are identifying what order statuses are used for closed order. We will then produce a report for all these orders for review.

  • Electronic/print records split – We are working on identifying bib records that have both electronic and print items.

Posted on November 27, 2020 by Bill Slauenwhite

Work resumed in September and the small working groups, lead by the Implementation Advisory Group, have started meeting again. They have been busy cleaning up things collection codes, old orders, separating print and electronic holdings, fixing record formats and the like. A full list of cleanup jobs in the queue and those that are completed can be seen at: https://www.novanet.ca/clean-up-reports/