Announcing CiviVoter And Canvasser

View: New views
7 Messages — Rating Filter:   Alert me  

Announcing CiviVoter And Canvasser

by Rob Thorne :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello CivCRM users and developers!

I'd like to announce a developer's release of CiviVoter and Canvassers,
two tools for managing voter files and contacts with voters during
political (and similar) campaigns.   The work  was sponsored by the
Green Party Of Canada, which has generously agreed to release it to the
general CiviCRM community.

I've just posted a demo site at http://cvdemo.torenware.com,  and will
post source files (a custom version of CiviCRM 1.6, and a Drupal module)
on that site shortly.  Here's a bit more info:

    *  CiviVoter is a new sub-system for CiviCRM. Its purpose is to
      manage a voter file for you (the kind you get from the your county
      registrar of voters, or your national elections authority). Since
      CiviCRM is a rich and rapidly improving system for managing
      contacts, a lot of what you'd want to do with a voter file is
      already a part of CiviCRM. CiviVoter adds tools for running phone
      banks (for calling voters) or foot canvasses (going door to door
      and meeting voters face to face).
    * Canvasser is a Drupal module for running phone banks and foot
      canvasses. It uses CiviVoter to manage the voter file, but uses
      Drupal modules like Events, CCK or Location to help manage
      volunteers, and to add additional UI.
    * We'd like to get some feedback on our "first generation" interface
      and work flow, and we've created some test accounts to help you do
      that. We've set up an imaginary political campaign for the
      Canadian House Of Commons (the Green Party of Canada sponsored
      this work, so why not?), and we've imported 100 "voter records".

I've set up two demo accounts,  Organizer (pw: demo)  and Volunteer (pw:
demo) so you can see what the site looks like from different points of
view.  I'll also be happy to give out accounts with admin access, so you
can see the admin interface as well.

Have at it!

Thanks,
Rob Thorne
Torenware Networks


____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

Re: Announcing CiviVoter And Canvasser

by Donald Lobo :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

great job and congratulations Rob :)

hats off and a BIG THANK YOU to the the Green Party of Canada for
releasing the code under very generous terms (that allows us to
include / modify / integrate the code into our svn)

We hope that quite a few other folks will test and use this component.
We plan on integrating a future version of this component into the
main CiviCRM code base. Please direct any/all feedback and reviews to
Rob and the dev list

lobo

On 3/23/07, Rob Thorne <rob@...> wrote:

> Hello CivCRM users and developers!
>
> I'd like to announce a developer's release of CiviVoter and Canvassers,
> two tools for managing voter files and contacts with voters during
> political (and similar) campaigns.   The work  was sponsored by the
> Green Party Of Canada, which has generously agreed to release it to the
> general CiviCRM community.
>
> I've just posted a demo site at http://cvdemo.torenware.com,  and will
> post source files (a custom version of CiviCRM 1.6, and a Drupal module)
> on that site shortly.  Here's a bit more info:
>
>     *  CiviVoter is a new sub-system for CiviCRM. Its purpose is to
>       manage a voter file for you (the kind you get from the your county
>       registrar of voters, or your national elections authority). Since
>       CiviCRM is a rich and rapidly improving system for managing
>       contacts, a lot of what you'd want to do with a voter file is
>       already a part of CiviCRM. CiviVoter adds tools for running phone
>       banks (for calling voters) or foot canvasses (going door to door
>       and meeting voters face to face).
>     * Canvasser is a Drupal module for running phone banks and foot
>       canvasses. It uses CiviVoter to manage the voter file, but uses
>       Drupal modules like Events, CCK or Location to help manage
>       volunteers, and to add additional UI.
>     * We'd like to get some feedback on our "first generation" interface
>       and work flow, and we've created some test accounts to help you do
>       that. We've set up an imaginary political campaign for the
>       Canadian House Of Commons (the Green Party of Canada sponsored
>       this work, so why not?), and we've imported 100 "voter records".
>
> I've set up two demo accounts,  Organizer (pw: demo)  and Volunteer (pw:
> demo) so you can see what the site looks like from different points of
> view.  I'll also be happy to give out accounts with admin access, so you
> can see the admin interface as well.
>
> Have at it!
>
> Thanks,
> Rob Thorne
> Torenware Networks
>
>
> ____________________________________________________________
> You received this message as a subscriber on the list:
>      civicrm-dev@...
> To be removed from the list, send any message to:
>      civicrm-dev-unsubscribe@...
>
> For all list information and functions, see:
>      http://lists.civicrm.org/lists/info/civicrm-dev
>


