Active
Project:
Sunlight Congressional Districts (with optional CiviCRM integration)
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
10 Mar 2010 at 01:11 UTC
Updated:
20 May 2011 at 00:28 UTC
Jump to comment: Most recent
Comments
Comment #1
dalinComment #2
gregarios commentedI'm interested in using a state-level option if you come up with it... for sure. Subscribing.
Comment #3
Old Man commentedI too would be very interested in this module. State level integration gets my vote!
Comment #4
meecect commented+10000 subscribe.
If you sketch out some of the tasks involved, I'd be willing to chip in some coding help. This would be an extremely powerful addition.
Comment #5
dalin@meecect sorry for the slow reply, I've been extremely swamped this past month.
Basically what needs to happen is that we need to abstract out the concepts of districts, and look-up services so that the system can integrate with any level of government and with any look-up service. It should probably use the factory pattern.
What is your skill level? Are you familiar with design patterns?
Comment #6
tjhellmannThis would be a great feature for a number of organizations I work with – to have access to this data at a state level and CiviCRM integration. I don't think I have the skill set to contribute code, but I'd be willing to help recruit others and/or find funding. I know of several organizations here in the Boston area who may be willing to contribute funds towards this feature. It would be a great tool for local activism.
Comment #7
adharris commentedI'm looking for this feature as well...
@dalin: I can help out with the coding. I'm pretty new to drupal development, but my PHP is pretty solid.
If I understand you right, you are looking to abstract the lookup process into lookup object (which is then pointed at sunlight or elsewhere), and then use a factory to provide the appropriate lookup for a given case. Am I following you?
What is your vision for abstracting out the districts?
Comment #8
meecect commentedI have created a chipin page for this work. I'm happy to share the proceeds with whoever contributes to the final project. Here is the page:
http://cliffordmeece.chipin.com/enhancement-of-cdsunlight-drupal-module
@tjhellmann , it would be great if you could reach out to some organizations to help fund the effort.
Comment #9
dalinSort of. To maintain the ability to use the module without CiviCRM there needs to be a few parts to each lookup object lets call them lookup_service, lookup_views, and lookup_civicrm. lookup_service provides the ability to query the service (or it could be a local file or database even), and optionally store the data locally (like we currently do). lookup_views provides views integration. lookup_civicrm provides fields on the settings page for the admin to choose which CiviCRM custom fields are used for its domain (federal districts, prefects, or what have you). There would have to be something listening to CiviCRM watching for changes, lets call that the Listener. When a contact's address data changes the Listener either puts the contact_id in the lookup queue, or has all the look_civicrm objects do an immediate lookup (depending on the context, just like we do now).
That's my basic plan. It would probably need to be refined and mapped out a bit better.
Unfortunately I don't see myself having availability to code this for at least the next six months.
Comment #10
meecect commentedMy organization is willing to pay for the development of this feature, but we would like to extend it beyond state reps and down to city aldermanic districts as well.
Is anyone interested in doing this work for a fee? I can discuss the details more if there is interest.