Changes between Version 17 and Version 18 of UserOptInConsent

Timestamp:

Jun 15, 2018, 10:06:56 AM (6 years ago)

Author:

skwang

Comment:

--

UserOptInConsent

@@ -38 +38 @@
  * `id` - primary key of table - a unique id for each row. Not used for the consent functionality.
  * `userid` - the user id
- * `consent_name` - consent name, corresponds to the 'shortname' in `consent_type` below.
+ * `consent_type_id` - consent type id, corresponds to the 'id' in the `consent_type` table.
  * `consent_time` - `datetime` type attribute : unixtime of when user `id` gave consent to `consent_id`.
  * `consent_flag` - the boolean which explicitly stats that this user id has given consent to this consent id. If this is 0 (FALSE), the following boolean should be 1 (TRUE).
@@ -45 +45 @@
 
 * `consent_type`
-  * `consent_id` - consent id, also the primary key.
+  * `id` - consent type id, also the primary key.
   * `shortname` - consent name, these should be short and in ALLCAPS, e.g., ENROLL, STATSEXPORTS, etc. There should be no spaces either.
   * `description` - text field describing the consent that user gives (or has given).
@@ -67 +67 @@
 Re: `consent_type` table
 
-At first there will be two records in `consent_type`: the main terms-of-use a user consents to when joining the project (ENROLL) and a stats-exports consent type (STATSEXPORT). In effect, these are distributed by BOINC upstream. This allows for flexibility - a project may decide to present a user with multiple items to consent to. Each can be recorded in the `consent` table with a different `consent_name`, whose description is stored in the `consent_type` table. The `protected` field indicated a consent type that is introduced by BOINC upstream for all projects.
+At first there will be two records in `consent_type`: the main terms-of-use a user consents to when joining the project (ENROLL) and a stats-exports consent type (STATSEXPORT). In effect, these are distributed by BOINC upstream. This allows for flexibility - a project may decide to present a user with multiple items to consent to. Each can be recorded in the `consent` table with a different `consent_type_id`, which corresponds to the row in the `consent_type` table, which contains the name and description. The `protected` field indicated a consent type that is introduced by BOINC upstream for all projects.
 
 The `enabled` flag is fairly important. By default no consent types are enabled. The project admins may toggle this in the Manage Consent Types OPS page. If the 'ENROLL' type is enabled, users will have to agree to a terms of use when creating an account. (The terms of use file must also exist). Independently, if 'ENROLL' is enabled, and parameter 'enable_login_mustagree_termsofuse' is equal to 1 (TRUE), existing users must agree to the site's terms of use.