Create a relationship between CRM entities, and in particular support and extend the D7 relationships:
Note that „is a member of“ is no longer separately necessary as households are subsumed under organizations. Also, a source can have several relations to a certain type of target (i.e. one organization has a parent, a subsidiary and 7 competitor organizations at the same time).
The implementation should be flexible enough to be extendable by others.
Some discussion about this already took place in 2016 in #2699811: [META] Data model discussions → .
Two general approaches are possible:
This is basically the same behavior as before, which the relation module provided. It has the benefit of making reverse-lookup queries easier to handle with.
However, it introduces significant overhead and cumbersome handling of revisions (i.e. a relationship is set to be no longer active and not tied to a specific revision of the relating entities). An activity could provide the relevant "log" per relationship here to track when a relationship was established and when it was broken.
From a UX perspective it could also be solved more elegantly than in 7 with functionality in the source/target entity context.
In this case the relationship entity would likely use bundles to differentiate types of relationships.
(Adding activities as pointed out above might still be worthwile for a better "log".)
Current state available in referenced branch
Active
3.0
Documentation
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.