Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-1953

SPIKE: propose an approach for scheduling tasks in Okapi

    XMLWordPrintable

Details

    • CP: sprint 62
    • 5
    • Core: Platform

    Description

      We currently only have the scheduling capability in the storage modules as provided by RMB. There is a need to have a scheduling capability also in the BL modules (e.g mod-circulation, please link the appropriate stories).

      Since BL modules have no persistence and may run in multiple instance we need a solution that will ensure the scheduling is coordinated (the scheduled event happens only once).

      Also, any scheduled activities needed to be granted permissions to interact with other module endpoints.

      DRAFT PROPOSAL

      One option is to do scheduling in Okapi;

      • extend the module descriptor with a a new "handler" type that would also include a property that would indicate to Okapi that the handler should be called periodically (e.g "tick" = minute,quarter,hour) (should this really be part of the tenant API?)
      • have Okapi elect a designated scheduling instance that will call the "handler" and ensure the handler is called only once
      • have the scheduling Okapi instance call the "handler" with a token that include permission reported though modulePermissions.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Task - A task that needs to be done. FOLIO-1786 SPIKE: evaluate "init" tokens as a way to trigger system tasks

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Draft

            New Feature - New feature requests UXPROD-1586 Send patron notices for time based loan events, such as due date/time (i.e., courtesy notices and overdue notices) via email

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-1587 Send patron notices for time based request events, such as hold expiration or request expiration via email

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-1636 Make Hold Shelf Expiration Date Respect Closed Library Days/Hours

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done before

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-292 Set Item Status to "Pickup expired" when "Awaiting pickup" Item Expires or is Cancelled

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-133 Request Expiration Job Takes Too Long for Short Term Expiry Periods

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-246 Hold Shelf Expiration Date Should Respect Closed Library Dates

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-82 Automated Patron Blocks

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-87 Loan: Aged to Lost using SET COST

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-105 Future Fees/Fines: Update current automated transfer process for fees/fines to bursar or other account that works for all sites

            • TBD - To be determined
            • Closed

            New Feature - New feature requests UXPROD-499 Future Fees/Fines: Collections agency interactions: when patron still pays library

            • TBD - To be determined
            • Draft

            New Feature - New feature requests UXPROD-527 Loans: Recently returned

            • TBD - To be determined
            • Draft

            New Feature - New feature requests UXPROD-1085 Automatically Anonymizing/Scrubbing Loan Data (through Settings)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-1858 Future Fees/Fines: Collections agency interactions - when patron pays agency

            • TBD - To be determined
            • Draft
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-272 [SPIKE] Investigate scope of work for sending time-based patron notices

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FOLIO-889 Develop a strategy to implement scheduled (cron-like) events

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. FOLIO-2010 Alternative Scheduling Approaches

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSENDER-8 [SPIKE] Investigate sending multiple messages at the same time.

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests OKAPI-730 system call timer

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            requires

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-272 [SPIKE] Investigate scope of work for sending time-based patron notices

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                adam Adam Dickmeiss (Inactive)
                jakub Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                15 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases