A quick note on disclosure of information from paper filings of Independent Expenditures
We are implementing a process for creating data from filings we receive on paper. As we implement this process, you'll see some filings that were actually received some time ago moving through the disclosure process now. For example, some Independent Expenditure reports submitted by party Senatorial committees last month (which file on paper. . .) are now beginning to appear in data feeds here - http://query.nictusa.com/cgi-bin/dcdev/indexp/1
Don't be confused by the "filing date" for these DSCC disclosures - they were actually submitted on paper in August and early September, as you can see here - http://images.nictusa.com/cgi-bin/fecimg/?C00042366
Update on the new "real time" disclosure of independent expenditures and electioneering communications.
We're still working on the full processes for creating data for all 24-hour and 48-hour filings for independent expenditures and electioneering communications, but while we continue to build the final process we wanted to start making data available as soon as possible.[Read More]
As we get ready to launch the new data files for independent expenditure and electioneering communication filings during the 2010 general election campaign, I thought it would be useful to talk a little about what we will be including in the files and some of the changes that may come during this campaign season.[Read More]
The reporting requirements for Electioneering Communications (the broadcast ads running within 30 days of a primary or 60 days of a general election that make reference to federal candidates but don't "expressly advocate" their election or defeat) are a little different than most everything else we see, so we're struggling with the best way to present the data.[Read More]
For those of you who would like to get a jump on the release of detailed candidate disbursement data (scheduled for next
Monday Tuesday the 11th) here is a link to the schema for the file. We're actually adding schemas for the other files in the catalog as well.
We've also updated the draft metadata page for disbursements with some changes that we've made in the last week or so.
We're working on the front end for detailed candidate disbursement files, and we'd like to get your feedback. Take a look at these screenshots and let us know what you think.[Read More]
At long last, we're getting ready to create the first set of data files containing detailed entries on campaign committee spending. We're planning to start with data for all 2009-2010 congressional campaigns (including Senate) with data covering the period from January 1, 2009. There have been a couple of problems in preparing these data, but we think we have an approach that can work now.[Read More]
We're working to provide disclosure of submissions for independent expenditures and electioneering communications we'll receive during the 2010 campaign that's quicker and easier to use. We have some challenges in working with this data so we're interested in your thoughts.[Read More]
We're ready to start providing files in the data catalog that contain detailed information about the specific receipts and disbursements for candidates and committees.[Read More]
Quick question -- as we build more data files in XML, we need to know how descriptive the tags for data elements should be. We'll always try to give clear and comprehensive definitions for the data in the metadata pages, but the tags themselves might be abbreviated pretty extensively in order to reduce the size of the files. Would these abbreviated tags pose a problem for you in the way you expect to use the data? Or is it ok for us to be a little cryptic in the tagging itself so long as we're thorough somewhere else?
This will become much more important very soon as we build the process for downloading detailed information about contributions and expenditures. These files will ultimately contain millions of records (with a query process on the front end that will allow you to focus on just those entries you're interested in) so XML with long tags becomes a problem.
Post a comment to let us know how you feel. Thanks