Issue #37: Data editing precedes sub-process 5.3 (review & validate)

Meeting 3 April: similar issue was discussed in Design and Collect phases and automatic correction was indeed mentioned as one of editing examples happening before Process phase. Nilgun proposed some changes in this regard.

Action: Nilgün Dorsan to check text in 5.3

After combining data at 5.1 (integrate data); classification of input data,  control of the codes and automatic coding, are done at 5.2 (classify and code). Unless doing this work, one cannot run the edit rules.  

At 5.3 (review and validate), errors, outliers, etc. are detected with the help of  edit rules. 

At 5.4 (edit and impute), after the errors are detected, correction/imputation procedure of the data has been started.

• OECD Glossary defines edit rule as: checking rule  "A checking rule is a logical condition or a restriction to the value of a data item or a data group which must be met if the data is to be considered correct. In various connections other terms are used, e.g. edit rule."
• OECD Glossary defines data editing as "Data editing is the activity aimed at detecting and correcting errors (logical inconsistencies) in data. Editing techniques refers to a range of procedures and processes used for detecting and handling errors in data"
• OECD Glossary defines imputation as "Imputation is a procedure for entering a value for a specific data item where the response is missing or unusable".

In line with those definitions, the issue raised at #37 about the "data editing" covers both 5.3 and 5.4.

In addition, 5.4 (edit and impute) especially defines the data correction activities. At this sub-process, "Edit" term is used as a correction which might be confused the users of GSBPM.

The title of this sub-process can be changed as "Correct/Impute".

Meeting 15/5: Agree with the point, but do not agree to change the name. Too many other things reference this sub process so the impact of the change is great.