http://waldo.jaquith.org/blog/2008/02/rs-duplicate-bills/ Sun, 27 Jul 2008 01:32:30 +0000 http://wordpress.org/?v=2.6 http://waldo.jaquith.org/blog/2008/02/rs-duplicate-bills/#comment-19863 Joe Thu, 28 Feb 2008 14:15:47 +0000 http://waldo.jaquith.org/blog/2008/02/rs-duplicate-bills/#comment-19863 ...Nice. …Nice.

]]> http://waldo.jaquith.org/blog/2008/02/rs-duplicate-bills/#comment-19862 Waldo Jaquith Thu, 28 Feb 2008 13:03:41 +0000 http://waldo.jaquith.org/blog/2008/02/rs-duplicate-bills/#comment-19862 It's based only on the bill <em>summary</em>, not the bill itself. I wasn't sure that would be good enough, but manually reviewing ~100 bills with various sets of matching summaries showed a 100% correlation. The reason that I don't match the bills is for precisely the reason you describe. It’s based only on the bill summary, not the bill itself. I wasn’t sure that would be good enough, but manually reviewing ~100 bills with various sets of matching summaries showed a 100% correlation. The reason that I don’t match the bills is for precisely the reason you describe.

]]> http://waldo.jaquith.org/blog/2008/02/rs-duplicate-bills/#comment-19861 Joe Thu, 28 Feb 2008 04:34:31 +0000 http://waldo.jaquith.org/blog/2008/02/rs-duplicate-bills/#comment-19861 Did (and if so, how) you just set it up to begin the hash at "be it enacted...?" Otherwise, the committee assignment and delegate information at the top of the data that RS gets from LIS would prevent duplicate hashes. Did (and if so, how) you just set it up to begin the hash at “be it enacted…?” Otherwise, the committee assignment and delegate information at the top of the data that RS gets from LIS would prevent duplicate hashes.

]]>