Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

SPIKE: Decide on scheduling approach for circulation

Description

In order to support changes like periodically anonymize loans (see ) or expiry of requests (see ) either mod-circulation needs to implement a scheduler, use an external scheduler or another modules needs to adopt these responsibilities (e.g. mod-circulation-storage, see my comment here https://folio-org.atlassian.net/browse/CIRC-132?focusedCommentId=112817&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel )

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Jakub Skoczen October 11, 2018 at 9:42 AM

Adding and who may have some ideas related to the workflow work.

Jakub Skoczen October 11, 2018 at 9:41 AM

Guys, we need to make some progress here, at least in terms of making decisions about the approach/design.

I see two different ways:

  • we rely on module internal scheduling similarly to what we have done for user expiration. can provide the details (please do it here so other guys can get an idea). RMB comes with some rudimentary DB polling/scheduling support, which we may need to extend.

  • we build a dedicated module for scheduling (something along the lines of mod-cron) this module would be able to trigger arbitrary requests in FOLIO at specified schedule. I think on the surface this is simple but once we get into error handling and logging, this gets complicated.

Thoughts?

Details

Assignee

Reporter

Labels

Priority

Development Team

Core: Platform

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 29, 2018 at 4:11 PM
Updated February 5, 2019 at 8:09 PM
TestRail: Cases
TestRail: Runs