• If the PO line is marked as automatic, whenever the renewal date arrives the job will automatically change the renewal date to the previous renewal date plus the time in the Renewal Cycle. The status of the PO line remains Recurring Renewal.
• If the PO line is marked as manual and the renewal date (minus the renewal notification period) arrives, the job will change the status of the PO line from Recurring Renewal to Waiting for manual renewal. The PO line will be displayed in the Renewal task list (Processing Renewals). The operator will then need to edit the PO Line to change the renewal date to a future date.
• In either case, a  PO Line Renewal Letter (see Configuring Alma Letters) is sent to the vendor if the po_line_send_notification_to_vendor_on_renewal parameter is set to true (see Configuring Other Settings).

• For one-time PO lines, the claim is sent automatically if the auto_claim customer parameter is set to Y.
• For continuous PO lines, the claim is sent automatically if the auto_claim_co customer parameter is set to Y. This is true whether the claim is sent with EDI or email.
• For electronic resources, the claim is sent automatically if the auto_claim_electronic customer parameter is set to Y.
• If the auto_claim_co parameter is set to N, a task is generated, but the claim is not sent. In this case, the claim must be sent manually.

In the job report, the following information is displayed:

• Total records processed: The number of jobs (SIS & MD Import) that the Recommendation loops over.
• Number of recommendation types skipped: The number of types that are disabled in the environment and therefore skipped (that have No Data Processed, Job Failure, or No Job Instance).
• Number of recommendation types failed: Currently not in use and will always display the value 0.
• Number of Job Failure recommendations created: The number of recommendations that were created for type Job Failure.
• Number of No Data Processed recommendations created: The number of recommendations that were created for type No Data Processed.
• Number of No Job Instance recommendations created: The number of recommendations that were created for type No Job Instance.
• Number of recommendations failed: The number of jobs that the Recommendation job failed to process and got an exception, such as when the job is not scheduled in the environment.
• IDs of failed jobs: When the recommendation job skips over the jobs (SIS & MD Import) and searches for jobs that ended with an error status, the process IDs are displayed in the report. 

• Schedule of Analytics Reports and Dashboards - Daily
• Schedule of Analytics Reports and Dashboards - Weekly
• Schedule of Analytics Reports and Dashboards - Monthly

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.

This job ensures the list of providers in the CDI configuration Provider preference order for CDI linking is kept up to date.
This configuration can be found in Discovery > Central Index and proxy set-up for Primo VE customers and also in Fulfillment > Discovery Interface Display Logic > Central Index for Alma/Primo customers.

Creates DB Categories File

No

Discovery

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:

• The electronic collection must have a Level URL or Level URL (Override) defined.

• The electronic collection's descriptive record must not be suppressed.

• The electronic collection's descriptive record must have one or more entries for the designated MARC field (as defined with the db_categories_field parameter on the Alma Customer Parameters page (Configuration Menu > Resources > General > Other Settings).

For more information on configuring Database Search, see the relevant page for your environment:

• Configuring Database Search for Primo

• Configuring Database Search for Primo VE

For more information, see Configuring Journal Search for Primo VE.

• If the conditions of an automatic loan renewal rule are met – performs automatic renew for an item.
• If the conditions of an automatic loan renewal rule are not met (and the loan is therefore not renewed) – sends a courtesy notice informing the patron that the item is due. One notice is sent per patron. For details on configuring automatic loan renewal rules, see Configuring Automatic Loan Renewal Rules.
• The Courtesy Letter is also sent if a block exists on the patron or item, preventing item renewal (see Configuring Block Preferences).

For information on configuring this job, see Configuring Fulfillment Jobs.

• Reading list items for a course that ended
• Items that were removed temporarily, such as a resource that was removed while a course was ongoing and the resource is now due to be returned

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.

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.

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.

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:

• Created Lending Request
• Being Processed
• Locate Failed

• An Expired ISO message is sent to the partner
• The resource request is canceled
• The request’s status is changed to Expired

• Resource sharing partners
• Rota templates
• Rota assignment rules
• Locate profiles
• Workflow profiles
• Sending borrowing request rules.

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).

Handle Expired Booking Requests

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. 

• If enable_booking_workflow = false – requests are handled by the handle expired booking requests job if not in status “FAILED”, “REJECTED” or “COMPLETED”, and the purged request fee is applied.
• If enable_booking_workflow = true – requests are handled by the handle expired booking requests job if not in status “FAILED”, “REJECTED”, “COMPLETED”, “PICK FROM SHELF” or “HOLD SHELF”, and the purged request fee is not applied. The fee will be applied when the item is removed from the hold shelf using the expired hold shelf workflow.

Final statuses for borrowing requests are:

• Canceled by partner
• Canceled by patron
• Canceled by staff
• Digitally received by library
• Expired
• Request completed - This is the final status before removal, and may be manually set.
  Make sure to select the statuses you would like to have removed. The job will clean up only the selected statuses.

Final statuses for lending requests are:

• Shipped digitally
• Request completed - This is the final status before removal and may be manually set.

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.

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.

• Publish bibliographic records to Primo
• Publish bibliographic records from Network Zone to Primo
• Publish bibliographic record from Network Zone to Primo - Implementation
• Publish electronic records to Primo Central
• Publish electronic records to Central Discovery Index

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 OCLC - Bibliographic Records
• Publishing to OCLC - Holdings Records

Publishing to Summon

Yes

Publishing

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.

Inventory - Electronic Package Activation/Deactivation

No

Repository

Sets the availability of electronic collections according to their activation start and end dates. For more information, including configuration, see Activation Tab Options.

Authorities - Handle Local Authority Record Updates

No

Repository

• The job searches all authority record fields, including subdivision fields, for complete terms listed in bibliographic records (giving priority to local authorities, if enabled).
• If exact matches are found, the bibliographic records are linked to the corresponding authority records.
• If more than one authority headings record match is found (a multi-match), the bibliographic headings record requires manual handling.
• If exact matches are not found, the subdivision fields are disregarded, a search of all authority records is performed once again, and the bibliographic records are linked to the matching authority records that are located during the second search.

Authorities - Preferred Term Correction

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.

• Library of Congress Name (LCNAF) 

• Library of Congress Subject (LCSH)  

• Library of Congress Children's Subject Heading 

• Library of Congress (LoC) – Genre/Form Terms Thesaurus Records 

• Library of Congress (LoC) – Medium of Performance Thesaurus for Music 

• FAST – Faceted Application of Subject Terminology – OCLC 

• NLM MeSH – United States National Library of Medicine 

• SpMaBN – National Library of Spain

Build ranking structures

No

Repository

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 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.

Distribute network user management changes to members

See Distribute network user management changes to members for more information.

• Search for the matching fine/fee record with the bursar transaction ID. If a match cannot be made, the hibernate ID is used.
• Create a new transaction with the Payment Imported type.
• Update the relevant fine/fee. If the payment is a full payment, close the fee. Otherwise, update the active amount. If the payment is an overpayment, create a credit.

Institution Zone (IZ) Success Rate:

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 :

• Get number of total load processes from usage_loaded_file_data (by the job ID) - TOTAL_LOAD.
• Get the number of jobs that completed successfully - SUCCEEDED_LOAD.
• Set the success_rate as SUCCEEDED_LOAD/TOTAL_LOAD * 100.
• This number will be gathered from all institutions and saved in the Global success rate in CERT_SUSHI_VENDOR.
• This number will then be distributed to the relevant institutions and will be saved.

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.

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.

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.