--
lobo

http://civicrm.org/blog/
http://civicrm.org/
http://lobostravel.blogspot.com/
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

Re: Announcing CiviVoter And Canvasser

by Kieran Lal :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi, I am evaluating CiviVoter for a customer use case.

Is this the latest version of CiviVoter ? http://cvdemo.torenware.com/downloads/civicrm-1.6-r8285-voter-alpha-3-drupal-php5.tar.gz

Is there a username:password for the demo site, or is it unnecessary?  I couldn't see how to create a canvasser node.

The customer use case is they would like to show information about their own elected officials in the website for each user.  So, once the Drupal user was a CiviCRM contact we would want to update that contact record with their local political representatives information.  Then we could extract that information using CiviNode and display it accordingly through out the site.

Cheers,
Kieran

On 3/22/07, Rob Thorne <rob@...> wrote:
Hello CivCRM users and developers!

I'd like to announce a developer's release of CiviVoter and Canvassers,
two tools for managing voter files and contacts with voters during
political (and similar) campaigns.   The work  was sponsored by the
Green Party Of Canada, which has generously agreed to release it to the
general CiviCRM community.

I've just posted a demo site at http://cvdemo.torenware.com,  and will
post source files (a custom version of CiviCRM 1.6, and a Drupal module)
on that site shortly.  Here's a bit more info:

    *  CiviVoter is a new sub-system for CiviCRM. Its purpose is to
      manage a voter file for you (the kind you get from the your county
      registrar of voters, or your national elections authority). Since
      CiviCRM is a rich and rapidly improving system for managing
      contacts, a lot of what you'd want to do with a voter file is
      already a part of CiviCRM. CiviVoter adds tools for running phone
      banks (for calling voters) or foot canvasses (going door to door
      and meeting voters face to face).
    * Canvasser is a Drupal module for running phone banks and foot
      canvasses. It uses CiviVoter to manage the voter file, but uses
      Drupal modules like Events, CCK or Location to help manage
      volunteers, and to add additional UI.
    * We'd like to get some feedback on our "first generation" interface
      and work flow, and we've created some test accounts to help you do
      that. We've set up an imaginary political campaign for the
      Canadian House Of Commons (the Green Party of Canada sponsored
      this work, so why not?), and we've imported 100 "voter records".

I've set up two demo accounts,  Organizer (pw: demo)  and Volunteer (pw:
demo) so you can see what the site looks like from different points of
view.  I'll also be happy to give out accounts with admin access, so you
can see the admin interface as well.

Have at it!

Thanks,
Rob Thorne
Torenware Networks


____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev



--
To strive, to seek, to find, and not to yield.

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

Re: Announcing CiviVoter And Canvasser

by Kieran Lal :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.


On 7/3/07, Kieran Lal <kieran@...> wrote:
Hi, I am evaluating CiviVoter for a customer use case.

Is this the latest version of CiviVoter ? http://cvdemo.torenware.com/downloads/civicrm-1.6-r8285-voter-alpha-3-drupal-php5.tar.gz

Is there a username:password for the demo site, or is it unnecessary?  I couldn't see how to create a canvasser node.

The customer use case is they would like to show information about their own elected officials in the website for each user.  So, once the Drupal user was a CiviCRM contact we would want to update that contact record with their local political representatives information.  Then we could extract that information using CiviNode and display it accordingly through out the site.

Looks like I was barking up the wrong tree.

For people interested in the use case: http://sunlightlabs.com/api/

Cheers,
Kieran

 

Cheers,
Kieran


On 3/22/07, Rob Thorne <rob@...> wrote:
Hello CivCRM users and developers!

I'd like to announce a developer's release of CiviVoter and Canvassers,
two tools for managing voter files and contacts with voters during
political (and similar) campaigns.   The work  was sponsored by the
Green Party Of Canada, which has generously agreed to release it to the
general CiviCRM community.

