Running a batch update can be deceptively simple. The real work is to make sure you’ve appropriately scoped and planned out your update to avoid unintended consequences. Only designated staff members listed on this page should run specific jobs: Jobs & Batch Processes
Most Alma jobs require a set as an input, with the exception of Import Profiles. You should be very well-versed in Set creation, including the various methods to do so. If you need a refresher, visit Sets.
In Alma, a job is “a scheduled, invoked, or on-request process that runs in the background.” They are called jobs or processes in different places in the system, but they refer to the same thing.
There are three major types of jobs:
This documentation focuses on manual jobs.
Critical Information on Permissions and Effects
A very big note: Alma login permissions are not granular. The new authorizations added to your login allow for other functionality, but we trust you will only perform actions for which you have received approval from LTS.
Although Alma has a great UI to allow for batch work), it is deceptively reassuring. We have heard anecdotes from other Alma customers that staff with a lot of experience in batch load and update processes have used an incorrect input file or norm rule and caused great harm to their catalog, including deleting the entire database. Please stick to the guidelines in this documentation, and only use jobs for which you’ve been approved.