Closed XanderVertegaal closed 7 months ago
Related to this: the Role
model now accepts only one Person
. It makes sense to make it accept multiple instances of Person
and PersonGroup
(or whatever we decide to call the groups of people.
It makes sense that Role
only accepts one person - if multiple people are involved in an action, they each have their own Role
(though the nature of the role can be the same for multiple actors).
We have asked the researchers to reflect on this.
Question sent to the team on February 7th:
How to describe groups of people? Are groups unique to their role in an action, or does it make sense to have a list of groups? In case of the latter, we also have to deal with people leaving/entering groups over time. Another point of difficulty is that individuals may be implicitly part of a group.
We are going to keep the same Person model for this, but rename it to Agent. The model needs an additional field is_group
. We can then also add another value for Gender (mixed
), which should only be selected if is_group
is set to True
. Fields such as PersonDateOfBirth
and PersonDateOfDeath
are not relevant for groups.
We should have a model for
Groups of people
. I guess users should also be allowed to indicate that individualPerson
s are part of a group.