I've just posted a demo site at http://cvdemo.torenware.com,  and will
post source files (a custom version of CiviCRM 1.6, and a Drupal module)
on that site shortly.  Here's a bit more info:

    *  CiviVoter is a new sub-system for CiviCRM. Its purpose is to
      manage a voter file for you (the kind you get from the your county
      registrar of voters, or your national elections authority). Since
      CiviCRM is a rich and rapidly improving system for managing
      contacts, a lot of what you'd want to do with a voter file is
      already a part of CiviCRM. CiviVoter adds tools for running phone
      banks (for calling voters) or foot canvasses (going door to door
      and meeting voters face to face).
    * Canvasser is a Drupal module for running phone banks and foot
      canvasses. It uses CiviVoter to manage the voter file, but uses
      Drupal modules like Events, CCK or Location to help manage
      volunteers, and to add additional UI.
    * We'd like to get some feedback on our "first generation" interface
      and work flow, and we've created some test accounts to help you do
      that. We've set up an imaginary political campaign for the
      Canadian House Of Commons (the Green Party of Canada sponsored
      this work, so why not?), and we've imported 100 "voter records".

I've set up two demo accounts,  Organizer (pw: demo)  and Volunteer (pw:
demo) so you can see what the site looks like from different points of
view.  I'll also be happy to give out accounts with admin access, so you
can see the admin interface as well.

Have at it!

Thanks,
Rob Thorne
Torenware Networks


____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev



--
To strive, to seek, to find, and not to yield.



--
To strive, to seek, to find, and not to yield.

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

Re: Announcing CiviVoter And Canvasser

by Rob Thorne :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Kieran,

The SunLight Labs work is really interesting, and I'm inclined to use it
as well for this sort of application.  I *have* developed something like
this for use with CiviVoter for Canadian Federal Ridings, but cannot
release it, since it's based upon data the Canadian elections agency
sells to political parties.  The code puts up a block where you enter
your Canadian postal code, and it redirects you to  a page for your
federal riding.  The Green Party of Canada is using this code in
production.  If you know someone who has access to the file, the code
itself can be released under GPL.

CiviVoter is pretty narrowly focused on a single problem: helping people
working with a voter file for a reaching people efficiently in that
file.  It has good support for linking volunteers up with voters for
calling in phone banks, and for getting walk lists for foot canvasses.  
Most of the handling of the voter file is on the CiviCRM side, and most
of the volunteer handling code is implemented using the Drupal module.

Newer versions of CiviVoter and Canvasser, though,  do have a feature
that could be extended for use with your SunLight Labs Congressional
lookup.  I wrote a module for the Green Party of Canada called Phone
Lookup, which calls a commercial REST service called API411, which is a
product of the WhitePages.com people.  The federal Canadian voter file
does not have phone numbers, so to do phone banking, either you have to
merge in your own numbers, or you need to look them up on the fly.  
Using Phone Lookup, when a volunteer needs somebody to call, I walk the
voter list (a CiviCRM group pulled from the voter file) and generate web
service queries until I find a voter with a valid phone number.  Both
hits on the service and misses are cached.  Between the relative
efficiency of the on-line database and the local cache, this is pretty
fast, and not noticeable to the volunteer waiting for the web page to
render.

I'm about to release Phone Lookup -- the full API411 spec is under NDA,
and up until two weeks ago, the WhitePages.com people did not want the
code released.  They've since changed their mind, and have given their
blessing to release of Phone Lookup under GPL.

Some of this code would work nicely for your use case as well, since you
only need to query the SLL service once per zip code.  I already have
code that handles the caching, and that can "automagically" fill in a
Congressional District ID field for any record you pull up -- it would
first check the cache, and if the zip code did not have a known CD, do
the lookup.  This is transparent, and very fast.


Rob

Kieran Lal wrote:

