Closed MattiasSealander closed 7 months ago
As previous pilot project dataset for dendro is ingested according to the old structure, it will be affected by this change. The smoothest way to manage this is to take this dataset out of the database completely and apply the changes. The dataset will need to be updated anyway due to new splint statistics from the dendro lab in Lund. This update can thus be performed on the data before reingestion according to new structure.
The previous pilot project test data will be completely removed from the SEAD database.
This change will be done retroactively i.e. affect all previously released database versions.
Any non-retroactive changes will be added to new CR 20231120_DML_DENDRO_MODEL_UPDATE. This CR might be removed if no (non-retroactively) changes are identified.
Original dendrochronology schema is defined in
Previously imported lookup lookup data will be kept as is in the database:
Previous submissions (pilot project). These CRs will be removed from the release chain:
The CRs needs to be revised or reworked:
The following CR has no effect and need to be investigated and possibly removed:
Tasks needed to handle this schema change:
Other tasks:
season_or_qualifier_id
, error_uncertainty_id
, error_plus
and error_minus
season_id
postgrest_api.qse_dendro_dating
20221121_DML_QSE_DENDRO_DATINGtbl_error_uncertainties
tbl_season_or_qualifier
Additional tasks:
postgrest_api.qse_dendro_dating
20221121_DML_QSE_DENDRO_DATING is used. (breaking change)Breaking changes: columns error_plus
, error_minus
, error_uncertainty_type
and season_or_qualifier_type
removed.
tbl_dendro_dates needs structural changes based around how seasons are indicated. This means that the table can be simplified and that seasons can be indicated via tbl_seasons instead of the current table (tbl_season_or_qualifier).
The changes that can be made to the table are:
The structure of the table should thus be: