Changes between Version 1 and Version 2 of DeveloperGuidelines/PersonEntityModel
- Timestamp:
- 03/07/12 20:34:06 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DeveloperGuidelines/PersonEntityModel
v1 v2 6 6 == Introduction == 7 7 8 [[Image()]] 8 We start with an obviously simple (read: small) set of person entities: 9 9 10 [[Image( )]]10 [[Image(pe_hierarchy1.png)]] 11 11 12 [[Image()]] 12 Each of these entities can define a number of roles which affiliated entities can have: 13 13 14 [[Image( )]]14 [[Image(pe_hierarchy2.png)]] 15 15 16 [[Image()]] 16 Now we link the respective entities to the roles, which defines an already pretty complex relationship network: 17 17 18 [[Image( )]]18 [[Image(pe_hierarchy3.png)]] 19 19 20 [[Image()]] 20 Some of these relationships define a hierarchy, while others don't: 21 21 22 [[Image()]] 22 [[Image(pe_hierarchy4.png)]] 23 24 This hierarchy defines ancestor paths among the person entities: 25 26 [[Image(pe_hierarchy5.png)]] 27 28 If we remove the roles, this becomes more obvious: 29 30 [[Image(pe_hierarchy6.png)]] 31 32 Now we can make the actual "hierarchy" visible by moving each entity to a certain "hierarchy level": 33 34 [[Image(pe_hierarchy7.png)]] 35 36 As you can see, "Person Y" belongs to two different organisations here - with two different ancestor paths. 23 37 24 38 ----