Posted by Branjawn on January 16, 2010 at 10:30pm
So, I have a website for a church. Each person (adult and children) have their own account.
I need to build a directory, with photos. This would be easy for a company directory, but we need 'family' photos to be available here and persons grouped together.
My initial idea goes something like this: create "family" nodes using address as the unifying data. And, that's about as far as I've gotten. I really can't wrap my head around how to do this. Please help me brainstorm!
Recap: I want a node, a box (will prob use panels) that has a family photo, then the names and address of that family. They need to maintain, which only pertains to the photo. I already gather address and all other kinds of personal info in the account creation process.
Comments
Flickr?
B.
Flickr does a really good job of making galleries of images and tagging faces in photographs. As of this writing they have free services that are fantastic. I think the recommendation I'd make would be to utilize the awesome power of Flickr (which specializes in managing photos) by embedded widgets on your site.
If you haven't seen Yahoo! Pipes yet, I definitely suggest checking that out and building your widget through that service. You can build it with custom arguments, etc. to make really dynamic content without knowing how to program at all.
Attempting to replicate ubiquitous functionality on-site is almost always a recipe for frustration as the services that offer such specialized care have spent millions of dollars in engineering time to make things awesome.
-t
Could you have a node with
Could you have a node with the picture, and then use a CCK field to grant certain users permission to edit?
http://drupal.org/project/nodeaccess_userreference
or
http://drupal.org/project/nodeaccess_autoreference
Perhaps I'm not understanding what you want to build.
Node Reference?
Putting my mind around the same issue. Thinking of using Node Reference to associate the different family member nodes to the family node. Would allow for unlimited family member node types (familyMemberSon, familyMemberDaughter, etc). Each type could have its own picture, address, phone #s, email, required and/or optional other references, etc. Check out Mustardseed Media for a primer on Node References. Coupled with gallamine's idea for access, could be functional and user maintained.
My other (hair-brained?) idea was to use Organic Groups with family nodes as a group type. Haven't thought too much about what roads that may lead me down, but you asked for brainstorming. :)
Be sure to report back what you find, the right recipe would definitely be useful to others.