Design Schedule B tab on committee page

[noahmanger]

Goal: Design how Schedule B summary data will be displayed on the committee pages

Criteria: Static comps demonstrating the design.

Steps:

• Identify what information will be shown and how it varies by committee
• Design comps
• Review with 18F
• Review with FEC

[noahmanger]

Trying to figure out what makes sense to show here, given the lack of normalization in the data. The two main things that I understand users to be looking for that would be found in this data are:

• Other committees they've given money to
• Vendors the committee has spent money with

I'm having a hard time imagining a useful way of showing vendor data, though. Any ideas?

Anything else this is missing?

[LindsayYoung]

The codes are kind of useful I have used them to explore what committees are spending money on.

[noahmanger]

Can you point me towards the list of codes?

[PaulClark2]

The transaction codes can help with contributions to other committees. The committee of interest's disbursements. But, operating expenditures, payments to vendors, are not coded. A complete list of transaction codes is here: www.fec.gov/finance/disclosure/metadata/DataDictionaryTransactionTypeCodes.shtml

[PaulClark2]

The list of transaction codes is extensive. Jeff and I can help with pulling out the committee-to-committee transactions if you think you want to go that way,

[jwchumley]

Along with where the money is spent, the purpose of disbursement is important for knowing what they are spending their money on. Unfortunately it is free form text so it is hard to work with but if you could do anything that makes good use of that it would be a winner I think.

[AmyKort]

I agree that the purpose of disbursement is interesting to users, so if there's a way to make that work, that would be great. Thanks!

[PaulClark2]

Comment from Christian: "I agree with the other comments about it being difficult to analyze disbursements because there isn't a uniform method of reporting the purposes. I wonder if we could somehow lump purposes into particular categories and allow public users to modify their own search criteria. For example, any disbursements with: consultant, staff, director, salary, payroll would be lumped under the category of Staff Expenses. Users could somehow modify the keywords."

[noahmanger]

Hmmm. This is interesting. So, if people have the ability to edit the search or keyword terms, that should happen on the query view. But we could present sort of "recommended shortcut" groupings that could then be edited.

Easier to explain with a picture (very crude... I just sketched it out):

This definitely entails making editorial decisions about what terms to include and we'll want to be transparent about those decisions and provide the necessary disclaimers. But if you think this is both permissable and doable I'm very interested.

[PaulClark2]

@noahmanger this is nice. I think with proper disclaimers this could be interesting and useful to people.

[noahmanger]

Cool! A few more questions:

1. What's the lift like, implementation-wise?
2. How many of these sub-totals do you think we'll have and how often will they change? Can we try sketching out what they would be?
3. Maybe a stretch, but would we be worried about people gaming the system by using different words in purpose descriptions?

[jmcarp]

We have a reasonably performant mechanism in place for updating summaries incrementally, and what you're describing seems similar enough to what we're already doing with the Schedule A receipts that this shouldn't be a huge implementation task for the API.

[PaulClark2]

@noahmanger This is the purpose of disbursement list Amy mentioned in the meeting: http://www.fec.gov/rad/pacs/documents/ExamplesofAdequatePurposes.pdf This is a place to start.

Here's more if you're interested: http://www.fec.gov/law/policy.shtml#purpose

[noahmanger]

Oh great! This is a great place to start. Could I ask your team to take a
swipe at grouping them?

On Mon, Jul 13, 2015 at 2:49 PM, Paul Clark notifications@github.com
wrote:

@noahmanger https://github.com/noahmanger This is the purpose of
disbursement list Amy mentioned in the meeting:
http://www.fec.gov/rad/pacs/documents/ExamplesofAdequatePurposes.pdf This
is a starting place.

—
Reply to this email directly or view it on GitHub
#315 (comment)
.

Noah Manger
18F http://18f.gsa.gov | Work: 415-696-6146

[PaulClark2]

Yup .... I'll ask FEC folks to take a swipe at grouping these.

[noahmanger]

Just to be clear, is this "Purpose of Disbursement" table the only one we're showing on this page, or did we also want to show something based on transaction codes?

[noahmanger]

@PaulClark2 just to try to close the loop on this.

I see this tab as having two tables: 1) Aggregate totals by Purpose and 3) 2) Aggregate totals by committee that received disbursement (to easily see how much was transferred to which committees).

Do we also want to aggregate by payee? (Like you have here?)