Changes between Version 4 and Version 5 of UserOptInConsent


Ignore:
Timestamp:
Apr 26, 2018, 12:11:44 PM (6 years ago)
Author:
skwang
Comment:

add additional table fields

Legend:

Unmodified
Added
Removed
Modified
  • UserOptInConsent

    v4 v5  
    3131 * `consent_id` - consent id
    3232 * `consent_time` - `datetime` type attribute : unixtime of when user `id` gave consent to `consent_id`. If zero, user has not consented (yet).
     33 * `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).
     34 * `consent_not_required` - a special boolean that indicates whether or not consent is not required. This feature may be used by certain special ...
     35 * `source` - text field containing the technology actor which the user gave consent. Example: if a user gives consent by registering for an account using the BOINC GUI client (BOINC manager), this would be set to 'client'. If the account is created on a Web site registration page, this would be set to 'web'. Other sources may be 'AM' (account manager), 'boinccmd' (command-line client), and 'RPC' (the Web RPC).
    3336
    3437* `consent_type`
     
    4043=== RPC ===
    4144
     45Two RPCs will need to change
     46 * create_account.php
     47 * am_set_info.php
     48
    4249The main RPC that needs to be changed is `create_account.php`, which needs to insert a record into the `consent` table when the user creates his/her account- assuming s/he consents to a site's terms of use.
     50
     51Additional parameters for RPC are
     52 * optin=0 | 1 -
     53 * source='string' -
     54
     55`am_set_info.php` needs to be modified in order to contain a consent parameter, which also modifies the `consent` table in the database.
     56
    4357
    4458=== Web site ===