CiviCRM Community Forums (archive)

Hi - have been discussing this with Erik and thought I would broaden the audience.
A client undertakes retrofilling insulation to houses for the poor and sick based on referrals from Health and Social Service organisations.
The houses may be privately owned (owner occupier) or rented.
Characteristics of the house; age, number of bedrooms, state of insulation, type of heating etc, pertain to the 'property', and remain with the property even if the tenants or owners change.
And ex-tenants may move to houses that are not covered by the project, and hence aren't Properties in that sense.
So I am looking at doing these as a subtype of either Orgs or Households.
Orgs was my first thought as I expected H/H may trip me up more.
But I can see the logic of saying "a household is now a house, therefore people can use a 'house' address' - but that would presumably interfere if I also wanted to say "John, Mary and little Jimmy are part of the same household" - and hence if they move, they move as a group to a new .... exactly, Household or Property.
If I go with Household as Properties, then I can 'relate' the members of a family to each other via a new relationship.

Any thoughts?

Actually, writing this out is so helpful. Just occurred to me that sharing Org addresses was on the cards, and I see that is possible - so I think I go with Properties as Orgs, then I can set a Location to 'Property' and use that via the 'Share address with' option - and still use Households if required - hmm and even set the H/hold to 'share' the Property address. Nice

Though I guess that means I can also have a H/hold subtype as a Property and share address with another H/hold that is a H/hold - too many options ;-)

Any obvious advantage of going down the H/hold route versus the Org route.

Now back to the 'store a history of addresses'.

I'd go org subtype too. Add a hook/custom template with jquery so the "org name" is automatically generated from address + flat/floor.

oh - that was your zombie look