Long Overdue Cron

Goal: $10,000

Raised: $10,000

Supporters: 0

Make a pledge

This enhancement request will move all the configuration options for the Long Overdue Cron into the staff side of Koha so that libraries can manage these settings on their own instead of needing someone to adjust them at the command line on the server.

Development

The development will create a new configuration page in the Administration area of Koha to allow libraries to set their configurations per branch for the long overdue process. New API routes will need to be created to allow Koha to get and set the rules. The rules will be set at the branch level, group level, or system level.

The current cron will still function with the runtime options however it will warn that the switches are to be deprecated and the new interface should be used.

Expected Outcomes

  • Add a new config page to the administration section
  • Add API routes for getting/setting rules
  • Utilize datatables API for displaying/editing rules
  • Allow for defining rules at the system, group, or library level
  • The cron switches will take precedence if set, but will warn of deprecation

Koha Community Enhancement in Bugzilla

Bug 18064 - Long overdue cronjob does not follow the library's calendar and skip closed days

Want to be a sponsor

Submit a request to dev@bywatersolutions.com to get the process started.