The Sunlight Foundation just put out their Open Legislative Data Report Card. California received a D grade :-| Find out how your state is doing. Below is the methodology that they used to grade state legislatures.

Methodology 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: COMPLETENESS 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.

• 0 State provides full breadth of legislative artifacts Open States collects: bills, legislators, votes, and committees.
• -1 State does not provide stand-alone roll call votes.

TIMELINESS 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.

• 1 Multiple updates throughout the day, real time or as close to it as systems will allow.
• 0 Site updates once or twice daily, typically at the end of the legislative day.
• -1 Updates take longer than 24 hours to appear on the site, often up to a week.

EASE OF ACCESS Common web technologies such as Flash or JavaScript can cause problems when reviewing legislative data. We found that the majority of sites work fairly well without JavaScript, but some received lower scores due to being extremely difficult to navigate, impossible to bookmark bills, and in extreme cases, completely unusable.

• 1 Site was considered exceptionally well layed out by multiple evaluators, no issues with Javascript.
• 0 Site was deemed average by those that evaluated it and/or had minor Javascript dependencies.
• -1 Site was considered more difficult than average to use by members of staff or volunteers or had more severe Javascript dependencies.
• -2 Site was considered extremely difficult to use with a heavy reliance on irregular browser behavior and Javascript.

MACHINE READABILITY 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.

• 2 Essentially all data can be found in machine-readable formats.
• 1 Lots of data in machine readable format but substantial portions that still required scraping HTML.
• 0 No machine readable data but standard screen scraping techniques applied.
• -1 Site had information that was much more difficult than average to collect. (Data only accessible via PDF or that required screen scraper to emulate Javascript.)
• -2 Site had information that was unaccessible to Open States due to use of scanned PDFs.

USE OF COMMONLY OWNED STANDARDS 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.

• 1 State made an effort to go above and beyond.
• 0 State provided bills in PDF and/or HTML format and nothing better (plaintext, ODT, etc.).
• -1 State only provided bills in a proprietary format.

PERMANENCE 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.

• 2 All information is avaialble in a permanent location and data goes back a reasonable amount of time (a decade or so).
• 1 Almost all information has a permanent location but a single data set doesn't. (Or a recent change to the site has wiped out historical links but information appears to be preservable going forward.)
• 0 Legislator & committee information lacks a permanent location (such as committees and legislators) but most is acceptable.
• -1 Ability to link to old information is badly damaged and and/or there is less than a decade of historical information.
• -2 Vital information like bills or versions lack a permanent location.

Continue Reading →