Migration · 👣

Approach

The main data tables and some of the docs have been migrated from ParlGov legacy and are presented on ParlGov web (see migrate-db.sh). The SQLite database parlgov-experimental.db (see ParlGov Dataverse) is used for the migration. A mapping of the migrated tables and their new table names is provided in migration-check.csv.

The main information is summarized in the tablesview_party, view_election, and view_cabinet, which are included as database views.

Database tables now include a data_* or docs_* prefix to distinguish them from the database tables created by Django.

All tables include a created_at and an updated_at column. The values are set to the date of the migration import and do not record an entry's initial coding and last update.

Codes used in the variable type_id are documented in the table data_code.

Parties

Parties, party families, name changes, and party changes have been migrated from ParlGov legacy.

Party Facts provides a link file with ParlGov IDs, which should be used to link party IDs with other datasets. Party IDs from Party Facts, Manifesto, and CHESS are not included in ParlGov web.

Party positions and party IDs from other datasets were not updated for recent versions of ParlGov legacy.

Elections

Election results have been migrated from ParlGov legacy.

ParlGov legacy includes tables that record changes in the composition of parliaments (parliament_change) and parliament compositions (parliament_composition). This data is used to calculate the seat strength of cabinet parties based on viewcalc_parliament_composition. The data and the scripts for the calculation have not been migrated.

Cabinets

Cabinet parties have been migrated from ParlGov legacy.

Cabinet seats have not been included (see above).

ParlGov legacy includes an experimental and incomplete recording of confidence votes and cabinet support parties that have not been migrated to ParlGov web.

Docs

Codebook pages and news entries have been migrated from ParlGov legacy.

All database tables and variables are documented in ParlGov legacy, which includes checks to ensure the documentation covers all tables and variables. This documentation and the checks have not been migrated for the initial version of ParlGov web. ParlGov legacy also includes a table that documents JSON keys.

Data sources are documented with keys in the data tables and these keys are mostly documented and checked in ParlGov legacy. A migration of the keys needs a substantial revision and is not included in the initial version of ParlGov web.

External

ParlGov legacy includes additional information, such as party IDs and party names from other datasets, in database tables with the prefix external_*.

These tables were not updated for recent versions of ParlGov legacy and are not needed in a new version of ParlGov.

---