Joint membership signup

[JulieR]

I'm setting up my first CiviCRM site. I'm still puzzling over what is the best practice for handling joint subscriptions. I've seen quite a few threads about this, suggesting that Households may not be the best way to go.  This suggestion seemed quite simple: http://forum.civicrm.org/index.php/topic,8052.0.html

But here's my puzzle. I am creating a contribution page to allow people to subscribe online.  Suppose someone wants to take out a joint subscription for himself and his wife.  I can offer him the more expensive 'joint' membership type easily enough, but how do I present him with a profile that captures both his and his wife's details, and creates separate records for them?  They only need to make one payment, so presumably everything should happen within a single profile, but I want them both to appear as members (ideally tagged to say they are joint) and both to be able to participate equally online.  And of course I have to capture their relationship.

I'm open to going with either the household or individuals method, but I'm not sure how to go about this in either case.  I'd really appreciate a steer, to tell me what strategy I could follow.

[dmd1062]

I have the same challenge, I’m setting up CiviCRM for a sports club with a membership of over 700 that comprises over 2000 individuals.

I therefore need to attribute several individuals to each membership on the signup page.

I look forward to seeing some helpful responses.

PS: What a fantastic product

[Donald Lobo]

This has come up a fair amount recently (was also discussed a bit on IRC last nite)

Unfortunately i cant think of a good solution

Sarah G think (and i agree) that a good solution is to potentially mimic the "On behalf of Organization" workflow and then use relationships to propagate this feature to all the household members. However this workflow will not collect data on each individual household member either

If this is important to you, consider sponsoring this feature for core and/or hiring a developer to work with us to get it into core for a 3.x release.

lobo

[petednz]

A hybrid of 'on behalf of organisation' and 'register additional participants'?

[JulieR]

Thanks for the answers - at least I know I'm not missing something.  For now I'll add some custom fields to capture the joint members' name and trigger a manual step to create that other individal user.  It's still a whole lot better than the MSAccess db we are using at the moment!

I often see the comment in the forums about sponsoring development, but it would be useful to have a sense of what sort of money is involved.   Wouldn't it be helpful to use civicrm to set up campaigns for desirable features where people could pledge contributions? That way various interested parties could share costs.  It would also provide a useful list of not-yet but potentially-available features.

[Donald Lobo]

I often see the comment in the forums about sponsoring development, but it would be useful to have a sense of what sort of money is involved.   Wouldn't it be helpful to use civicrm to set up campaigns for desirable features where people could pledge contributions? That way various interested parties could share costs.  It would also provide a useful list of not-yet but potentially-available features.

In general we do prefer that folks hire a developer from the community (http://civicrm.org/professional/) and work with them to build things for their needs. For significantly large features (like CiviCase etc), the core team would be interested in working and incorporating it.

In the recent past, a community member tried to organize this via the blog: http://civicrm.org/node/602 It was not successful, but was a good start, IMO

If you are interested in helping manage and coordinate this let us know. We already have a fair amount of stuff on our plate

lobo