This project contains information on how to automatically and successfully submit the contact forms of members of Congress.
This is what you need to power any system which aims to collect and submit electronic text from US citizens to their elected members of Congress.
Current Status
We're going through every member of the House of Representatives and codifying their contact form structure into YAML files that follow a simple schema. The /members directory already contains a few examples, such as this description of how to submit Roy Blunt's contact form.
We have completed the contact forms for the entire Senate!
Read our contribution guide for a fuller description.
But more briefly, if you'd like to help:
- Reply to an open ticket stating that you are currently working on this issue.
- Fork this repository.
- Check out the schema we're using to represent the steps involved in filling out a member's web form.
- Go visit that representative's website, and fill out a new YAML file describing how to submit the form.
- Save this file in
/membersas[bioguide].yaml, where[bioguide]is that member's Bioguide ID. - If you don't know their Bioguide ID: you can find it by visiting bioguide.congress.gov and looking at the end of the URL for a given member. For example, Sen. Chiesa's profile at
http://bioguide.congress.gov/scripts/biodisplay.pl?index=C001100means his Bioguide ID isC001100, and so his file would be placed at/members/C001100.yaml. - When you're done, submit a pull request with the new file.
Suggestions on making this process easier are quite welcome.
Why just the Senate?
Several reasons:
- The Senate is a smaller target (100 members) than the House (441 members).
- Senate contact form URLs are officially and centrally maintained in XML.
- Senate systems are less aggressive about rejecting letters by constituents thought not to be in their district.
Once the Senate data is good, we'll look at moving on to the House.
So I can drop my contract with [vendor name here]??
This is just data. Even once we have data for everyone, you'll still need to build a system that integrates this data. There's nothing here for tracking and storing errors and mistakes, strategies for re-trying, or storing any sort of user data or success statistics.
But what you won't have to do is keep up with Congress' constantly shifting websites. That's what this project does.
Submitting the contact form isn't enough. How do I get other data about members of Congress?
You can find detailed, reliable data about every current and historical member of Congress at the unitedstates/congress-legislators project.
The data in that project, also stored as YAML, is easily connect-able to this project via each member's Bioguide ID.
- The Sunlight Foundation is in the process of collecting this data and integrating it into OpenCongress.org.
This project is dedicated to the public domain. As spelled out in CONTRIBUTING:
The project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.
All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.
These graphics are pulled in near-real-time from http://opencongress.org, based on the last letter sent to each member through OpenCongress' contact tools.
You can use them to see at a glance how a particular contact form's formula is doing, and click the image for a failing form to see the error it generated. While the errors are specific to the formageddon implementation OpenCongress uses, the first line will likely contain some useful information--the form url was a 404, a selector wasn't found, etc.
Note: These are lagging indicators and should be checked against the repo's recent activity, meaning sometimes a form can be fixed but either not yet imported to OpenCongress, or just that no one has tried to contact that member since their form was fixed.
