Acquisition : rollover process

[PascalRepond]

User story

As a system librarian, I want to do a rollover in the acquisition module each year, in order to recreate my account structure and move open orders to a new fiscal year.

Global concept

• Each library has a set of configurations editable for the next rollover (how to duplicate accounts, etc.)
• The rollover is done in one step for a whole organisation, because currently the active fiscal year (budget) is defined on the organisation level (for now).
• The rollover is launched and monitored manually (for now).

Acceptance criteria

Detailed spec: https://ncloud.rero.ch/index.php/s/BgqpRYiZNgJA4ar

1. You give the organisation pid
   1. If it doesn’t exist: interruption with a message
2. It verifies if the next fiscal year exist
   1. If yes: it verifies if it is active
      1. If no: it activates it
   2. If no:
      1. it automatically creates it with status active OR interruption with a message “Please create the next fiscal year and make it active”
3. It verifies if there are accounts in the active fiscal (org.current_budget) of the organisation
   1. If no: interruption with a message
4. It duplicates the accounts (see transfer spec in section 5.1)
5. It duplicates the orders (see transfer spec in section 5.2)
6. It duplicates the order lines (see transfer spec in section 5.2)
7. It changes the current budget on the organisation

Tasks

• implement global CLI
• implement and test order & order line transfer
• implement and test account transfer
• implement linked issues:
  • Changing the fiscal year in the organisation should be directly effective for all users #2929
  • Block modification of resources linked to a non current fiscal year #2930
  • Add rollover settings in the library / fiscal year / organisation #2931

[github-actions]

This issue is stale because it has been open 6 months with no activity.