Changes between Version 11 and Version 12 of LEGACY - CiviCRM LCBRU Use Case


Ignore:
Timestamp:
09/21/12 16:27:27 (12 years ago)
Author:
Nick Holden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LEGACY - CiviCRM LCBRU Use Case

    v11 v12  
    1111
    1212=== CiviCRM Object Model ===
     13
     14
     15=== Contact Types ===
     16
     17We can create sub-types which allow for specific custom fields and relationships to be built. This is most important to differentiate between LCBRU staff and those who might be study subjects, who we will call 'contacts'.
     18
     19* Individual - Contact
     20* Individual - LCBRU staff
     21* Individual - Health worker
     22
     23* Organisation - GP Surgery
    1324
    1425
    … …  
    2940
    3041=== Groups ===
    31 * LCBRU staff (ACL group, to allow for ACL role of 'LCBRU staff' to have edit permissions on contacts etc) - could this be a 'SMART GROUP' based on the drupal account being in the associated drupal role 'LCBRU staff'.
     42* LCBRU staff (ACL group, to allow for ACL role of 'LCBRU staff' to have edit permissions on contacts etc) - could this be a 'SMART GROUP' based on the drupal account being in the associated drupal role 'LCBRU staff'. Needs to interact with the designated contact type.
    3243
    3344=== Tags ===