CiviCRM Integration (for Content Types)

Hi Joe
Can you provide some scenario/use cases as the purpose of this isn't leaping out to me - and maybe i am missing something really obvious

Hi Joe, I'd strongly encourage you to get involved in this discussion: http://forum.civicrm.org/index.php/topic,24292.msg102922.html#msg102922
I admit that, like Pete, I am a little at a loss for comprehending how this will work and what it will do for us, but perhaps you and Matt will understand each other :)

The way we have done the above - with an example - is to use a civicrm reference field on the Content Type and then use a Contextual Filter based View block to pull in the other data.
Eg
Political Party as a Node
reference it so civicrm contact via civicrm reference field
build view such that the block that shows on the Party page includes 'party leader' 'office phone and fax' etc

You could use civicrm reference field also for Job Listing if you are providing a Content Type that a user fills in, and they need to reference an Org that is in civicrm.

If you need them to create the Org, then I would suggest a 2 step process - first via webform to push data in to civi - then as per the Party example.

I think asking for generic Content Types to be able to pull/push data to civi is reaching for the stars (but happy for coleman to say 'ah yes, i see how to do it"

A combo of views and webforms is a great start for making your directory. They both have advanced features and both accept contact_id as args, so you may well be able to put something together that does exactly what you want using those two tools. Something like:

1. Use a view to list/search for contacts in the directory (call this view 1). For each listing, provide a link to view 2:
2. Use a second view (call it view 2) that accepts cid in the url and displays a single member of the directory. Using some sort of embedding/blocks you could probably get your drupal taxonomy stuff in there as well (although CiviCRM does have tags, don't forget)
3. View 2 can provide a link to your webform, which could contain the exact same fields as view 2 (but of course will be editable)
4. Submitting the webform redirects you back to view 2, and viola, the data has been updated!

I think asking for generic Content Types to be able to pull/push data to civi is reaching for the stars

ah, yes, i see how to do it.

;-)

But it will take some time or volunteers or sponsorship. But my proof-of-concept, linked above, shows that it can be done.

ah, yes, i see how to do it.

nice one Matt
Pete must write out x 50 "I will read and digest all forum posts and always read links coleman supplies before mouthing off" ;-)

Matt I think I can see how your approach would make the Views/Context Filters/Blocks kind of redundant which would be great if it were able to have us pulling in data from related contacts etc which i daresay is all 'possible' given what you describe on the forum

Not really within the scope of this project.