CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • Modeling membership structure
Pages: [1]

Author Topic: Modeling membership structure  (Read 815 times)

jcaston

  • I’m new here
  • *
  • Posts: 4
  • Karma: 0
  • CiviCRM version: 4.2.6
  • CMS version: Drupal 7.17
  • MySQL version: 5.1
  • PHP version: 5.3
Modeling membership structure
December 01, 2012, 03:26:32 pm
Looking for some feedback about how to structure my users... I've been playing with this for over a week, reading forums and guides, trying different configurations but can't seem to get Civi to do what I want.  I'm probably missing a something pretty fundamental and just not seeing it.

Here's what I think I have so far...

Diocese (org)
- Parish or Organization (household)
-- Priest
-- Deacon
-- Seminarian

The organization that I'm working with wants individuals of three types (priests, deacons, and seminarians) to self-register for access to membership resources (in Drupal, with ACLs).  During registration individuals would be required to fill out a profile listing the households (parishes or schools, etc) they belong to as well as their organization (diocese).

The first group of issues I had was how to define priests, deacons and seminarians.  I assumed I would use 3 sub-types, then use 3 separate forms for sign up.  The goal is to have different fields available to the different sub-types, for instance priests and deacons would require a date of ordination field while seminarians would not.  Since it's possible for each to be attached to more than one Parish or Diocese, I was under the impression I could enable them to add their own relationships from a Webform or profile.

The second chunk of issues I had was when I tried to use CiviMember to intake those users.  CiviMember seems to require that each organization already exists as a contact. 

Ultimately, a user should be able to sign up for Drupal, enter some basic contact information, and attach themselves to new or existing households and orgs and have their role, group or membership pushed to Drupal for ACL.

I think my biggest issues stem not understanding how *all* of the components connect.  Does anyone else have a similar structure that could throw me a bone?

-jc

 

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Modeling membership structure
December 01, 2012, 04:20:37 pm

Any idea why you want to use CiviMember?

Seems like this is more contact structuring and does not really involve membership

i suspect folks with more experience will respond to the other parts of your post

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

jcaston

  • I’m new here
  • *
  • Posts: 4
  • Karma: 0
  • CiviCRM version: 4.2.6
  • CMS version: Drupal 7.17
  • MySQL version: 5.1
  • PHP version: 5.3
Re: Modeling membership structure
December 01, 2012, 04:33:20 pm
Not married to the idea.  I've tried it in normal profile forms, Webforms, and CiviContrib/CiviMember forms to try to accomplish my goal...  I posted in the CiviMember category because it was the last feature I had tried and I felt like I was getting closer to my goal.  I could be on totally the wrong track.

If I scrap the membership idea, then my goal will be enrolling users using profile forms, then some how allowing them to attach relationships to to existing households or orgs and have the option to create a new one.

One thing I haven't tried yet, but just thought, was making the registration multi-step.  I suppose if they register with Drupal first, it will be easier to expose other contacts to them to select from or allow them to create new ones.

Thanks lobo

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • Modeling membership structure

This forum was archived on 2017-11-26.