Author Topic: Data Structures in Related Communities  (Read 3607 times)

Offline FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Data Structures in Related Communities
« on: February 20, 2012, 08:52:34 am »
On my horizon is an implementation in which parishes have their own Drupal instance and there is at least some data sharing of basic contacts between parish and diocese for Civi.  A single ACL partition of Civi has it's own challenges since each parish needs it's own website.  A lot has been written and imagined on this topic:


If any interested parties would like to join in a conversation here to synthesize all this into a way forward I would really appreciate the collaboration!
Lead Developer, C3 Design.
Twitter: @FatherShawn

Offline SarahG (FountainTribe)

  • Ask me questions
  • ****
  • Posts: 782
  • Karma: 29
  • CiviCRM version: 4.4.7
  • CMS version: Drupal 6, Drupal 7
  • MySQL version: 5.5
  • PHP version: 5.3
Re: Data Structures in Related Communities
« Reply #1 on: February 20, 2012, 02:10:16 pm »
Have you considered the pros/cons of giving each parish its own install of CiviCRM + Drupal?   Then creating automation for updates/patches (such as using Drush/Aegir/etc) so they all stay at the same version?    Then you could use custom CRON jobs to share the data that needed to be shared.     

Wondering if enough data is different between each parish that sharing a single CiviCRM install would be a headache.  Also, in the case where all parishes share a single CiviCRM database, who would be the chief administer of the system for deciding global settings: such as custom fields, contribution types, event types, profiles, etc.




Did I help you? Please donate to the Civi-Make-It-Happen campaign  CiviCRM for mobile devices! 

Offline FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Re: Data Structures in Related Communities
« Reply #2 on: February 20, 2012, 02:53:33 pm »
That's my basic instinct, but I haven't yet had time to read/think through all that's in the wiki.  It's really the contact info that I would want to sync up to the diocesan level.  So that when an address or similar info was changed in a parish the change was also made at the diocese.  I just need to think through the best way to do that and to keep those records associated.
Lead Developer, C3 Design.
Twitter: @FatherShawn

Offline petednz

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4899
  • Karma: 193
    • Fuzion
  • CiviCRM version: 3.x - 4.x
  • CMS version: Drupal 6 and 7
Re: Data Structures in Related Communities
« Reply #3 on: February 20, 2012, 07:38:22 pm »
We would most likely be going down the multiorg approach since we have it running for several clients with various complex geographic and other layering.
You can then use a single Drupal site with lots of subdomains - eg Domain Access if sharing content/editing is useful.
Each domain then has civicrm forms - and if someone fills it in at x.yoursite.com then they get added to the container of contacts that the admins of x site should have access to - and ditto admins at site y get access to people who are added front or back end via the y site

hope that helps

if my brevity causes more head scratching than clarity - as it often does - happy to skype you through an example use case if that would help
Sign up to StackExchange and get free expert advice: https://civicrm.org/blogs/colemanw/get-exclusive-access-free-expert-help

pete davis : www.fuzion.co.nz : connect + campaign + communicate

Offline 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: Data Structures in Related Communities
« Reply #4 on: February 20, 2012, 08:30:56 pm »
Might want to check:

http://wiki.civicrm.org/confluence/display/CRM/CiviDataSync+Specification

basically aggregating n child sites into 1 master site for analytics. This is still a work in progress

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

Offline Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: Data Structures in Related Communities
« Reply #5 on: April 26, 2012, 05:21:57 pm »
Father Shawn - the concept of Chapter organisations came up @ the sprint & is slowly coalescing into a more public discussion. Both IMBA & Emphanos are in the stages of working through the documentation you have listed & improving it / coming up with their own.

Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

Offline FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Re: Data Structures in Related Communities
« Reply #6 on: May 15, 2012, 08:13:37 am »
Hey!  That's cool!   ;D

This is steadily floating up to the top of my pile!  My first task will be to build the diocesan property, which needs contacts shared between 4 or so entities. At the moment that looks like it can be one install.  Once that's operating well I'll bend my mind to an Aegir powered parish platform. 
Lead Developer, C3 Design.
Twitter: @FatherShawn