when to use OG, taxonomy, cck, views... how to display clubs, been done before? potential tutorial/cook book

Hi, I'm trying to decide what modules I need, and how to organize and implement something I'm sure has been done before, but I could not find it listed in the cookbook, and I'm not sure what keywords to search for...

The idea is I want a site that displays a directory of different instances of clubs. but each club is made up of the same parts....

What parts should I use taxonomy for? cck for? OG? My guess is that I will use multiple views, some calling other views, then finally a club view.

I guess my question is: do you know of any tutorials, case studies, cook books, modules to point me to?

If you know of how to do one little part of this, please post, you dont have to have a comprehensive solution for be to be very grateful.

Thanks a ton, volunteermama (who will be more than happy to write up a cook book [or what not] when I get this set)

what follows is background information:

simple example (believe it or not, there is actually a lot more info for each club, but the properties of the info repeat... so if I can get this to work, I can replicate it for the rest of the club info):

----------------------

club name: Whisper Pines Club
club description generic: anyone can come to meetings or call a member for support
club news: -

meeting information (each meeting name, description, time, location = mtgn + mtgd, + mtgt + mtgl):
meeting name: sports
meeting description: -
meeting time: tuesdays at 7pm
meeting location: cafe late, 100 main st, citytown

member information (club member qualification: cmq which is gcmq, ccmq, or gcmq + ccmq; followed by a list of members):
custome club member qualification: club members are required to have 2 years training
members:
john 333 555 1111 j@b.c
sally s@f.b
fred 111 222 3333

list of x nearest meetings (based on club zip code):
forest view sports mondays at 9
rock hills cafe tuesdays at 3
rock hills sports saturdays at 2
club page maintainer: global default (frances)

----------------------

club name: Rock Hills Club
club description generic: anyone can come to meetings or call a member for support
club news: -

meeting information (each meeting name, description, time, location = mtgn + mtgd, + mtgt + mtgl):
meeting name: cafe
meeting description: drop in meeting
meeting time: tuesdays at 3
meeting location: cafe uno, 2222 east st, bigcity

meeting name: sports
meeting description: -
meeting time: saturdays at 2
meeting location: field duo, 321 west ave, bigcity

member information (club member qualification: cmq which is gcmq, ccmq, or gcmq + ccmq; followed by a list of members):
custome club member qualification: club members are required to have 2 years training
members:
sally s@f.b
chris 333 555 1111

list of x nearest meetings (based on club zip code):
forest view sports mondays at 9
whisper pines sports tuesdays at 7
club page maintainer: chris

------------

if sally decides to display her phone number, than any clubs she is a member of, should change to display that also.
if sally leaves the whole organization, then she is removed from each club she was a member of ... (and if she was a maintainer, that defaults to the system default, if she was the ruling member, another sally must specify which other member is to take over the ruling member status.... and on and on....

--

Complex description...
Each club has a club name.
Each club has a number of club members (0-cm club members).
Each club that has more than 0 members has one and only one ruling member (rm) which has to be a member of the club.
Each club can specify a member to be the club page maintainer, if no one specified, use the "global" maintainer default. The maintainer is the contact for changes to the club page, but also can pick the settings of the club page and update the info there (like adding or removing a member or meeting, changing a description).
Each club has a description (cd). Each club can pick to use a generic club description (gcd), or a custom club description (ccd), or both.
Each club can have news items with optional start expiration dates (0-n news items).
Each club has a main zip code.
Each club has a member qualifications (cmq) describing what criteria members have to meet to be members of that club. Each club can pick to use a generic club member qualification (gcmq), or a custom club member qualification (ccmq), or both.
Each member can be associated with different clubs (0-c clubs).
The member might be associated with a user login, or the member information might be updated by a club admin, or the site admin.
Members are made up of: first name, last name, phone number, email address, street address.
Members can choose to hide: phone number or email address, but not both (just doesnt make sense to list them if no way to contact them in my situation) in the club listing (same for any club they are a member of). Last name and address are hidden manditorily in a club page.
Members can update their own info.
Clubs can have meetings (0-mtg meetings).
Each meeting can have a different name (mtgn), description (mtgd), time (mtgt), location (mtgl)

Then each club page would display:

club name
club description (cd) which is gcd, ccd, or gcd + ccd
club news
meeting information (each meeting name, description, time, location = mtgn + mtgd, + mtgt + mtgl)
member information (club member qualification: cmq which is gcmq, ccmq, or gcmq + ccmq; followed by a list of members)
list of x nearest clubs (based on zip code)
club page maintainer