Change Details

The Fundraising Operation Center makes use of the `spenden` and `request` tables for backoffice functions (looking at new donation/memberships and moderating them), Analysis and Reporting. Since the backoffice functionality changes the data, the backoffice code (`application/controller/Backend/DonationController`, `application/controller/Backend/Ajax/ListController`, `application/controller/Backend/Ajax/MemberController`, `application/model/Donation`, `application/model/Member` `DonationStatusUpdateService`) need to be changed first. We need to keep the legacy `state` field in sync in the legacy `spenden` and `request` tables so analysis, reports and export don't show donations/memberships that were soft-deleted/moderated. Analysis and reporting should query the new database tables. This mostly affects the classes `application/model/Donation`, `application/model/Member`, `application/model/Analysis`, `application/model/Report`. `

The Fundraising Operation Center makes use of the `spenden` and `request` tables for backoffice functions (moderating and deleting new donations and memberships), using a custom database abstraction layer. While we have two different database tables for the same information during the database refactoring, this would create inconsistent data. That means we need to add new state transiations to our domain models and new use cases for the state transiations and replace the existing code in the Fundraising Operation Center. **Acceptance Criteria** * All code *writing* to the database uses the repository classes from the bounded contexts. **Implementation notes** * Start with the following classes: - `application/controller/Backend/DonationController` - `application/controller/Backend/Ajax/ListController` - `application/controller/Backend/Ajax/MemberController` - `application/model/Donation` - `application/model/Member` - `DonationStatusUpdateService` * Add new use cases and methods to the domain classes as necessary.

The Fundraising Operation Center makes use of the `spenden` and `request` tables for backoffice functions (lookmoderating at new donation/membershipnd deleting new donations and moderating thememberships), Analysis and Reportingusing a custom database abstraction layer. Since the backoffice functionality changesWhile we have two different database tables for the same information during the dataabase refactoring, the backoffice code (`application/controller/Backend/DonationController`,this would create inconsistent data. `application/controller/Backend/Ajax/ListController`, `application/controller/Backend/Ajax/MemberController`, `application/model/Donation`,That means we need to add new state transiations to our domain models and new use cases for the state transiations and replace the existing code in the Fundraising Operation Center. **Acceptance Criteria** * All code *writing* to the database uses the repository classes from the bounded contexts. **Implementation notes** * Start with the following classes: `application/model/Member` `DonationStatusUpdateService`) need to be changed first. We need to keep the legacy `state` field in sync in the legacy `spenden` and `request` tables so analysis, reports and export don't show donations/memberships that were soft-deleted/moderated. Analysis and reporting should query the new database tables. This mostly affects the classes `application/model/Donation`, `application/model/Member`, `application/model/Analysis`, `application/model/Report`.- `application/controller/Backend/DonationController` - `application/controller/Backend/Ajax/ListController` - `application/controller/Backend/Ajax/MemberController` - `application/model/Donation` - `application/model/Member` - `DonationStatusUpdateService` `* Add new use cases and methods to the domain classes as necessary.