This is still a work in progress but creating a fresh database totally from scratch using the 2i data should now work and be mostly doc'd in dataingest/README.md.
Doc dataingest/geo as actually used.
There are also changes in the python in "git@github.com:ONSdigital/nomis-bulk-to-postgres.git" repo which have been merged to support 2i. This has the side effect of breaking metadata_test.go (PR to fix to follow)
The database name is "census" but the data_ver table says Notes: "20220117 2i based on metadata/i2.txt (fewer QS + some KS rows)
"SetupDB" has been renamed to "SetupUpdateDB". It still reports some errors in the log in normal operation but fewer than before.
NomisDesc.ID is fixed. There are comments explaining some of the database constraints aren't in the gorm model (to allow the python to easily work)
This is still a work in progress but creating a fresh database totally from scratch using the 2i data should now work and be mostly doc'd in dataingest/README.md.
Doc dataingest/geo as actually used.
There are also changes in the python in "git@github.com:ONSdigital/nomis-bulk-to-postgres.git" repo which have been merged to support 2i. This has the side effect of breaking metadata_test.go (PR to fix to follow)
The database name is "census" but the data_ver table says Notes: "20220117 2i based on metadata/i2.txt (fewer QS + some KS rows)
"SetupDB" has been renamed to "SetupUpdateDB". It still reports some errors in the log in normal operation but fewer than before.
NomisDesc.ID is fixed. There are comments explaining some of the database constraints aren't in the gorm model (to allow the python to easily work)