As a [Donor or Project Owner], I want to see the historical performance of past rounds, so that I have an understanding of what round stats were in the past.
-
Goal
Enable the new v6 application to display historical QF rounds ("Archived Rounds") by importing legacy data into the new database structure, rather than querying or syncing with the old database.
-
Technical Requirements
One-Way Data Import: Import all legacy QF round data:
- Round IDs, Round Name, Round description, matching pool (allocated fund), matching pool token, is allocated fund USD preferred T/F, allocated fund USD, project list (project ids in the round), total raised, number of donors, QF round banners (mobile, desktop and hub image), slug, begin date, end date, priority, allocated token chain ID,
...into the new v6 database.
Database Principle: Ensure the architecture adheres to the rule: Do not push data to the old database.
Reasoning: Future rounds will generate data native to the new DB. Appending legacy data to the new DB allows the new system to become the single source of truth for "Archives" moving forward.
Validation: @RamRamez must validate this approach to ensure the new schema can gracefully accept the legacy data structure.
- Out of Scope (Post-MVP)
Full Stats Dashboard: A comprehensive dashboard visualizing deep historical data (V1, V2, etc.) is not included in this ticket.
Push Syncing: No mechanism should be built to send v6 round data back to the legacy database.
- Acceptance Criteria
[ ] Legacy QF round data is successfully migrated to the new database.
[ ] The "Archived Rounds" page on the v6 frontend successfully loads historical round lists from the new database.
[ ] No write connections are established from the v6 backend to the legacy database for round data.
As a [Donor or Project Owner], I want to see the historical performance of past rounds, so that I have an understanding of what round stats were in the past.
Goal
Enable the new v6 application to display historical QF rounds ("Archived Rounds") by importing legacy data into the new database structure, rather than querying or syncing with the old database.
Technical Requirements
One-Way Data Import: Import all legacy QF round data:
...into the new v6 database.
Database Principle: Ensure the architecture adheres to the rule: Do not push data to the old database.
Reasoning: Future rounds will generate data native to the new DB. Appending legacy data to the new DB allows the new system to become the single source of truth for "Archives" moving forward.
Validation: @RamRamez must validate this approach to ensure the new schema can gracefully accept the legacy data structure.
Full Stats Dashboard: A comprehensive dashboard visualizing deep historical data (V1, V2, etc.) is not included in this ticket.
Push Syncing: No mechanism should be built to send v6 round data back to the legacy database.
[ ] Legacy QF round data is successfully migrated to the new database.
[ ] The "Archived Rounds" page on the v6 frontend successfully loads historical round lists from the new database.
[ ] No write connections are established from the v6 backend to the legacy database for round data.