>
>     The customer use case is they would like to show information about
>     their own elected officials in the website for each user.  So,
>     once the Drupal user was a CiviCRM contact we would want to update
>     that contact record with their local political representatives
>     information.  Then we could extract that information using
>     CiviNode and display it accordingly through out the site.
>
>
> Looks like I was barking up the wrong tree.
>
> For people interested in the use case: http://sunlightlabs.com/api/
>
> Cheers,
> Kieran
>
>  
>
>     Cheers,
>     Kieran
>
>
>     On 3/22/07, *Rob Thorne* <rob@...
>     <mailto:rob@...>> wrote:
>
>         Hello CivCRM users and developers!
>
>         I'd like to announce a developer's release of CiviVoter and
>         Canvassers,
>         two tools for managing voter files and contacts with voters during
>         political (and similar) campaigns.   The work  was sponsored
>         by the
>         Green Party Of Canada, which has generously agreed to release
>         it to the
>         general CiviCRM community.
>
>         I've just posted a demo site at
>         http://cvdemo.torenware.com,  and will
>         post source files (a custom version of CiviCRM 1.6, and a
>         Drupal module)
>         on that site shortly.  Here's a bit more info:
>
>             *  CiviVoter is a new sub-system for CiviCRM. Its purpose
>         is to
>               manage a voter file for you (the kind you get from the
>         your county
>               registrar of voters, or your national elections
>         authority). Since
>               CiviCRM is a rich and rapidly improving system for managing
>               contacts, a lot of what you'd want to do with a voter
>         file is
>               already a part of CiviCRM. CiviVoter adds tools for
>         running phone
>               banks (for calling voters) or foot canvasses (going door
>         to door
>               and meeting voters face to face).
>             * Canvasser is a Drupal module for running phone banks and
>         foot
>               canvasses. It uses CiviVoter to manage the voter file,
>         but uses
>               Drupal modules like Events, CCK or Location to help manage
>               volunteers, and to add additional UI.
>             * We'd like to get some feedback on our "first generation"
>         interface
>               and work flow, and we've created some test accounts to
>         help you do
>               that. We've set up an imaginary political campaign for the
>               Canadian House Of Commons (the Green Party of Canada
>         sponsored
>               this work, so why not?), and we've imported 100 "voter
>         records".
>
>         I've set up two demo accounts,  Organizer (pw: demo)  and
>         Volunteer (pw:
>         demo) so you can see what the site looks like from different
>         points of
>         view.  I'll also be happy to give out accounts with admin
>         access, so you
>         can see the admin interface as well.
>
>         Have at it!
>
>         Thanks,
>         Rob Thorne
>         Torenware Networks
>
>
>         ____________________________________________________________
>         You received this message as a subscriber on the list:
>              civicrm-dev@...
>         <mailto:civicrm-dev@...>
>         To be removed from the list, send any message to:
>              civicrm-dev-unsubscribe@...
>         <mailto:civicrm-dev-unsubscribe@...>
>
>         For all list information and functions, see:
>              http://lists.civicrm.org/lists/info/civicrm-dev
>
>
>
>
>     --
>     To strive, to seek, to find, and not to yield.
>
>
>
>
> --
> To strive, to seek, to find, and not to yield.

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

Re: Announcing CiviVoter And Canvasser

by Donald Lobo :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

kieran's email inspired me to sit and hack out a fairly quick
integration with the sunlight API :)

A preliminary version of the integration is now in trunk :) You can
read more details about it at:

http://civicrm.org/node/205

and how you can potentially jump in and help build the rest :)

lobo

On 7/3/07, Rob Thorne <rob@...> wrote:

