The current database schema has four problems:
* **German column names** - This leads to confusion for non-German speaking developers, diminishing developer experience, making onboarding more involved and leading to subtle errors: `adresstyp` vs `address_type`, note the different amount of "d"
* **Large Object (LOB) Columns** (`data` fields) - This makes it hard to export and query existing data.
* **Persistence layer breaks the boundaries of bounded contexts**. Example: Both Donations and Memberships have a relation to Address Changes, but Address Change is its own bounded context and the Donation and Membership Entities (Business Objects) don't have references to Address Change. The reference is only there as a convenience, to trigger the creation of an AddressChange record when we save Donations/Memberships. Here, the framework/storage layer bleeds into the BC.
* **Overloaded Status** - For donations, the payment status (waiting for payment, received payment notification from external provider), donation status (new, deleted in Fundraising Operation Center, Canceled on the Confirmation Page) and moderation status (Address contains suspicious words, donation comment contains suspicious words) and kept in one field, leading to data loss on status changes because the status has no "permutations" for the three different aspects. For memberships the situation is slightly better: Status is kept in bit field on the database level, but that makes it hard to comprehend.
During this refactoring, these problems should be rectified, with the following **constraints**:
* The FundraisingFrontend, Fundraising Operation Center and Export (SpendenDumper) must be operational at all times.
* To enforce the separation of the bounded contexts, we want to get rid of FundraisingStore "library" dependency in the fundraising-donation, fundraising-memberships and fundraising-subscriptions code repositories. Each bounded context should manage its own database schema.
* Entities in different bounded contexts are not allowed to reference each other (creating a dependency on entities outside the bounded context). If there is a reference on the storage level, for example to aggregate data for export, the reference should be inserted/changed at the storage level and should not show up in the entity definition.
* We want to keep the code of our domain objects unaffected by database technology - no ORM annotations on them. Use a separate XML file instead
**Acceptance Criteria**:
* All column names are in English
* If using ENUM columns (e.g. `address_type`), the values are in English.
* The data stored in the LOB is split out into tables
* The data stored in the "status" field is split among the entities, with a separate database field for each purpose.
* All database access is behind one or more interfaces, using the [[ https://martinfowler.com/eaaCatalog/repository.html | Repository Pattern ]]
* We're still able to do database migrations across all bounded contexts.
**Note**:
* To keep the Fundraising Operation Center and export working without huge refactorings, we could store the data redundantly, using the [[ https://www.martinfowler.com/bliki/StranglerApplication.html | StranglerApplication ]] pattern:
1) Copy the `DoctrineDonationRepository` and `DoctrineMembershipApplicationRepository` to the FundraisingFrontend, change the `Doctrine` prefix to `Legacy`
2) Change the `DoctrineDonationRepository` in `fundraising-donation` and `fundraising-membership` to map the Domain entities to database tables.
3) In FundraisingFrontend, create `DonationRepositoryWrapper` and `MembershipApplicationRepositoryWrapper` classes that implement the repository interfaces and have the Legacy and newly created repositories as dependencies. Whenever an interface method is called, both repositories must receive the method call. There must be a "mapping table" that maps between the automatically generated IDs for the legacy and "new" entities.
**Possible tables/entities (to be discussed)**
* donation
* With a better state, separating payment state, soft delete, export, etc. See for example {T137704}
* Maybe the concept of a "followup donation" (for recurring payments) that's linked to a previous donation and shares its entities. But maybe that's too much and should be implemented as a detail of the payment domain.
* donor (mostly differentiated by different address types, so far it's "private" and "company", but could become "email" in the future, see {T220367})
* donation events/change log: Commented, canceled, paid, moderated, exported. Those can be triggered from frontend and FOC
* payment (we'll have to see how we model the different payment types & their metadata)
* comment
* tracking (impcount, keyword and campaign from banner)
* buckets (bucket and name campaign from banner)
* membership_applications
* membership_applicants
* subscriptions (we can probably drop the address part because we use the subscription feature only for collecting emails for various purposes)
* address_change
* Change Log (Which user in the Fundraising Operations Center triggered which status changes, payment notifications, cancellations by user)
Impression counting should be its own domain/entities in the backend.
Maybe not every Domain object needs a table, minor objects (like `DonorName`) could be implemented as [[ https://www.doctrine-project.org/projects/doctrine-orm/en/2.6/cookbook/custom-mapping-types.html | Mapping Types ]].
Resources:
* https://www.martinfowler.com/articles/evodb.html
* https://martinfowler.com/eaaCatalog/repository.html