|Active||Whether the job is active or inactive. Jobs can be activated/deactivated by Ex Libris staff only (although some jobs can be scheduled by library staff).|
|Name||The job name.|
|Job Category||A job category.|
|Creator||The user who scheduled the job. Jobs scheduled by Alma are indicated with a hyphen (-).|
|Schedule||How often and when the job is scheduled to run (for example, every day at X time).|
|Next Run||The date and time of the next run of this job.
The time is set according to the time zone of the Alma Data Center that is closest to your institution.
- Configure email notifications that are sent after the job runs (Email Notifications). For more information, see Configuring Email Notifications for Scheduled Jobs.
- View completed runs of the job (Job History). For more information, see Viewing Completed Jobs.
|PO Line - Packaging||Yes||Acquisition||Packages PO lines that are waiting for auto packaging into purchase order (POs) that may be sent to the vendor. For details on PO line packaging, see Packaging PO Lines into a PO.
This job is relevant only for automatic PO line packaging. Ex Libris must enable this job in order for PO lines to automatically be packaged into POs.For more information and scheduling options, see Configuring Acquisition Jobs.
The e-mail generated from the "PO Line - Packaging job" will not be sent to the operator if there are no PO lines to package.
|PO Line - Renewal||No||Acquisition||Renews subscriptions for both electronic and physical material, such as magazines, journals, or periodicals. For more information about the renewal workflow, see Renewal Workflow.
Ex Libris must enable this job in order for PO lines to be renewed.Each day the system checks for all PO lines whose status is Recurring Renewal and whose renewal date is equal to the current date. The renewal date is calculated as the renewal date (according to the PO line) minus the renewal notification period.
Renewals are processed as follows:
|PO Line - Claiming||No||Acquisition||Generates claims for PO lines whose associated resources have not yet been received or activated. For more information about claims, see Processing Claims.
Ex Libris must enable this job in order for claims to be generated.
|EDI - Load Files <vendor name>||Yes||Acquisition||File data should be in EDI format, and if not, the file will fail to load yet will still be attached to the vendor record. For more information, see Electronic Data Interchange (EDI).
You can run this manually on a single EDI invoice file; see Creating an Invoice From a File.
|Trials - Start and Notify Participants||No||Acquisition||Starts a trial and notifies the participants that the trial has begun. For details, see Evaluation Workflow. The notification sent to participants is the Trial letter. For more information on the letter, see Configuring Alma Letters.
Ex Libris must enable this job in order for trial participants to receive notifications.
|PO Line – Deferred||No||Acquisition||Adds an alert to PO lines that are deferred. The alert is based on the deferral reminder date that was set when the PO line was deferred. See Deferring PO Lines.|
|Recalculate Transactions Exchange Rates||No||Acquisition||When this job runs, transactions created in the last 30 days are updated according to the exchange rate that was applicable at the time of the transaction.
When Explicit Ratio is set for a transaction, the rate used is defined at the time of invoicing; these transactions are not included in this job.
By default, this job updates the exchange rates and transaction amounts of PO lines whose transaction date is in the last 30 days. The job updates the exchange rate and transaction amounts for all active transactions (both encumbrance and expenditure) if the exchange rate date is greater than the transaction date.
This job updates only transactions with incorrect exchange rates and is unrelated to the job Recalculate PO Line Encumbrances Based on Current Exchange Rates (see Configuring Explicit Exchange Rates).
|PDA - Alert PDA Reached Threshold||Yes||Acquisition||Sends notifications when funds for a patron-driven acquisition program are entirely expended; customers can suppress publishing the patron-driven acquisition until the program’s funds are replenished. The notification sent is the PDA Threshold letter. For more information on the notification letter, see Configuring Alma Letters.
For more information about pausing the patron-driven acquisition program, see To pause a PDA program.
|Recalculate PO Line Encumbrances Based on Current Exchange Rates||No||Acquisition||
Updates encumbrances and fund balances based on current exchange rates. This is only relevant for open encumbrances (not yet entirely matched with equal or greater value disencumbrances), and where the encumbrances' currency is not the same as the fund's currency. See Managing Funds and Ledgers.
This job is impacted by the recalculate_fund_transaction_with_explicit_exchange_rate customer parameter (see Configuring Other Settings).
This job is inactive by default.
This job is unrelated to the job Recalculate Transactions Exchange Rates; if this jobs runs successfully, there will be no problematic transactions for the job Recalculate Transactions Exchange Rates to correct.
|Notify E-Activation Due Task||No||Acquisition||Sends a notification, Notify E-Activation due Letter, to the assigned operator when an electronic activation task’s due date has passed. For more information about this due date, see Managing Electronic Resource Activation.
To configure the notification, see Configuring Alma Letters.
|ERP Export Using Profile <integration profile>||Yes||Acquisition||When defined as a profile, sends invoices to an Enterprise Resource Planning (ERP) system. For more information, including scheduling, see Financial Systems.|
|ERP Import Using Profile <integration profile>||Yes||Acquisition||When defined as a profile, receives payment confirmations from an Enterprise Resource Planning (ERP) system. For more information, including scheduling, see Financial Systems.|
|Update Fund Tx Job||Yes||Acquisition||Loads fund allocations for an Enterprise Resource Planning (ERP) system. For more information, including scheduling, see Financial Systems.|
|Sushi harvesting job||No||Acquisition||Harvests all COUNTER data from all active SUSHI accounts. See Managing SUSHI Harvesting.|
|Import PO Approvals||Yes||Acquisition||Loads POs after an Enterprise Resource Planning (ERP) system adds ERP numbers to them. For more information, including scheduling, see Financial Systems.|
|Distribute Network Acquisition Changes to Members||Yes||Acquisition||Distributes new vendor information and/or centrally managed licenses that were added to a Network Zone to member institutions since the date in the acq_distribute_changes_last_run parameter. For more information, see Jobs for Centrally Managing Configurations and Profiles in the Network Zone.|
|PO Line - Delete interested users||No||Acquisition||Runs weekly to delete interested users that are linked to closed or canceled PO lines. The job checks that an interestedin letter was sent to the interested users before removing it from the PO Line. Interested users will not be removed from a closed or canceled PO line if a letter was not sent to them. See Manually Creating a PO Line.|
|Configuration - Run HealthCheck tests on the system||Yes||Administration||Allows Alma administrators to identify whether any issues exist with their configuration. See HealthCheck Tool for more information.|
|Institution Recommendations Job||No||Administration||Generates general recommendations not produced by other jobs|
|Smart Recommendation Reflection Job||No||Administration||Cleans up irrelevant recommendations|
|Feature Recommendation Job||No||Administration||Generates recommendations for customer to use new features of Alma|
|Generate Recommendations based on Analytics reports||No||Administration||Generates recommendations that are based on analytics reports|
|Recommendations on jobs||No||Administration||Monitors Student Information System (SIS) jobs and Metadata Import (MD Import) jobs for the No Job Instance, Job Failure, and No Data Processed recommendations.
In the job report, the following information is displayed:
|No||Analytics||Processes all scheduled reports and dashboards, and distributes them to their subscribed users. See Running Analytics Reports and Displaying Them in Alma.
There are two jobs each for daily, weekly, and monthly processing. This enables staff users to schedule dashboards and reports to run at a time that coincides with the completion of the ETL process.
|Analytics Usage Tracking||No||Analytics||Collects usage of Alma Analytics in the institution. This is then reflected in the Analytics Usage Tracking subject area. For more information, see Analytics Usage Tracking.|
|Generate Recommendations based on Analytics reports||No||Analytics||Generate the DARA recommendations that are based on Alma analytics reports. For more information, see DARA – Data Analysis Recommendation Assistant.|
|Export Context object to BX job||No||Data Services||This job shares Alma Link Resolver data statistics with the bX community to enrich bX's recommender service.
See Sharing Alma Link Resolver Data Statistics with bX for more information.
|Synchronize Changes from CZ||No||Data Services + Administration||This job synchronizes changes done in the CZ with your institution, for example, updates in the harvest URL for SUSHI vendors, portfolio, bibliographic record and authorities information, etc.
Any change to a Community Zone bibliographic record is automatically reflected in every institution that uses the Community Zone bibliographic record. For institutions that use records linked to the updated Community Zone record, the change is reflected in the institutional record after the Synchronize Changes from the CZ job finishes running.
For more information, see Last Updated from Community Zone.
For Primo and Primo VE, this job runs once daily to create/update the database category tree, which contains up to three category levels and appears on the Database Search page. This job processes all MARC records that are connected to an electronic collection for which the following are true:
For more information on configuring Database Search, see the relevant page for your environment:
If you are using DB categories and this job is not active, please open a Support ticket to have it activated.
|Creates Journal Categories File||No||Discovery||For Primo and Primo VE, the Creates Journal Categories File job runs once daily to create/update the categories/subcategories that appear in Journal Search. The system creates a maximum of three category levels.
For more information, see Configuring Journal Search for Primo VE.
If you are using Journal categories and this job is not active, please open a Support ticket to have it activated.
|Saved Searches Alerts||No||Discovery||Primo VE patrons may create queries and request weekly email alerts when their saved search includes new results. This process checks these queries and sends the results using the Saved Searches Letter.
These alerts include all records including those loaded directly into Primo VE.
|Update Non Preferred Terms||No||Discovery||
For Primo VE, when a bib record is connected to an Authority record and that Authority record was updated in the CZ, then this job updates the Primo VE index with non-preferred terms Authorities changes.
This job depends on an internal system process for updating the Institution Zone with relevant changes from Community Zone. This process brings in the non-preferred terms Authorities changes. This job cannot complete as long as that internal process is running.
|Requests - Handle Expiration Step||No||Fulfillment||Carries out the actions defined in Request Pickup Configuration, such as expiring a request, marking the requested item(s) as missing, or converting the request to a resource sharing request. For more information on configuring the rules, see Configuring Request Pickup Rules. If no rules are configured, the requested items are marked as missing.|
The Loan Status Notice letter must be enabled for this job to run correctly. Otherwise, the job will complete with errors.
|Notifications - Send Courtesy Notices and Handle Loan Renewals||Yes||Fulfillment||Manages loans whose due date minus the value of the auto_renew_loan_days parameter is less than or equal to the current date. For additional information and examples see Configuring Fulfillment Jobs.
Short term loans are also managed by the job. If the short_loan_courtesy_reminder parameter is set, a courtesy reminder is triggered based on the due date time less the value of that parameter. If the short_loan_overdue_reminder parameter is set, an overdue reminder is triggered based on the due date time plus the value of that parameter. For both notifications, the letter will be sent if the item was not returned, is not in Lost or Claim Return status, and the current due date time is the same as the due date time that was on the item when the reminder was triggered. The loan due date time can change due to a renewal, recall, or manual change of due date. See also Configuring Short Term Loans.
When an overdue letter is issued, if the short_loan_overdue_block parameter is set to Yes, an overdue block will be set for the patron.
When first running this job, or running it after a period of inactivity, the value of send_courtesy_notices_and_handle_loan_renewals_last_run needs to be manually updated to the day before the expected run date to prevent courtesy notices for loans with due date in the past.
|Notifications - Send Hold Shelf Reminders Job||Yes||Fulfillment||Allows you to send a reminder notification to the patron after a set number of days. This scheduled job sends out the letter On Hold Shelf Letter Reminder, and it is possible to configure how many days after being placed on the hold shelf the reminder will be sent, and whether the reminder will continue to be sent at the configured interval until the Hold Shelf expiry.
For information on configuring this job, see Configuring Fulfillment Jobs.
|Fulfillment - Handle Historical Archiving||No||Fulfillment||Appears only when scheduled. Archives completed loans, fines and fees, hold requests and resource sharing requests.
Active fines still retain links to item and loan information.For information on configuring this job, see the Anonymization job entry in Configuring Fulfillment Jobs.
|Notifications - Send Periodic Fulfillment Activity Report||Yes||Fulfillment||Sends periodic fulfillment activity reports to patrons with active loans and/or fees. The report includes information on both loans and fees. The report includes a maximum of 100 active loans. For information on configuring this job, see Configuring Fulfillment Jobs. For information on configuring this notification, the Borrowing Activity letter, see Configuring Alma Letters.
If this job completes with errors, this may be due to users not receiving the email sent, although the job ran successfully.
|Notifications - Send Due Date Reminders||Yes||Fulfillment||Sends the Overdue Notice letter to patrons to indicate that loaned items are due on the current date. Note that this letter does not include short loans: items which have a loan period defined by hours and were loaned and are due the same day the letter is sent. For details on these type of loans and for configuring the reminder, see Configuring Short Term Loans.
The Courtesy Letter is sent before this notice. For information on configuring this job, see the Overdue Notices job in Configuring Fulfillment Jobs.
This job can be configured to send daily reminders from the Handle loans field. For more information, see Configuring Fulfillment Jobs.
|Requests - Restore Temporarily Shelved Items||No||Fulfillment||Creates restore item requests on all temporarily shelved items whose due back date is the current day or earlier. This informs the circulation desk operators at these locations to restore the items to their permanent locations. For more information on this job, see Viewing Restore Request Jobs. For information on configuring this job, see Configuring Fulfillment Jobs.
These items may include:
|Requests - Recalculate after Inventory Update||No||Fulfillment||
Recalculates requests after changes to the inventory are made. As a result, requests may be canceled, converted to resource sharing requests, or have a different item attached.
For example, if an item’s policy changes or a request for the item can no longer be fulfilled due to the item having been added to the repository or deleted from it, marked as missing, or moved to a different owning library/location, and no other items can fulfill this request, the job cancels the request. If a second item is available according to its policies, the request is linked to the second item instead.
If an item is determined to be lost and the policy for a lost loan is Not Requestable, this job detaches the request from the item and cancels the request if no other items can be used for fulfilling the request.
If other items become available after the request's creation, the On Shelf request policy is ignored and the request is not canceled.
The system allows inventory to be deleted — and therefore any accompanying request to be canceled or transferred to another item — until the point at which the request reaches the hold shelf. At this point, the request and its associated inventory cannot be canceled/deleted.
This job processes inventory changes only for the last seven days.
This job can be activated and scheduled on the Fulfillment Jobs Configuration page. See Configuring Fulfillment Jobs.
The job affects requests made on the title level or requests made on the item level (if the item change was done in bulk by a change items job).
|Loans - Overdue and Lost Item||Yes||Fulfillment||Notifies patrons about overdue loans and/or changes a loan’s status to lost according to the configuration for lost loan profiles. May be configured to send a single overdue or lost item notification to the patron listing all of the patron's overdue or lost loan. Configured as such, the patron receives a single notification for each notification type.
For information on configuring lost loan profiles, see Configuring Overdue and Lost Loan Profiles. For information on lost loan management, see Lost Loan Management. For information on configuring this job, see Configuring Fulfillment Jobs.
To configure the notifications Ful Overdue and Lost Loan Letter and Ful Overdue and Lost Loan Notification letter, see Configuring Alma Letters.
|Fines/Fees Notifications||Yes||Fulfillment||Generates email and/or SMS notifications to patrons of outstanding fines and fees. For information on fines/fees notifications, see Sending Patron Notifications for Fines and Fees. Letters are based on the Ful Fines\Fees Notification letter. For information on configuring letters, see Configuring Alma Letters. For information on configuring this job, see Configuring Fulfillment Jobs.|
|Send Overdue Message to Resource Sharing Borrowing Partner||No||Fulfillment||
Labels lending requests as Overdue when a request’s due date arrives and the request's status is not one of the following: Deleted, Canceled, Rejected, Expired, Returned by Partner.
The job is working with Email, ISO, SLNP and NcipP2P partners. The job automatically issues notices to borrowing libraries when a lending request is marked as Overdue. When working with an ISO or ISO18626 partner, the job updates the borrowing institution with the request’s Overdue status.
If the partner has defined a "Resending Overdue Days Interval" in the Parameters tab, overdue messages will be resent every configured number of days (for the parameter, see ISO Parameters). If an active borrowing request cannot be found, the overdue message is only sent once, rather than each time the job runs.
The letter that is sent to the borrowing institution is the Borrower Overdue Email letter. This letter must be active for overdue messages to be sent successfully to NcipP2P partners.
|Activate/Deactivate Courses||No||Fulfillment||Changes the statuses of courses to be aligned with their start and end dates. When activating courses, this job republishes all bibliographic data with the course data. When deactivating courses, this job republishes all bibliographic data without the course data.
Automates the reading list status for a course while it is either Active or Inactive. When multiple courses use the same reading list, this job is performed on the reading list as follows:
This job also updates bib records that are added after the start of the course.
For detailed information on courses, see Managing Courses.
|Users - Remove Blocks||No||Fulfillment||Removes expired blocks from user records.
This job determines whether suspended users fulfilled their suspension period, and if so, the user block is lifted. For demerit blocks, the job checks whether users exceeded the configured demerit threshold while on suspension, before removing the block. For more information, see Configuring Demerits. For information on configuring this job, see Configuring Fulfillment Jobs.
|Expired Resource Sharing Requests||Yes||Fulfillment||Checks for resource sharing requests that expired. The expiration date was automatically communicated by the borrower in the borrowing request. The request expires on the lender side, and the borrower is automatically notified about the expiration. In response, the borrower activates the next partner in the rota.
This job runs on requests that have an expiration date in the past, and which contain one of the following statuses:
When the job runs and detects expired requests:
When the borrower receives the Expired ISO message, it activates the next partner in the rota. If there is no additional partner in the rota, the request is expired.
|Distribute Central Resource Sharing Configuration||Yes||Fulfillment||Distributes the following among all institutions in a Network Zone:
For more information, see Jobs for Centrally Managing Configurations and Profiles in the Network Zone.
|Email Leganto Notifications to Users||Yes||Fulfillment||Appears only if Leganto is enabled for your institution. Emails instructors with a link to Leganto when there are notifications waiting for them. The email letter is Leganto Notifications Letter. For information on configuring letters, see Configuring Alma Letters.
To configure this job, see Configuring Fulfillment Jobs.
|Requests - Send Report||Yes||Fulfillment||Generates one letter per patron detailing all requests by status: Not Active, In Process, and On Hold Shelf. The letter is Ful Requests Report Letter. For information on configuring this job, see Configuring Fulfillment Jobs. For information on configuring letters, see Configuring Alma Letters.|
|Update BLDSS Requests||No||Fulfillment||
Activate in order to receive status updates from the British Library. The job retrieves updates posted by the British Library on their server. The job appears twice in the scheduler. If both are activated, status retrieval is done twice a day. For more information, see British Library Document Supply Service (BLDSS).
For information on activating/deactivating or manually running this job, see Configuring Fulfillment Jobs.
|Document Delivery Files Cleanup||No||Fulfillment||Removes files that were delivered digitally after they have been accessed by the patron, As determined by the Maximum Views parameter. See Adding A Digitization and Copyright Rule.
Document Delivery Files Cleanup job is not visible to users, including in the Job history.
|CCC Synchronize (Leganto only)||No||Fulfillment||Appears only if Leganto is enabled for your institution. Synchronizes data with the CCC. See Clearing Copyrights Through the Copyright Clearance Center (CCC).|
|UPDATE_READING_LIST_SCORE (Leganto only)||No||Fulfillment||Appears only if Leganto is enabled for your institution. Updates scores for the Reading List Advisor. See Managing the Reading List Advisor.|
Considers all expired booking requests that are not in Failed, Rejected, or Completed statuses. The job runs daily by default. Each of the requests that meets the criteria will be canceled and anonymized according to the institution's request anonymization configuration. If a purged request fee has been configured, the job applies the fee.
|DCS Synchronize||Yes||Fulfillment||Updates the status of DCS requests for citations every six hours. See Attaching a Citation to the CLA Digital Content Store.
To configure this job, see Configuring Fulfillment Jobs.
|Resource Sharing Completed Request Cleanup||Yes||Fulfillment||Enables you to remove requests from the resource sharing task list based on the request status and the number of days since the request reached a final status.
Final statuses for borrowing requests are:
Final statuses for lending requests are:
Any request that is in one of the statuses above and is in the range of the request age (based on the request modification date) will have its status changed to Deleted. Not selecting ‘number of days’ means all requests that match the selected statuses are removed, regardless of when the request was completed. Deleted requests will not appear in the active and completed task lists. After the request is deleted, it is viewable only in analytics.
|Clean logical deleted lists job||Fulfillment|
|Course copyright change||Fulfillment|
|Bolk synchronize||Fulfillment||This job can be enabled to check Bolk's status and update the status in Leganto accordingly. The default setting for this job is disabled.|
|ReShare Updates Job||Fulfillment||Rapido creates a ReShare ID so that both Rapido and ReShare stay in sync. When configuring the ReShare credentials, the job runs every four hours and is enabled automatically upon configuring ReShare.|
|Metadata Import w/ <import profile>||Yes||Import||
Imports bibliographic records for import profiles that use FTP. For more information, see Configuring New Import Profiles.
When the OAI Import Profile fails due to socket timeout exception, the system loads into Alma the number of records that it was able to import up to the moment of exception. If reconnect attempts are unsuccessful, the system saves the resumption token and attempts to use it in the next session of the job, resuming import from the resumption token.
|Yes||Publishing||Publishes institution or Network Zone records to Primo, Primo Central, or CDI. For more information, including scheduling, see Publishing to Primo, Publishing Bibliographic Records to Primo When Working with a Network Zone and Publishing Electronic Records to Central Discovery Index.|
|Publishing RSS Feed <profile name>||Yes||Publishing||Publishes RSS feeds. For more information, including scheduling, see RSS Publishing.|
|Publishing Platform Job <profile name>||Yes||Publishing||
Publishes records according to the configuration of general profiles. For more information, including scheduling, see Publishing and Inventory Enrichment.
Note that if the publishing process fails, all the records that did not publish will be published by the next publishing process.
|Publishing to Google Scholar||Yes||Publishing||Publishes records to Google Scholar. For more information, including scheduling, see Publishing Electronic Holdings to Google Scholar.|
|Yes||Publishing||Publishes bibliographic/holdings records and embedded holdings to OCLC. For more information, see Publishing to OCLC.|
|Publish Records to PubMed||Yes||Publishing||Publishes bibliographic records to PubMed. For more information, see Publishing to PubMed..|
|Upload Holdings to Libraries Australia||Yes||Publishing||Publishes records (all, or updates) marked to be published to Libraries Australia (by the job Synchronize MMS with National Catalog)
For configuration and scheduling information, see Libraries Australia Publishing Profile.
Publishing to Summon
Publishes bibliographic records to Summon. This job is scheduled with the Publish bibliographic records to Summon publishing profile. See Publishing Records to Summon for more information.
Sets the availability of electronic collections according to their activation start and end dates. For more information, including configuration, see Activation Tab Options.
|MMS - Build Record Relations||No||Repository||Creates relationships between MMS (bibliographic) records. See Using the MARC Linking Fields for Related Records for more information.|
This job is used when importing local authority records or updating local authority records in the MD Editor.
This job is also used to process automatic ID changes for institutions configured for ID-based authority control and that have implemented a Direct ID Prefix in their metadata configuration. See the Updating the Authority Record ID Automatically in Bibliographic Records section for more information.
In cases where this job runs and the system finds more than 10,000 bibliographic headings linked to one authority record, a new indexing job called Authorities - Handle non preferred indexing of Local Authority Record <job ID of the related "Authorities - Handle Local Authority Record Updates" job> is automatically triggered to handle the non-preferred term indexing. This helps to improve performance for completing the job.
|Authorities - Link BIB Headings||No||Repository||Links bibliographic headings to matching authority headings (preferred and non-preferred), giving priority to local authorities, if enabled. Bibliographic headings that are linked to non-preferred authority headings are marked for preferred term correction.
Processing is handled in the following manner:
|No||Repository||Updates bibliographic data fields that were marked for preferred term correction by the Authorities - Link BIB Headings job. See Authorities – Link BIB Headings in this table.
When the Authorities – Preferred Term Correction job is run, the order of the subfields is corrected when the bibliographic headings match the non-preferred term correction.
When the Authorities – Preferred Term Correction job is run, the order of the subfields remains unchanged if there is no data field correction.
Note that there is a configurable customer parameter that controls how punctuation is handled when a bibliographic record is updated by headings information (see add_punctuation_for_heading).
For more information, see Working with Authority Records.
The best practice for following authority record updates is working with the Authority Control Task List (see Using the Authority Control Task List for more details).
Builds the Did You Mean (DYM) index, which allows Primo VE to provide search suggestions to users. For more information, see Did You Mean.
This job is only visible to users with the "implementer" role.
|Inventory Remote Storage Update - <integration profile>||No||Repository||Updates remote storage when changes in the remote storage inventory are registered in Alma, such as changes to an item's metadata or addition/removal from the ASRS database.|
|Delete Draft Deposits||Yes||Repository||Deletes all deposits in draft. For more information, see Configuring the Delete Draft Deposits Job.|
|Yes||Repository||Sends an email to depositors that indicates the status of their active deposits.
For more information, see Configuring the Deposit Activity Report Job.
|Upload electronic holdings - SPRINGER||Yes||Repository||Downloads your Springer holdings files.
This can be scheduled to run automatically in order to keep the Springer targets in your portfolios up-to-date.
For information regarding the job report, see Upload Electronic Holdings - Springer.
For information about setting up the integration profile used in running this job, see Upload Electronic Holdings from Springer.
|Synchronize All Logical Collections||No||Repository||Updates all logical collections according to their set queries. Select a default collection in which to put all digital titles that do not have a collection after this job is run.|
|External Capture||No||Research||Esploro customers only, for future use.|
|Research usage statistics email job||No||Research||Sends email notifications to ETD authors and affiliated researchers with outputs that have been either viewed or downloaded in the past month. Authors who have opted out will not receive email notifications. If you want to change the job status (Active/Inactive/Run Now), see Research Jobs Configuration.|
|Update DOI Registration Agency - Research Assets||No||Research||Esploro customers only. Updates DOI agencies with any changes to assets. For more information, see Configuring DOI Agencies in the Esploro documentation.|
|No||Users||The Distribute network user management configuration changes job distributes changes made in the Network Zone for role profiles and role assignment rules to the member institutions.
See Distribute network user management changes to members for more information.
|Users <external action> Using Profile <integration profile>||Yes||Users||Performs an external action. For example, IMPORT or SYNCHORNIZE user information from external sources such as a Student Information System (SIS). For more information, including configuration, see Student Information Systems.
Appears if you have at least one Users type integration profile.
|Export to Bursar Using Profile <integration profile>||Yes||Users||Exports patrons fines and fees to the bursar system. For more information, including scheduling and configuration, see Bursar Systems.
Appears if you have at least one active Bursar type integration profile.
|Import from Bursar Using Profile <integration profile> Fines and Fees||Yes||Users||Performs the following actions:
|Letters Purge with Retention||No||Users||Deletes all attachments for letters listed in the Letter Retention Configuration table that were created prior to the retention date. Runs weekly. For more information, see Setting Letter Retention Periods.|
|User Audit Purge with Retention||No||Users||Deletes user history records that are older than the value specified in the retention period customer parameter. For information on setting the customer parameter, see Configuring Other Settings (User Management). For more information on user history retention, see User Audit History.|
|Publish research assets to Google||Yes||Research||(Institutions implementing Esploro, only)|
|Publish research assets to Google Scholar||Yes||Research||(Institutions implementing Esploro, only)|
|Retrieve API usage statistics for Analytics||No||Analytics||Internal job.|
|Global Success Rate||Yes||Administration||
Institution Zone (IZ) Success Rate:
Relevant only for COUNTER 4 usage.
UpdateSushiSuccessRate_IZ - this job will check the success rate of every SUSHI_VENDOR_ACCOUNT and will update the relevant fields in SUSHI_VENDOR_ACCOUNT table. The job will check in the harvest and harvest history how many processes were totally executed and how may were loaded successfully and will calculate the success rate accordingly. The job will ignore the processes that their severity is "Warning" or "Info" and will consider only those that their Error severity are "Error" or "Fatal" according to the new mapping table.
For each SUSHI vendor :
Community Zone (CZ) Success Rate:
The global success rate is defined as the number of successful processes per total executions for a certified vendor. This can give a global picture of this vendor and how the SUSHI processes run and may help the institution to verify if an issue is due to a Vendor's problem or Alma or the connection between them.
The success rate will be saved in the CERT_SUSHI_VENDOR entity which is a CZ entity and for each SUSHI Vendor with the same ORIGINATING_ID it will be distributed to the local environment.
This is done by a process automation that is executed per certified SUSHI vendor in the CZ and will search the vendor in the local IZ by ORIGINATING_ID.
|CZ Harvesting Primo Ve Indexing||No||Administration||
This job is complementary to the CZ Community Zone Harvesting (Synchronize Changes from CZ) job. Its objective is to improve the CZ harvesting synchronization process.
The job is monitored by Ex Libris on an ongoing basis and does not require any action from Alma users.
|CZ Harvesting AuthIndexing
|No||Administration||CZ Harvesting AuthIndexing job is one of the CZ synchronization jobs. Part of the 'Synchronize Changes from CZ' job is to update Authority Records. A change in Authority Records can trigger indexing in any bibliographic records linked to the updated Authority Record.
The ' CZ Harvesting AuthIndexing' job is responsible for handling the indexing for any bibliographic record linked to an Authority record that was updated by the 'Synchronize Changes from CZ' job.
- General System Administrator
- On the Monitor Jobs page (Admin > Manage Jobs > Monitor Jobs), select Email Notifications in the row actions list on the Scheduled tab for the job whose email notification you want to configure. The Email Notifications for Scheduled Jobs page appears.
- Select Add User to configure email notifications to be sent to users. The following pane appears.
- In the User text box, enter or select the Alma user to whom you want email notifications sent.
- Select Send on success to have an email notification sent when the job completes successfully and select Send on error to have an email notification sent when the job does not complete successfully.
Successful completion of a job does not mean that the job did not produce errors. Rather, it means that the job completed with the status of Completed Successfully (as shown in History tab of the Monitor Jobs page).
- Select Add and Close.
- Select Add Email Address to configure email notifications to be sent to any email address (follow the steps described above).
- After you have completed configuring the email notification recipients, select Save.