Difference between revisions of "General Data Protection Regulation (GDPR) (EU)"
From Diversity Workbench
(→Changes to be implemented in the databases) |
|||
| Line 8: | Line 8: | ||
*** PrivacyConsentDate: The time and date of the consent (set via trigger) | *** PrivacyConsentDate: The time and date of the consent (set via trigger) | ||
* Function UserID(): Providing the ID of the user in replacement of the SQL function User_Name() etc. | * Function UserID(): Providing the ID of the user in replacement of the SQL function User_Name() etc. | ||
| − | * Datatables | + | * All Datatables |
** Insert missing content from columns LogUpdatedBy into UserProxy | ** Insert missing content from columns LogUpdatedBy into UserProxy | ||
** Changing the contstraints for the logging columns from suser_sname() to UserID() | ** Changing the contstraints for the logging columns from suser_sname() to UserID() | ||
** Changing content of logging columns from name to ID | ** Changing content of logging columns from name to ID | ||
| + | * Special changes according to objects in the databases to remove reliance on fuctions like User_Name() | ||
| + | * Client software | ||
| + | ** Login: The user will be asked to consent to the storage and processing of his personal data. Otherwise the access will be denied | ||
| + | ** Tools: | ||
| + | *** The creation of standard objects and handling of datatables via skript | ||
| + | *** The insert of a link to the website with detailed information about the handling of the user related data | ||
| + | *** The possibility to remove the personal data of the user (removal of the entries in table UserProxy) | ||
---- | ---- | ||
Back to [[Software#Diversity_Workbench_software_implementations_in_compliance_with_regulations_and_directives]] | Back to [[Software#Diversity_Workbench_software_implementations_in_compliance_with_regulations_and_directives]] | ||
Revision as of 12:56, 9 April 2018
see https://en.wikipedia.org/wiki/General_Data_Protection_Regulation
Changes to be implemented in the databases
- Table UserProxy:
- New columns:
- ID: ID replacing the login name in datatables e.g. in columns LogUpdatedBy etc.
- PrivacyConsent: If the user constented to the storage and processing of his data in the database (set by user during login)
- PrivacyConsentDate: The time and date of the consent (set via trigger)
- New columns:
- Function UserID(): Providing the ID of the user in replacement of the SQL function User_Name() etc.
- All Datatables
- Insert missing content from columns LogUpdatedBy into UserProxy
- Changing the contstraints for the logging columns from suser_sname() to UserID()
- Changing content of logging columns from name to ID
- Special changes according to objects in the databases to remove reliance on fuctions like User_Name()
- Client software
- Login: The user will be asked to consent to the storage and processing of his personal data. Otherwise the access will be denied
- Tools:
- The creation of standard objects and handling of datatables via skript
- The insert of a link to the website with detailed information about the handling of the user related data
- The possibility to remove the personal data of the user (removal of the entries in table UserProxy)
Back to Software#Diversity_Workbench_software_implementations_in_compliance_with_regulations_and_directives
