Changes between Version 1 and Version 2 of DeveloperGuidelines/PersonEntityModel


Ignore:
Timestamp:
03/07/12 20:34:06 (10 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/PersonEntityModel

    v1 v2  
    66== Introduction ==
    77
    8 [[Image()]]
     8We start with an obviously simple (read: small) set of person entities:
    99
    10 [[Image()]]
     10[[Image(pe_hierarchy1.png)]]
    1111
    12 [[Image()]]
     12Each of these entities can define a number of roles which affiliated entities can have:
    1313
    14 [[Image()]]
     14[[Image(pe_hierarchy2.png)]]
    1515
    16 [[Image()]]
     16Now we link the respective entities to the roles, which defines an already pretty complex relationship network:
    1717
    18 [[Image()]]
     18[[Image(pe_hierarchy3.png)]]
    1919
    20 [[Image()]]
     20Some of these relationships define a hierarchy, while others don't:
    2121
    22 [[Image()]]
     22[[Image(pe_hierarchy4.png)]]
     23
     24This hierarchy defines ancestor paths among the person entities:
     25
     26[[Image(pe_hierarchy5.png)]]
     27
     28If we remove the roles, this becomes more obvious:
     29
     30[[Image(pe_hierarchy6.png)]]
     31
     32Now we can make the actual "hierarchy" visible by moving each entity to a certain "hierarchy level":
     33
     34[[Image(pe_hierarchy7.png)]]
     35
     36As you can see, "Person Y" belongs to two different organisations here - with two different ancestor paths.
    2337
    2438----