Data Sourcing Notification Requirements

[Nathan Woodhull]

In 2008 I remember that there was a requirement for users of the
Google polling place API to give Google credit as the source of the
data. I do not see any such requirement based on my quick read of the
current ToS. Is this correct?

Thanks,

Nathan Woodhull

[Nathan Woodhull]

Also, will external org precinct IDs (catalist, DNC, votervault, NCEC,
etc) be included in the API, as they are in the soon to be released
NOI data sets?

This will better enable us to integrate the Google API into our programs.

Nathan

[Daniel Berlin]

Hi,

On Fri, Oct 22, 2010 at 11:03 PM, Nathan Woodhull <wood...@gmail.com> wrote:

I forwarded your first question along to the right people to get an answer.

> Also, will external org precinct IDs (catalist, DNC, votervault, NCEC,
> etc) be included in the API, as they are in the soon to be released
> NOI data sets?

Undecided as of yet. There is basically an unlimited number of
mappings we could expose (and attempt to get, since we don't have all
of the ones you list even :P),
and by exposing some number of in the API, we'd have to keep them
*all* up to date.

It seems to me it would be better to expose some single neutral id,
release the files containing the mappings, and let folks do what they
want with both.

> This will better enable us to integrate the Google API into our programs.

Understood. We'll look into it.

[Nathan Woodhull]

Yes, we thought of this solution too.

We'll probably try to do this once NOI releases the mapping data on
Sunday if you can get an NOI ID into your output format. Including an
ID that we can use, perhaps in combination with NOI data, to map to
our own precinct IDs is a requirement for us to integrate the service
into our organizing program.

Nathan