(Note: Since the publication of this report card several states have come to us with additional information or made changes that would affect their score. Details are available below.)
|State||Completeness||Timeliness||Ease of Access||Machine Readibility||Standards||Permanence||Grade|
|District of Columbia||0||0||0||0||0||1||C|
Each state was evaluated in six categories based largely on the Ten Principles For Opening Up Government Information. Each score is based on at least two members of staff and a volunteer during our state survey. Additionally, state legislatures were contacted (unless noted in their score) to ensure that our information on bulk data availability and timeliness was as accurate as possible.
The specific criteria for each category are as follows:
We evaluated each state on the data collected by Open States: bills, legislators, committees, votes and events. We also took note if a state went above and beyond to provide this information and other relevant contextual information such as supporting documents, legislative journals and schedules. Points were deducted for missing data, often roll call votes.
Legislative information is most relevant when it happens, and many states are publishing information in real time. Unfortunately, there are also states where updates are more infrequent and showing up days after a legislative action took place. States were dinged if data took more than 48 hours to go online.
For many sites, the Open States team wrote scrapers to collect legislative information from the website code—a slow, tedious and error prone process. We collected data faster and more reliably when data was provided in a machine-readable format such as XML, JSON, CSV or via bulk downloads. If a state posted PDF image files or scanned documents, it received the lowest score possible.
Because our ability to access most of a state’s data is represented by the above “Machine Readability” metric, we decided to use this provision to measure how a state made their bill text available. Making text available in HTML or PDF is the norm, and was considered an acceptable commonly owned standard (PDFs are a commonly owned standard, but it would be certainly nice to see alternative options where bill text is only available via PDF). States that only make documents available in Microsoft Word or Wordperfect formats require an individual to purchase expensive software or rely on free alternatives that may not preserve the correct formatting. It is worth noting, all states except for two met the common criteria of providing HTML and/or PDF only, one state (Kansas) went above and beyond and another (Kentucky) did not even meet this threshold.
Many states move or remove information when a new session starts, much to the dismay of citizens seeking information on old proposals and researchers that may have cited a link (e.g. http://somelegislature.gov/HB1 vs http://somelegislature.gov/2011/HB1) only to see it point to a different bill in the following session. Tim Berners-Lee, inventor of the World Wide Web, wrote an article declaring Cool URIs Don’t Change and we agree.
This poses a particular challenge to us since every page on OpenStates.org points to the page we collected data from, but if a state changes their site then users lose the ability to check us against the original source. Most (but not all) states are good about at least preserving bill information, but few were equally as good about preserving information about out-of-office legislators and historical committees, equally important parts of the legislative process.
Since the initial publication of this report card on March 11th, 2013 some states have provided us with additional information or made changes in response that have affected their score. These changes are reflected below and noted on the report card itself.
Rhode Island - On March 12th, 2013 we confirmed with Rhode Island IT staff that data is updated in real-time, not weekly as we had initially been told. This information raised their score by 2 points, bringing them into the 'D' class.
New York - On March 12th, 2013 New York Senate staff reached out and clarified their update policy, raising their score by a point and putting them into the 'A' class. A better API was also pointed out to us, which may affect their machine readability score in the future.
Virginia - On March 22nd, 2013 Virginia Legislature staff clarified their update policy, raising their score by a point and putting them into the 'A' class. There is also potential that a coming change to their data availability will raise their score further.
Colorado - On March 22nd, 2013 it was determined via discussion with an IT manager from the Colorado Legislature that the bills that went missing were site errors and no actual data was affected. This made a large change in Colorado's Timeliness score, raising Colorado from an F to a C.