I've had some comments / questions off-list that I thought it might be useful to address. One is the issue of compatibiilty --different unit websites using different platforms, different scripting language, etc etc.
What I had in mind was a completely plug and play interface that would be hosted on RPV.org -- local unit websites would just link to their county's version of the form. WAY easier tihat way and way easier to control quality, privacy issue compliance, etc. Each unit could upload their own top graphic / page chrome to make it look like part of their site, but it would be an RPV.org subdomain or subfolder. The form itself would need to be be the same basic template for everybody - the only variable being each unit would have different options listed in the data field for precinct, if known (drop down menu?)
civicrm.org is pretty impressive -- thanks for the link. Glad to know there's an open source solution out there. I wouldn't think this would need to involve completely redesigning what RPV currently has or starting from scratch. I'd think it would be relatively easy to add to the system they've currently got, if it turns out this is something that units would find useful -- add the precinct field, add another level of permissions, add the unit-specific front end template. If there's sufficient interest on the part of units, maybe RPV could have its web design consultants take a look
I don't think RPV's gonna let their databases out any time soon
All volunteer information stemming from online database submittable forms should also be converted to KML format so that we can have a digital representation of our volunteer base on a Google Earth of ArcGIS globe. The technology exists and is easily adaptable to existing websites.
BTW I "run" the RPVB website.
I guess for just a volunteer sign up form, it's not so complicated. But if we wanted to think about sharing more voter ID data than just that, it gets tricky. And I am not even talking about the DB programming aspect - just the rules involved.
Jim Huber said:I guess for just a volunteer sign up form, it's not so complicated. But if we wanted to think about sharing more voter ID data than just that, it gets tricky. And I am not even talking about the DB programming aspect - just the rules involved.
What exactly are the rules for handling the data? I'm a software engineer with very little political/campaign background, so I'm completely ignorant of such things. Also re: the transient nature of NOVA, perhaps correlating against credit reporting agencies and other consumer streams? Or would that be against those rules?