> Kieran,
>
> The SunLight Labs work is really interesting, and I'm inclined to use it
> as well for this sort of application.  I *have* developed something like
> this for use with CiviVoter for Canadian Federal Ridings, but cannot
> release it, since it's based upon data the Canadian elections agency
> sells to political parties.  The code puts up a block where you enter
> your Canadian postal code, and it redirects you to  a page for your
> federal riding.  The Green Party of Canada is using this code in
> production.  If you know someone who has access to the file, the code
> itself can be released under GPL.
>
> CiviVoter is pretty narrowly focused on a single problem: helping people
> working with a voter file for a reaching people efficiently in that
> file.  It has good support for linking volunteers up with voters for
> calling in phone banks, and for getting walk lists for foot canvasses.
> Most of the handling of the voter file is on the CiviCRM side, and most
> of the volunteer handling code is implemented using the Drupal module.
>
> Newer versions of CiviVoter and Canvasser, though,  do have a feature
> that could be extended for use with your SunLight Labs Congressional
> lookup.  I wrote a module for the Green Party of Canada called Phone
> Lookup, which calls a commercial REST service called API411, which is a
> product of the WhitePages.com people.  The federal Canadian voter file
> does not have phone numbers, so to do phone banking, either you have to
> merge in your own numbers, or you need to look them up on the fly.
> Using Phone Lookup, when a volunteer needs somebody to call, I walk the
> voter list (a CiviCRM group pulled from the voter file) and generate web
> service queries until I find a voter with a valid phone number.  Both
> hits on the service and misses are cached.  Between the relative
> efficiency of the on-line database and the local cache, this is pretty
> fast, and not noticeable to the volunteer waiting for the web page to
> render.
>
> I'm about to release Phone Lookup -- the full API411 spec is under NDA,
> and up until two weeks ago, the WhitePages.com people did not want the
> code released.  They've since changed their mind, and have given their
> blessing to release of Phone Lookup under GPL.
>
> Some of this code would work nicely for your use case as well, since you
> only need to query the SLL service once per zip code.  I already have
> code that handles the caching, and that can "automagically" fill in a
> Congressional District ID field for any record you pull up -- it would
> first check the cache, and if the zip code did not have a known CD, do
> the lookup.  This is transparent, and very fast.
>
>
> Rob
>
> Kieran Lal wrote:
> >
> >     The customer use case is they would like to show information about
> >     their own elected officials in the website for each user.  So,
> >     once the Drupal user was a CiviCRM contact we would want to update
> >     that contact record with their local political representatives
> >     information.  Then we could extract that information using
> >     CiviNode and display it accordingly through out the site.
> >
> >
> > Looks like I was barking up the wrong tree.
> >
> > For people interested in the use case: http://sunlightlabs.com/api/
> >
> > Cheers,
> > Kieran
> >
> >
> >
> >     Cheers,
> >     Kieran
> >
> >
> >     On 3/22/07, *Rob Thorne* <rob@...
> >     <mailto:rob@...>> wrote:
> >
> >         Hello CivCRM users and developers!
> >
> >         I'd like to announce a developer's release of CiviVoter and
> >         Canvassers,
> >         two tools for managing voter files and contacts with voters during
> >         political (and similar) campaigns.   The work  was sponsored
> >         by the
> >         Green Party Of Canada, which has generously agreed to release
> >         it to the
> >         general CiviCRM community.
> >
> >         I've just posted a demo site at
> >         http://cvdemo.torenware.com,  and will
> >         post source files (a custom version of CiviCRM 1.6, and a
> >         Drupal module)
> >         on that site shortly.  Here's a bit more info:
> >
> >             *  CiviVoter is a new sub-system for CiviCRM. Its purpose
> >         is to
> >               manage a voter file for you (the kind you get from the
> >         your county
> >               registrar of voters, or your national elections
> >         authority). Since
> >               CiviCRM is a rich and rapidly improving system for managing
> >               contacts, a lot of what you'd want to do with a voter
> >         file is
> >               already a part of CiviCRM. CiviVoter adds tools for
> >         running phone
> >               banks (for calling voters) or foot canvasses (going door
> >         to door
> >               and meeting voters face to face).
> >             * Canvasser is a Drupal module for running phone banks and
> >         foot
> >               canvasses. It uses CiviVoter to manage the voter file,
> >         but uses
> >               Drupal modules like Events, CCK or Location to help manage
> >               volunteers, and to add additional UI.
> >             * We'd like to get some feedback on our "first generation"
> >         interface
> >               and work flow, and we've created some test accounts to
> >         help you do
> >               that. We've set up an imaginary political campaign for the
> >               Canadian House Of Commons (the Green Party of Canada
> >         sponsored
> >               this work, so why not?), and we've imported 100 "voter
> >         records".
> >
> >         I've set up two demo accounts,  Organizer (pw: demo)  and
> >         Volunteer (pw:
> >         demo) so you can see what the site looks like from different
> >         points of
> >         view.  I'll also be happy to give out accounts with admin
> >         access, so you
> >         can see the admin interface as well.
> >
> >         Have at it!
> >
> >         Thanks,
> >         Rob Thorne
> >         Torenware Networks
> >
> >
> >         ____________________________________________________________
> >         You received this message as a subscriber on the list:
> >              civicrm-dev@...
> >         <mailto:civicrm-dev@...>
> >         To be removed from the list, send any message to:
> >              civicrm-dev-unsubscribe@...
> >         <mailto:civicrm-dev-unsubscribe@...>
> >
> >         For all list information and functions, see:
> >              http://lists.civicrm.org/lists/info/civicrm-dev
> >
> >
> >
> >
> >     --
> >     To strive, to seek, to find, and not to yield.
> >
> >
> >
> >
> > --
> > To strive, to seek, to find, and not to yield.
>
> ____________________________________________________________
> You received this message as a subscriber on the list:
>      civicrm-dev@...
> To be removed from the list, send any message to:
>      civicrm-dev-unsubscribe@...
>
> For all list information and functions, see:
>      http://lists.civicrm.org/lists/info/civicrm-dev
>


