CiviCRM Community Forums (archive)

Hi,

I've seen or developed various solutions to synchronise (as in when you create it in one side, it creates it on the other) "things" between drupal and civicrm, eg. when you create a case, it automatically creates a node of type project, when you create a node "document" it creates an activity "doc"...

Part of it is likely to be custom (eg my node document has not the same contact cck than yours, the activity type is likely to be different..), but some might/should be shared ?

eg creating a civicrm_external_ref table:
- cms_id
- cms_type
- crm_id
- crm_type
- creation_date
- author
- is_active

functions createCRM (to be called from a hook on drupal), createDrupal (to be called from a hook on civi), same for deleteCRM deleteDrupal

And an example or two of hooks using that.

Something like that exists already ? Should be part of the drupal modules in the standard distrib?

X+

P.S. Better names more than welcome, not inspired.

I only use og_mailinglist in one case so far, as a discussion on new features and developments.

Each project is an OG, each issue is a node, and each subsequent discussion on the issue a comment.

So you can send an email to newissue@kabissa.org that would send  that to the other in the group, that can reply...

How does it relate in civi ? Each project is a case, each issue an activity, it would make sense to sync the two.

What was your need for kabissa ?

Why would you want to have issues in both places - as nodes/comments in OG and cases/activities in CiviCRM? One or the other would seem more than adequate.

Because all the details and discussions and files are "content" (ie comment/node/OG), and using OG_mailinglist works great for that IMO.

On the other hand, an overview of activities (eg. how often they are activities in the group, are they all closed, should some be part of case needing follows up) is about contacts, hence in civicrm.

X+

Right, probably not all of them indeed, but would be useful to be able to "flag" one to be synced with civi because you want to follow up, or in general want to keep it in the activity.

Another usage of sync is that we are using the forum usage as a way of gauging the topics of interest, eg if you post in the forum "transparency & democracy" we tag your contact "transparency".

X+

Not sure I'm following your suggestion, an incoming email creates an activity, but doesn't tag the contact.

This being said, my initial point was that there is a need that have been expressed several time to sync between drupal and civi, and seems to me that everyone is re-inventing the same underlying table and structure to handle the same basic need (1<->1 between two ids, checking if the records exists already...). But it might be that's a common need of us only.

X+

Hi,

I have been looking at doing something like this in the context of using 'Rules' module.

The request was to have an organic group created whenever an event was created and to add participants to it as group members when they registered. When the registration role is 'tutor' they are made the groups owner.

We wanted to get a feeling for the potential of rules module so explored it that way. Effectively it moves the ability to configure these interactions from code into the UI.

One issue I hit was the one you described here - how do I link the event & then group. I decided to add a cck field type called 'cck_civicrm_event' (although it's being renamed to 'civicrm_entity' I think).

So, the cck field is attached to the node & holds a reference to an entity & that makes it possible to link them via rules. One issue is that more than one event could be linked to a node but I'm just using 'limit = 1' ATM

The point of the UI is to make it so other people can do it & I don't have to!