[Tech] Re: Supporter database status

[Jamie O'Keefe]

On 3/9/07, Jamie O'Keefe <jokeefe at jamesokeefe.org> wrote:
> Open issues (For CiviCRM):
>
> 1.  Does it do what the contributor database does and if not, can we
> write code to do what Dan needs the contributor db to do?

Seems like it might, but we should need to rewrite custom OCPF
contributor report code.

> 2.  What features are not in CiviCRM and can we write add-ins to
> perform those functions?

If not in there, then we can always add to the schema and write code
to deal with those tables and joining them.

> 3.  What is the schema for CiviCRM and how can we merge our data into it?

For the schema, see:

http://wiki.civicrm.org/confluence/display/CRM/CiviCRM+ERD

CiviCRM can import data, see:

http://wiki.civicrm.org/confluence/display/CRMDOC/Importing+Data (new,
but incomplete)

or

http://wiki.civicrm.org/confluence/display/CRM/Import+Contacts+from+Other+Sources
(older)

or

http://wiki.civicrm.org/confluence/display/CRM/Importing+Contributions

> 4.  Does it support access to the data on a town by town basis?

Haven't figured that out yes, but I think so.

> 5.  What do we need in the voter schema, what features does the voter
> lookup app need, how will we handle updates to the voter data from the
> state, how will we link the voter data with the CiviCRM supporter
> data, as well as under what cases will we merge new voter data into
> the CiviCRM supporter data?

To be defined, but I will explore them.

> 6.  There are 4 million+ voter records that the state has?  How can we
> setup the database to store that data in memory efficiently and how
> much memory will we need to do it?  John Eskew, might you be able to
> answer this one?

Still need to answer this question, but found this article which I
hope we will be able to use in the near future:

http://wiki.civicrm.org/confluence/display/CRM/Large+Canadian+Political+Database+implementation

Jamie
> Jamie
>


-- 
James O'Keefe
www.jamesokeefe.org