ar-jan
commented
1 year ago Expected changes are fixing typos and incorrect values, no new entries or changes to how entries are related.
Storing the data as CSVs (and recreating the database via import upon release/deploy) is the most straightforward option, but does require carefully checking that the correct CSV records are updated. Since an edit UI is out of scope, this looks like the best option.
In principle the data set is complete and archived, but a few corrections are needed (and more might still pop up). Establish the best way to do this. The data size is small enough that we can include it in the repository. Allows keeping track of data changes and using tags/releases for the published version.