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 transitions to our domain models, 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.