[FOLIO-1445] SPIKE: Decide on scheduling approach for circulation Created: 29/Aug/18  Updated: 05/Feb/19

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Marc Johnson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: core-spike, sprint49
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks CIRC-132 Backend Work for UICIRC-54: Anonymize... Closed
blocks CIRCSTORE-109 Implement request status "Closed - Pi... Closed
blocks UICHKIN-39 Status change upon check in: recently... Closed
blocks UICIRC-54 Automatically anonymize loan history ... Closed
Relates
relates to UXPROD-594 Scheduler Closed
Sprint:
Development Team: Core: Platform

 Description   

In order to support changes like periodically anonymize loans (see CIRC-132 Closed ) or expiry of requests (see CIRCSTORE-109 Closed ) 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 )



 Comments   
Comment by Jakub Skoczen [ 11/Oct/18 ]

Adam Dickmeiss Heikki Levanto Kurt Nordstrom 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. Kurt Nordstrom 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?

Comment by Jakub Skoczen [ 11/Oct/18 ]

Adding Jeremy Huff and William Welling who may have some ideas related to the workflow work.

Generated at Thu Feb 08 23:13:23 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.