Would it be possible to add a 12th module, that automatically creates relationship types with complex relationships? I want to create the relationships for a family trees.

For example:

  1. Parent --> Child automatically creates Child --> Parent in reverse direction
  2. Parent --> Child automatically creates Sibling --> Sibling among all the siblings in the family
  3. Grandchild --> Grandchild automatically creates Cousin --> Cousin among all the people with the same grandparent
  4. Sibling --> Parent --> Parent automatically creates Grandchild --> Grandparent
  5. and so on...

I know at least (1) and (2) can be done with "User Relationship Implications. However

  1. I'm over my head and can't figure out the logic, and
  2. Even if someone (I) could figure out how to get it to work, it would be nice to share it with the community, so others (like me) wouldn't have to "re-invent the wheel."

Thanks!

Comments

alex.k’s picture

alex.k commented
Component: User interface » Code

That's an interesting use case. It seems to me, though, at least from the software perspective, it's better to build the logic in the UI or API level, not necessarily in the data. That is, for example, not necessarily create a 'sibling' type of relationship and maintain all the links between all the children, but infer it from the fact that they all have the same parent. This can be just done on display, or perhaps as a function that underneath queries parent-child relationships.
Doing so will let you ask arbitrarily complex questions about the family tree without having to have first modeled them as distinct relationship types. Actual relationship data would only reflect minimal necessary 'direct' relationships, such as parent-child, married, divorced, adopted, and so on.

mogop’s picture

mogop commented

subscribe

ajayg’s picture

ajayg commented

Another option is integrate with Family tree module (http://drupal.org/project/family) instead of reinventing the wheel completely. I have no idea how difficult it is or make sense, just adding my first reaction. Such submodule or integration may remove the need for a standalone family tree module. If not possible some of the code in UI could be borrowed.

In any case doesn't hurt to atleast contact the developer of family tree module and see if there are possibilities of collaboration.

And here are more ideas for integration /borrow code

Darrin Lythgoe's The Next Generation (TNG) genealogy software
http://lythgoes.net/genealogy/software.php

Comparison of Drupal modules for Genealogy
http://groups.drupal.org/node/25135

mrf’s picture

mrf commented
Component: Code » Implications
Status: Active » Closed (won't fix)

Sounds like taking implications to the next level. This seems like something that would be better handled by the relation module due to the complexity of the intended relationships.