--
lobo

http://civicrm.org/blog/
http://civicrm.org/
http://lobostravel.blogspot.com/
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

Re: Announcing CiviVoter And Canvasser

by Kieran Lal :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



On 7/4/07, Donald Lobo <donald.lobo@...> wrote:
kieran's email inspired me to sit and hack out a fairly quick
integration with the sunlight API :)

A preliminary version of the integration is now in trunk :) You can
read more details about it at:

http://civicrm.org/node/205

and how you can potentially jump in and help build the rest :)

Lobo this is fantastic and it's a key part of why so many NPO's an advocacy organizations pay top dollar.  CivicSpace Labs is actively doing client work on the SunLight APIs if anyone else has use cases or would like to see further development, let me know and we will make sure Drupal modules are GPL'd and made available for everyone.

Cheers,
Kieran
 

lobo

On 7/3/07, Rob Thorne <rob@...> wrote:

> Kieran,
>
> The SunLight Labs work is really interesting, and I'm inclined to use it
> as well for this sort of application.  I *have* developed something like
> this for use with CiviVoter for Canadian Federal Ridings, but cannot
> release it, since it's based upon data the Canadian elections agency
> sells to political parties.  The code puts up a block where you enter
> your Canadian postal code, and it redirects you to  a page for your
> federal riding.  The Green Party of Canada is using this code in
> production.  If you know someone who has access to the file, the code
> itself can be released under GPL.
>
> CiviVoter is pretty narrowly focused on a single problem: helping people
> working with a voter file for a reaching people efficiently in that
> file.  It has good support for linking volunteers up with voters for
> calling in phone banks, and for getting walk lists for foot canvasses.
> Most of the handling of the voter file is on the CiviCRM side, and most
> of the volunteer handling code is implemented using the Drupal module.
>
> Newer versions of CiviVoter and Canvasser, though,  do have a feature
> that could be extended for use with your SunLight Labs Congressional
> lookup.  I wrote a module for the Green Party of Canada called Phone
> Lookup, which calls a commercial REST service called API411, which is a
> product of the WhitePages.com people.  The federal Canadian voter file
> does not have phone numbers, so to do phone banking, either you have to
> merge in your own numbers, or you need to look them up on the fly.
> Using Phone Lookup, when a volunteer needs somebody to call, I walk the
> voter list (a CiviCRM group pulled from the voter file) and generate web
> service queries until I find a voter with a valid phone number.  Both
> hits on the service and misses are cached.  Between the relative
> efficiency of the on-line database and the local cache, this is pretty
> fast, and not noticeable to the volunteer waiting for the web page to
> render.
>
> I'm about to release Phone Lookup -- the full API411 spec is under NDA,
> and up until two weeks ago, the WhitePages.com people did not want the
> code released.  They've since changed their mind, and have given their
> blessing to release of Phone Lookup under GPL.
>
> Some of this code would work nicely for your use case as well, since you
> only need to query the SLL service once per zip code.  I already have
> code that handles the caching, and that can "automagically" fill in a
> Congressional District ID field for any record you pull up -- it would
> first check the cache, and if the zip code did not have a known CD, do
> the lookup.  This is transparent, and very fast.
>
>
> Rob
>
> Kieran Lal wrote:
> >
> >     The customer use case is they would like to show information about
> >     their own elected officials in the website for each user.  So,
> >     once the Drupal user was a CiviCRM contact we would want to update
> >     that contact record with their local political representatives
> >     information.  Then we could extract that information using
> >     CiviNode and display it accordingly through out the site.
> >
> >
> > Looks like I was barking up the wrong tree.
> >
> > For people interested in the use case: http://sunlightlabs.com/api/
> >
> > Cheers,
> > Kieran
> >
> >
> >

