<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The FEC&#8217;s Disclosure Data Catalog</title>
	<atom:link href="http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/</link>
	<description>Derek Willis' weblog on investigative and computer-assisted reporting.</description>
	<lastBuildDate>Mon, 08 Mar 2010 02:26:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wendell</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-142397</link>
		<dc:creator>Wendell</dc:creator>
		<pubDate>Tue, 10 Nov 2009 16:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-142397</guid>
		<description>Weighing into a discussion between Aron and Derek is like getting between two elephants. In this case, they are both right.

It seems trivial for the FEC to move the address of donors fields from the electronic files into the FTP files and most of the other things Aron suggests.

But as one who has worked with these things for a long time, I also am glad that the FTP filings remain stable. The single identifier would be a great thing (try doing a history on Hillary or Obama without it).

What I fear is that the Senate will finally be forced to go to electronic filing and the FTP files will go away. The electronic filing system, dictated by the software companies, is beyond horrible.

The other point I would make is that you should not expect &quot;data quality&quot; from the FEC. As a regulatory agency it is purposely weak (mainly regulating members of Congress), and I don&#039;t think the agency uses the public disclosures in its regulatory audits of campaigns.</description>
		<content:encoded><![CDATA[<p>Weighing into a discussion between Aron and Derek is like getting between two elephants. In this case, they are both right.</p>
<p>It seems trivial for the FEC to move the address of donors fields from the electronic files into the FTP files and most of the other things Aron suggests.</p>
<p>But as one who has worked with these things for a long time, I also am glad that the FTP filings remain stable. The single identifier would be a great thing (try doing a history on Hillary or Obama without it).</p>
<p>What I fear is that the Senate will finally be forced to go to electronic filing and the FTP files will go away. The electronic filing system, dictated by the software companies, is beyond horrible.</p>
<p>The other point I would make is that you should not expect &#8220;data quality&#8221; from the FEC. As a regulatory agency it is purposely weak (mainly regulating members of Congress), and I don&#8217;t think the agency uses the public disclosures in its regulatory audits of campaigns.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-141851</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Fri, 30 Oct 2009 11:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-141851</guid>
		<description>Oops!  I meant good follow up reporting will make for certainty...not uncertainty.</description>
		<content:encoded><![CDATA[<p>Oops!  I meant good follow up reporting will make for certainty&#8230;not uncertainty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-141850</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Fri, 30 Oct 2009 11:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-141850</guid>
		<description>Hi Derek,

  The quality of the data isn&#039;t about to change.  Why?  The FEC isn&#039;t going to enforce &#039;quality&#039; reporting.  This isn&#039;t a criticism, but a realization that the law is so quirky, with so many exceptions, that errors are going to be common.  Unfortunately, those few who chose to obfuscate in a critical reporting period will likely be able to do so in the short run.

  Unless the FEC mandates donors to have unique identifiers (say for instance, SSN - something never likely to happen), there will always be uncertainty when aggregating donors by name.  The same is true for &#039;intent&#039; of donation...is it because of employment or ideology?

  Although we in the data world like clean, constrained data, it&#039;ll never happen with public records.  The agencies have too small a budget and too little time to make timely checks on filed information.

  In other words, it is what it is, and only good follow up reporting will make for uncertainty in data with so many anomalies. 

  BTW, almost all of the recent changes mandating &#039;improved&#039; disclosure have in fact confused things.  Much of the &#039;extra&#039; data is duplicate (lobby bundling, for example).  

  One huge improvement would be to limit itemization of donors aggregating over $1,000 per cycle...that&#039;s right, actually reducing disclosure.  It would instantly make the data more manageable, protect privacy and let us zero in on the true heavy weights in our little world.</description>
		<content:encoded><![CDATA[<p>Hi Derek,</p>
<p>  The quality of the data isn&#8217;t about to change.  Why?  The FEC isn&#8217;t going to enforce &#8216;quality&#8217; reporting.  This isn&#8217;t a criticism, but a realization that the law is so quirky, with so many exceptions, that errors are going to be common.  Unfortunately, those few who chose to obfuscate in a critical reporting period will likely be able to do so in the short run.</p>
<p>  Unless the FEC mandates donors to have unique identifiers (say for instance, SSN &#8211; something never likely to happen), there will always be uncertainty when aggregating donors by name.  The same is true for &#8216;intent&#8217; of donation&#8230;is it because of employment or ideology?</p>
<p>  Although we in the data world like clean, constrained data, it&#8217;ll never happen with public records.  The agencies have too small a budget and too little time to make timely checks on filed information.</p>
<p>  In other words, it is what it is, and only good follow up reporting will make for uncertainty in data with so many anomalies. </p>
<p>  BTW, almost all of the recent changes mandating &#8216;improved&#8217; disclosure have in fact confused things.  Much of the &#8216;extra&#8217; data is duplicate (lobby bundling, for example).  </p>
<p>  One huge improvement would be to limit itemization of donors aggregating over $1,000 per cycle&#8230;that&#8217;s right, actually reducing disclosure.  It would instantly make the data more manageable, protect privacy and let us zero in on the true heavy weights in our little world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serdar Tumgoren</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-141781</link>
		<dc:creator>Serdar Tumgoren</dc:creator>
		<pubDate>Thu, 29 Oct 2009 17:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-141781</guid>
		<description>Derek,
The &quot;two classes&quot; of users description is apt. I&#039;ve been working daily with this data for months and every day I discover a new quirk. I can&#039;t imagine anyone -- even a seasoned data analyst -- diving into these data sets and doing anything moderately sophisticated (and accurate) in a short amount of time. The learning curve is just too high.

The Sunlight Foundation folks are on the money with their message to the FEC: Focus on data quality and accuracy first, then worry about the bells and whistles.</description>
		<content:encoded><![CDATA[<p>Derek,<br />
The &#8220;two classes&#8221; of users description is apt. I&#8217;ve been working daily with this data for months and every day I discover a new quirk. I can&#8217;t imagine anyone &#8212; even a seasoned data analyst &#8212; diving into these data sets and doing anything moderately sophisticated (and accurate) in a short amount of time. The learning curve is just too high.</p>
<p>The Sunlight Foundation folks are on the money with their message to the FEC: Focus on data quality and accuracy first, then worry about the bells and whistles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-141764</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Thu, 29 Oct 2009 13:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-141764</guid>
		<description>The consistency is admirable in terms of people being able to use data across time. It&#039;s not admirable in terms of overall usefulness, as you rightly point out. And electronic filing is still an unwieldy mess that has made for two classes of campaign finance data users: those who have the time and ability to figure out the electronic data and those who cannot.</description>
		<content:encoded><![CDATA[<p>The consistency is admirable in terms of people being able to use data across time. It&#8217;s not admirable in terms of overall usefulness, as you rightly point out. And electronic filing is still an unwieldy mess that has made for two classes of campaign finance data users: those who have the time and ability to figure out the electronic data and those who cannot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aron Pilhofer</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-141758</link>
		<dc:creator>Aron Pilhofer</dc:creator>
		<pubDate>Thu, 29 Oct 2009 12:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-141758</guid>
		<description>Admirably consistent? Are you kidding? There&#039;s nothing admirable about those text files, which have changed exactly once since 1979. 

* Not when the FEC has been collecting full donor addresses since 2002 for all but Senators and the DSCC (last I checked the NRSC files electronically -- only DSCC is a holdout), and cannot seem to bother itself to get those data out there except through the extraordinarily complex electronic filing system. 

* Not when there is a mandate for committees to report names as five discreet data fields, yet it continues to shove them into a single field. 

* Not when they STILL have employer/occuptation (again, separate data fields) shoved into a single field in the FTP data that is too small to accommodate them. 

Frankly, my patience is wearing thin on this front. This has been the one thing people have been asking for for years, and it&#039;s the easiest thing in the world to figure out: Keep the existing files, and create a new set of data files that actually reflects the data they collect. Done! 

Hell, I&#039;ll even volunteer to write the SQL to export those files if the FEC promises to actually produce them.</description>
		<content:encoded><![CDATA[<p>Admirably consistent? Are you kidding? There&#8217;s nothing admirable about those text files, which have changed exactly once since 1979. </p>
<p>* Not when the FEC has been collecting full donor addresses since 2002 for all but Senators and the DSCC (last I checked the NRSC files electronically &#8212; only DSCC is a holdout), and cannot seem to bother itself to get those data out there except through the extraordinarily complex electronic filing system. </p>
<p>* Not when there is a mandate for committees to report names as five discreet data fields, yet it continues to shove them into a single field. </p>
<p>* Not when they STILL have employer/occuptation (again, separate data fields) shoved into a single field in the FTP data that is too small to accommodate them. </p>
<p>Frankly, my patience is wearing thin on this front. This has been the one thing people have been asking for for years, and it&#8217;s the easiest thing in the world to figure out: Keep the existing files, and create a new set of data files that actually reflects the data they collect. Done! </p>
<p>Hell, I&#8217;ll even volunteer to write the SQL to export those files if the FEC promises to actually produce them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-141706</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 28 Oct 2009 18:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-141706</guid>
		<description>Thanks for the info.

I support watchdogs more closely evaluating whether government data disclosure efforts live up to the letter and spirit of their legal mandates. Thank you for doing this.

Politicians can get a ton of good press for putting these things into law, but if the data products aren&#039;t executed successfully then the whole thing doesn&#039;t amount to much.

Will any of these new FEC products replace or greatly change your current campaign finance data collection process?</description>
		<content:encoded><![CDATA[<p>Thanks for the info.</p>
<p>I support watchdogs more closely evaluating whether government data disclosure efforts live up to the letter and spirit of their legal mandates. Thank you for doing this.</p>
<p>Politicians can get a ton of good press for putting these things into law, but if the data products aren&#8217;t executed successfully then the whole thing doesn&#8217;t amount to much.</p>
<p>Will any of these new FEC products replace or greatly change your current campaign finance data collection process?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-141698</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Wed, 28 Oct 2009 15:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-141698</guid>
		<description>Bob Biersack was put in charge of better coordinating the FEC&#039;s web offerings a little while ago, and the leadership PAC list in particular is a response to a law passed by Congress mandating broader lobbyist disclosure.</description>
		<content:encoded><![CDATA[<p>Bob Biersack was put in charge of better coordinating the FEC&#8217;s web offerings a little while ago, and the leadership PAC list in particular is a response to a law passed by Congress mandating broader lobbyist disclosure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://blog.thescoop.org/archives/2009/10/28/the-fecs-disclosure-data-catalog/comment-page-1/#comment-141697</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 28 Oct 2009 15:05:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thescoop.org/?p=5251#comment-141697</guid>
		<description>What&#039;s the onus for this move by FEC? Was there some new requirement passed into law?</description>
		<content:encoded><![CDATA[<p>What&#8217;s the onus for this move by FEC? Was there some new requirement passed into law?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
