Alma jobs allow running batch processes on a large number of entities. The jobs run in the background, without impacting the day-to-day work of the library staff. To maximize efficiency, the system constantly performs optimization and prioritization of the running jobs in order to make sure that each job gets enough resources to complete. In addition, some jobs can run in parallel (Multi-threaded) – the job population is split into parts that can run in parallel to each other. Before a job is executed, it is examined by the system to check whether any dependent jobs or other instances of the same job are currently running.
For information, watch Applying Changes to Batches of Records in Alma (Jobs) (06:00).
Alma supports the following job types:
- Scheduled Jobs – Scheduled jobs run periodically. Some of these jobs are scheduled by Alma. For other jobs, you can configure the schedule using predefined job scheduling options. Note that scheduled jobs run as close as possible to their scheduled time. A job may wait until other jobs are done and the system has enough available resources.
In addition to their scheduled run times, Alma provides the ability to run some of these jobs at any time. For example, you can run an import job on demand (see Running Import Profile).
- Workflow Jobs – Workflow jobs run automatically when they are required. For example, after submitting a purchase order, the job Export Orders (PO) Job runs to send the PO to the vendor. In some cases, you can also run or rerun these jobs at any time—for example, if the original run failed.
- Manual Jobs – These jobs are available to run by you as required. Some manual jobs first require you to create sets (of items, users, and so forth) for the job to process. To run manual jobs, see Manual Jobs.
- Jobs are sometimes called processes in the UI.
- Some Alma jobs are dependent on other jobs due to the fact that they modify the same data. A job can also modify data that has a relationship with data updated in other jobs. To prevent these jobs from failing due to simultaneous data use, dependent jobs are scheduled to not run at the same time.
The following dependent jobs wait till the completion of the job they are depended on with the status 'Pending', and start running after that job completion: Authorities - Link BIB Headings, Authorities - Preferred Term Correction, Authorities - Handle Local Authority Record Updates, MMS - Build Record Relations.
Configuring Jobs by Use of Profiles
- Integration Profile – Creates a job that exports information to, or imports information from, an external system, such as a Student Information System. For more information, see Configuring Integration Profiles.
- Import Profile – Creates a job that imports bibliographic or authority records into Alma, and may also import purchase order or inventory information. For more information, see Record Import and Monitoring Import Jobs.
- Publishing Profile – Creates a job that exports bibliographic records from Alma to an external system, such as Primo or Google Scholar. For more information, see Configuring Publishing Profiles.
- To view scheduled jobs, see Viewing Scheduled Jobs.
- To view running jobs, see Viewing Running Jobs.
- To view job history and reports, see Viewing Completed Jobs.
The option to Abort a run job is further described in Viewing Running Jobs.
Network Zone Perspective
Each job running by an institution can be monitored from the Network Zone. When viewing the jobs from the Network Zone, an option to filter on a specific institution is available. When this option is selected, only jobs of the specific institution will be visible. The Network Zone cannot execute a job on behalf of an institution.
Some jobs have dependencies with related jobs (for example, the Bibliographic Heading Correction job cannot run when the Linking job is running) or with other instances of the same job (for example, the Loan Anonymization job), which means they cannot run at the same time. The job will be finished with a message that it cannot be executed when the other job is in process. For jobs that are scheduled by the system, the time scheduling of these jobs is set up to minimize overlapping.
Expected Job Duration
|Batch Service||Records Per Hour (Peak)||Records PerHour (Off-Peak)|
Note: The different profiles of metadata import may influence the time the service takes. For example, an EOD import profile will on average take longer than a bibliographic only update.
|Global Changes – MARC Bibliographic Normalization||50k||200k|