> >     Cheers,
> >     Kieran
> >
> >
> >     On 3/22/07, *Rob Thorne* <rob@...
> >     <mailto:rob@...>> wrote:
> >
> >         Hello CivCRM users and developers!
> >
> >         I'd like to announce a developer's release of CiviVoter and
> >         Canvassers,
> >         two tools for managing voter files and contacts with voters during
> >         political (and similar) campaigns.   The work  was sponsored
> >         by the
> >         Green Party Of Canada, which has generously agreed to release
> >         it to the
> >         general CiviCRM community.
> >
> >         I've just posted a demo site at
> >         http://cvdemo.torenware.com ,  and will
> >         post source files (a custom version of CiviCRM 1.6, and a
> >         Drupal module)
> >         on that site shortly.  Here's a bit more info:
> >
> >             *  CiviVoter is a new sub-system for CiviCRM. Its purpose
> >         is to
> >               manage a voter file for you (the kind you get from the
> >         your county
> >               registrar of voters, or your national elections
> >         authority). Since

> >               CiviCRM is a rich and rapidly improving system for managing
> >               contacts, a lot of what you'd want to do with a voter
> >         file is
> >               already a part of CiviCRM. CiviVoter adds tools for
> >         running phone
> >               banks (for calling voters) or foot canvasses (going door
> >         to door
> >               and meeting voters face to face).
> >             * Canvasser is a Drupal module for running phone banks and
> >         foot
> >               canvasses. It uses CiviVoter to manage the voter file,
> >         but uses
> >               Drupal modules like Events, CCK or Location to help manage
> >               volunteers, and to add additional UI.
> >             * We'd like to get some feedback on our "first generation"
> >         interface
> >               and work flow, and we've created some test accounts to
> >         help you do
> >               that. We've set up an imaginary political campaign for the
> >               Canadian House Of Commons (the Green Party of Canada
> >         sponsored
> >               this work, so why not?), and we've imported 100 "voter
> >         records".
> >
> >         I've set up two demo accounts,  Organizer (pw: demo)  and
> >         Volunteer (pw:
> >         demo) so you can see what the site looks like from different
> >         points of
> >         view.  I'll also be happy to give out accounts with admin
> >         access, so you
> >         can see the admin interface as well.
> >
> >         Have at it!
> >
> >         Thanks,
> >         Rob Thorne
> >         Torenware Networks
> >
> >
> >         ____________________________________________________________
> >         You received this message as a subscriber on the list:
> >              civicrm-dev@...
> >         <mailto:civicrm-dev@...>
> >         To be removed from the list, send any message to:
> >              civicrm-dev-unsubscribe@...
> >         <mailto:civicrm-dev-unsubscribe@...>
> >
> >         For all list information and functions, see:
> >              http://lists.civicrm.org/lists/info/civicrm-dev
> >
> >
> >
> >
> >     --
> >     To strive, to seek, to find, and not to yield.
> >
> >
> >
> >
> > --
> > To strive, to seek, to find, and not to yield.
>
> ____________________________________________________________
> You received this message as a subscriber on the list:
>      civicrm-dev@...
> To be removed from the list, send any message to:
>      civicrm-dev-unsubscribe@...
>
> For all list information and functions, see:
>      http://lists.civicrm.org/lists/info/civicrm-dev
>


--
lobo

http://civicrm.org/blog/
http://civicrm.org/
http://lobostravel.blogspot.com/



--
To strive, to seek, to find, and not to yield.

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev