ChurchCRM / CRM

ChurchCRM is an OpenSource Church CRM & Management Software.
https://ChurchCRM.io
MIT License
607 stars 428 forks source link

Question on Multi-Generational #2147

Open litocabz opened 7 years ago

litocabz commented 7 years ago

Hi, I'm new in using ChurchCRM and I'm not a developer but understands a little bit of programming. I'm currently building our member database system for our community (this is how we refer to our group which is a Catholic Charismatic group).

Our community consists of several families and have multiple generations already. How do we address this in ChurchCRM? To ilustrate, we have one family with head of family, spouse and 2 children. Eventually, one of the children got married and now has his own family and he is the head of the family. Then, he also had children that got married and still in the community and is also head of the family. How can we do it that when we view the first family, it will still display their children and same with the second.

I'm not sure if this has been asked here but I tried to look but didn't get any thing about it.

Appreciate your assistance.

DawoudIO commented 7 years ago

This is a new feature as we don't have family trees... but i do like the idea...

litocabz commented 6 years ago

Hi, just would like to check this new feature... Thanks.

michaeleino commented 5 years ago

+1 for this feature ! any expected milestone for this ?

michaeleino commented 4 years ago

Hey! it is very important to track the people tree... for each person, after marriage, we can't determine what was his/her family?... and in the case of a family separation "divorce" should we leave the family empty and each person go to his parent's family again ?

moreover after a second re-marriage! what should be the case is!

I suggest just to enable to assign a multiple roles @ "Family Info" section:

As one person will be a child of his parent's family, and a household on another family after marriage, and so on....

or to add a custom field like "Person from Group" type, but instead the holder should be a family name, where we can name the field "parent family" and/or "first marriage" [in case second marriage happend] -- those are just suggestions.

the above case is a real case in my deployment. and I can't handle.

any suggestion! Thanks

github-actions[bot] commented 3 weeks ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.