Add rollover settings in the library / fiscal year / organisation

[pronguen]

How it works

Rollover issue

Currently, it is not possible to define settings for the rollover per library in RERO ILS.

Improvement suggestion

• Complete the library JSON schema to add the rollover_settings (see fields below)
• Adapt the library editor

Field needed in the section "Rollover settings"

• Transfer of the accounts (account_transfer)
  • Description: This defines if and how the accounts are transferred into the next fiscal year.
  • Required
  • Values enumeration (only 2 values for now)
    • Transfer with the allocated amount of the previous budget [default value]
    • No transfer (orders are not transferred either)
    • [for later] Transfer with no available amount (orders are transferred, the allocated amont is the sum of the engagements)
    • [for later] Transfer with the remaining balance of the previous budget
    • [for later] Transfer with the remaining balance plus the allocated amount of the previous budget
    • [for later] Transfer with no allocated amount (orders are not transferred)

Context

See overall rollover specifications: https://ncloud.rero.ch/s/mACKxzKZeDWeTGW

Other fields like name and period of the next fiscal dates are not stored in the library, but are asked dynamically at the moment of the rollover.

[pronguen]

At Grooming, we discussed 2 points:

1. do we need to store this data in RERO ILS or not?
   • yes, the data that usually doesn't change from one year to another should be stored in RERO ILS. This is not the case of the rollover name and period.
2. if yes, in which resource: library or organisation?
   • Rather in the library. If it is in the organisation, there are logic to implement in case of a creation/deletion of a library. Moreover, the organisation is currently not editable.
   • An argument for the organisation would be to restrict the edition of the rollover settings to a specific role.