Old entries #132

New Issue

2022-03-01T13:09:45+01:00

mpeltriaux commented

2022-03-01 13:09:45 +01:00

Status quo

The so called 'Alteinträge' are a special type of Intervention, which have been around since at least 2010. They are mostly in very poor conditions regarding their data quality.

These old entries are those, which binding date have been before 18.06.2018, the date of the LKompVzVo publication.

Predecessor system

Formerly these old entries would have been entered by selecting Alteintrag from a drop down field on the first page of the form. If switched, the form would reload and certain fields would not be needed to enter data on. Since many people did not know what Alteintrag would mean, they simply ignored it therefore there could be old entries, which are not marked as old entries on the db.

Konova

Since konova does not provide due to simplifications any particular differences on entered data, we need to do the following:

As long as the binding date is not entered, we can not decide whether the entry is a regular one or an old entry
1. Therefore we run all regular logic on these ones
As soon as the binding date is entered, we can see whether this data has to be handled slightly different, which means:
1. Reduced check routine
  1. No process type needed
  2. No compensation/payment needed

Migration of old entries

A lot of old entries are in a miserable condition. We need to decide which one should be recorded directly and which one should not:

Old entries do not have any binding date on them by default. So we set them to be on 01-01-2018, marking them all equally as binding before the LKompVzVo, and add a hint to the comment field, being an old entry.
The following data need to exist on the old entry, so we can record it again. If this data does not exist, we migrate it but will not record it by default, due to low data quality:
1. Geometry
2. Identifier
3. Title
4. law
5. registration office
6. conservation office

# Status quo The so called 'Alteinträge' are a special type of `Intervention`, which have been around since at least 2010. They are mostly in very poor conditions regarding their data quality. These old entries are those, which binding date have been before 18.06.2018, the date of the LKompVzVo publication. ## Predecessor system Formerly these old entries would have been entered by selecting `Alteintrag` from a drop down field on the first page of the form. If switched, the form would reload and certain fields would not be needed to enter data on. Since many people did not know what `Alteintrag` would mean, they simply ignored it therefore there could be old entries, which are not marked as old entries on the db. ## Konova Since konova does not provide due to simplifications any particular differences on entered data, we need to do the following: 1. As long as the binding date is not entered, we can not decide whether the entry is a regular one or an old entry 1. Therefore we run all regular logic on these ones 1. As soon as the binding date is entered, we can see whether this data has to be handled slightly different, which means: 1. Reduced check routine 1. No process type needed 1. No compensation/payment needed ### Migration of old entries A lot of old entries are in a miserable condition. We need to decide which one should be `recorded` directly and which one should not: 1. Old entries do not have any binding date on them by default. So we set them to be on `01-01-2018`, marking them all equally as binding before the LKompVzVo, and add a hint to the comment field, being an old entry. 1. The following data need to exist on the old entry, so we can `record` it again. If this data does not exist, we migrate it but will not `record` it by default, due to low data quality: 1. Geometry 1. Identifier 1. Title 1. law 1. registration office 1. conservation office

mpeltriaux added the enhancement label 2022-03-01 13:09:45 +01:00

mpeltriaux self-assigned this 2022-03-01 13:09:45 +01:00

mpeltriaux referenced this issue from a commit

2022-03-11 14:38:44 +01:00

#132 WIP Old entries

mpeltriaux referenced this issue from a commit

2022-03-11 14:38:44 +01:00

#132 old entries

mpeltriaux referenced this issue from a commit

2022-03-14 16:00:36 +01:00

#132 Old entries migration

mpeltriaux referenced this issue from a commit