View Revisions: Issue #17123

Summary 17123: Store state of encrypted fields for archived tables
Revision 2021-04-12 16:31 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Data will be stored in a new table with the following structure:;

id - autoincrement integer
survey_id- the survey ID (original survey ID this table belonged to)
user_id - the user ID of user which created the archived table
tbl_name - varchar(255) name of the archived table without prefix
tbl_type - string (10) - token / survey / timing
created - datetime - datetime when table was archived
properties - text - JSON which contains a copy of fieldmap ?

Things to pay attention:
- When a table is archived an entry should be created
- When an archived table is deleted the entry should be removed from this table and not kept around - it is not a log
- The integrity check should check if there are entries with missing table and should remove them
- All existing archive tables should be added to the table on update - user ID should be set to 1. sid, date and Type needs to be extracted from name
- Restoration of/access to an archived table should only be allowed for superadmins, owner or admins with permission.
Revision 2021-02-24 16:35 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Data will be stored in a new table with the following structure:;

id - autoincrement integer
survey_id- the survey ID (original survey ID this table belonged to)
user_id - the user ID of user which created the archived table
tbl_name - varchar(255) name of the archived table without prefix
tbl_type - string (10) - token / survey / timing
created - datetime - datetime when table was archived
properties - text - JSON which contains a copy of fieldmap ?

Things to pay attention:
- When a table is archived an entry should be created
- When an archived table is deleted the entry should be removed from this table and not kept around - it is not a log
- The integrity check should check if there are entries with missing table and should remove them
- All existing archive tables should be added to the table on update - user ID should be set to 1. sid, date and Type needs to be extracted from name
- Restoration of/access to an archived table should only be allowed for superadmins and user_id
Revision 2021-02-24 16:34 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Data will be stored in a new table with the following structure:;

id - autoincrement integer
survey_id- the survey ID (original survey ID this table belonged to)
user_id - the user which created the archived table
tbl_name - varchar(255) name of the archived table without prefix
tbl_type - string (10) - token / survey / timing
created - datetime - datetime when table was archived
properties - text - JSON which contains a copy of fieldmap ?

Things to pay attention:
- When a table is archived an entry should be created
- When an archived table is deleted the entry should be removed from this table and not kept around - it is not a log
- The integrity check should check if there are entries with missing table and should remove them
- All existing archive tables should be added to the table on update - user ID should be set to 1. sid, date and Type needs to be extracted from name
- Restoration of/access to an archived table should only be allowed for superadmins and user_id
Revision 2021-02-24 16:34 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Data will be stored in a new table with the following structure:;

id - autoincrement integer
survey_id- the survey ID (original survey ID this table belonged to)
user_id - the user which created the archived table
tbl_name - varchar(255) name of the archived table without prefix
tbl_type - string (10) - token / survey / timing
created - datetime - datetime when table was archived
properties - text - JSON which contains a copy of fieldmap ?

Things to pay attention:
- When a table is archived an entry should be created
- When an archived table is deleted the entry should be removed from this table and not kept around - it is not a log
- The integrity check should check if there are entries with missing table and should remove them
- All existing archive tables should be added to the table on update - user ID should be set to 1. Type needs to be extracted from name
- Restoration of/access to an archived table should only be allowed for superadmins and user_id
Revision 2021-02-24 16:33 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Data will be stored in a new table with the following structure:;

id - autoincrement integer
survey_id- the survey ID (original survey ID this table belonged to)
user_id - the user which created the archived table
tbl_name - varchar(255) name of the archived table without prefix
tbl_type - string (10) - token / survey / timing
created - datetime - datetime when table was archived
properties - text - JSON which contains a copy of fieldmap ?

Things to pay attention:
- When a table is archived and entry should b created
- When an archived table is deleted the entry should be removed from this table and not kept around - it is not a log
- The integrity check should check if there are entries with missing table and should remove them
- All existing archive tables should be added to the table on update - user ID should be set to 1. Type needs to be extracted from name
- Restoration of/access to an archived table should only be allowed for superadmins and user_id
Revision 2021-02-24 16:31 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Data will be stored in a new table with the following structure:;

id - autoincrement integer
survey_id- the survey ID (original survey ID this table belonged to)
user_id - the user which created the archived table
tbl_name - varchar(255) name of the archived table without prefix
tbl_type - string (10) - token / survey / timing
created - datetime - datetime when table was archived
properties - text - JSON which contains a copy of fieldmap ?

Things to pay attention:
- When a table is archived and entry should b created
- When an archived table is deleted the entry should be removed from this table and not kept around - it is not a log
- The integrity check should check if there are entries with missing table and should remove them
- All existing archive tables should be added to the table on update - user ID should be set to 1. Type needs to be extracted from name
- Restoration of an/access to a archived table should only be allowed for superadmins and user_id
Revision 2021-02-24 16:28 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Data will be stored in a new table with the following structure:;

id - autoincrement integer
survey_id- the survey ID (original survey ID this table belonged to)
user_id - the user which created the archived table
tbl_name - varchar(255) name of the archived table without prefix
tbl_type - string (10) - token / survey / timing
created - datetime - datetime when table was archived
properties - text - JSON which contains a copy of fieldmap ?

Things to pay attention:
- When a table is archived and entry should b created
- When an archived table is deleted the entry should be removed from this table and not kept around - it is not a log
- The integrity check should check if there are entries with missing table and should remove them
- All existing archive tables should be added to the table on update - user ID should be set to 1. Type needs to be extracted from name
Revision 2021-02-23 16:39 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Data will be stored in a new table with the following structure:;

id - autoincrement integer
tblname - varchar(255) name of the archived table without prefix
tbltype - string (10) - token / survey / timing
created - datetime - datetime when table was archived
properties - text - JSON which contains a copy of fieldmap ?

Things to pay attention:
- When an archived table is deleted the entry should be removed from this table and not kept around - it is not a log
- The integrity check should check if there are entries with missing table and should remove them


Revision 2021-02-23 15:25 by c_schmitz
Description When archiving/restoring a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user enables/disabled encryption for some fields and restores the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new setting(s).

Columns:

* Timestamp
Revision 2021-02-23 15:24 by c_schmitz
Description When archive/restore a response/participant table using encryption, we need to know which fields were encrypted.
Because if a user switches off decryption for some fields and restore the data from an archived table, on restoration the data needs to encrypted/decrpyted according to the new settings.

Columns:

* Timestamp
Revision 2021-02-23 15:16 by ollehar
Description When import a response table, we need to know what was encrypted or not.

Same goes for participants.

Columns:

* Timestamp
Revision 2021-02-23 15:13 by ollehar
Description When import a response table, we need to know what was encrypted or not.

Same goes for participants.
Revision 2021-02-23 15:13 by ollehar
Description When import a response table, we need to know what was encrypted or not.