Closed noahmanger closed 8 years ago
Here's a first pass at a map of browse pages and sub-pages / sub-views:
The idea is that each category (blue box) contains a view of all items in that category (brown) (which is what we have now), and then multiple sub-pages (white) for more narrow data sets. Each sub-page:
The more work I do on this the more excited I am. In addition to all of the above, this is a great chance to more closely mirror the user's mental model of the data. You really see this in providing specific destinations to the different types of committees, since we've learned that people don't really have an overarching concept of "a committee".
Last thing, I've started a spreadsheet that I'll share in Slack for tracking which columns, filters, and details panel items we'll want to include in each subview.
This is great Noah—thanks so much for putting it together. It all makes sense to me, and jives with how I've been thinking about this section as well. Heads up @onezerojeremy
We've been working off of Noah's mockups here & have been doing lots of brainstorming with him and @onezerojeremy. (You've seen some debate in the slack channel :) )
Here's the latest thinking for the IA of the data side of the site I recommend opening in a new tab so that the text is actually legible:
Noah's 3 points above still stand, but here are a few new additions:
While we're still working through exactly how to approach those feature pages, you can see the sort of questions that could guide that introduction in the mockup.
(Orange outlines are areas of uncertainty, on the data set index side, I could especially use @LindsayYoung / @jmcarp 's expertise to whether or not we need these, and on the featurette side, I could use @onezerojeremy 's aid in refining)
My brain is a little melted at the moment, and this could likely do with some synchronous working sessions. Excited and exhausted at the same time to hear what you all think!
Nearest steps forward from here:
I should have mentioned, this does not take into account the partitioning in https://github.com/18F/openFEC-web-app/issues/1023, which I'd like to chat about to make sure I understand what some options could be.
This is amazing work, Jen, Noah, and Jeremy! Looking at picture and spreadsheet closely now.
I'll post some spreadsheet thoughts in the spreadsheet, as I make my way through.
Thanks so much for the common-sense explainer and introduction to all this, Jen <3
For the filings, we have all the reports, notices, RAFI's etc. Tell me if you think something is missing.
Independent expenditures are a type of spending and can be disclosed in different places. The forms that a committee fills out are dependent on what kind of entity they are. If you are a PAC doing independent expenditures, you are going to report that on a F3x, if you are a independent expenditure only committee, you are going to report that on the F5. There will also be 24 and 48 hour notices, which are preliminary reports of the independent expenditure spending close to an election.
Partitioning will mean for the really big tables you can query over 2 or 4 years at a time. We will make it as big of a window as possible while still being performant.
Thanks, Lindsay! I take that to mean that we do have data for Form 6, Form 8, and Form 12? Should they be included under the "All filings" list in Jen's mockup?
A couple more IE questions:
IE reports
thus include information from Form 3X, Form 5, and so on (i.e., essentially grouping information drawn from the forms already listed under All filings
)? All other spending
section be the same data as what's in the "IE reports" in "All filings" ?Looking at filings is not the best way to find IEs. We are not showing IE totals on the filings browse view at all. On the election and committee pages, there are summaries of the IE spending. For the IE browse view, it is going to be data on the transaction level.
I think 1. would be confusing because while F3X can have IEs most of them don't. If people are interested in IEs they should look at the IE transactions browse view and not the filings view.
We don't have anything on the API for seeing and filtering the different data types together so we want to make sure we really want to do with some user testing of that grouping before doing the additional work. I am not sure those kinds of spending make sense together since it might be hard to describe how they are different things.
Based on a week of great workshopping with the team, here is the latest information architecture for the data side,
For a better feel of how this navigation could play out , poke around this (still WIP) InVision interactive prototype. If you find a link that isn't linked, return to the first page, which has the most comprehensive interactions installed.
I'll follow up with a brief intro-to-this mockup, but it may benefit from 1-on-1 walkthroughs, and I'd like to demo this at tomorrow's Sprint check in, then have a review with the FEC team at a follow-up meeting.
18F team, start digging in and commenting in the prototype. I have capacity to make changes before tomorrow's meeting.
This is looking really awesome and interesting. The main question or concern I have is how exactly the "All totaled receipts" / "all totaled disbursements" pages work. Is each row in those tables a report? Or is it a committee entry? I think we do want a way for people to view the financial reports with summary data filed by committees. I see the value in breaking out of the "filing" model, but I want to make sure we're not losing anything.
Also, RFAIs under "Committees" feels just a little weird, but I'm not sure where I'd put it otherwise.
We have some ongoing comments in the filter spreadsheet about this—mostly similar open questions. I'd love to sort this one out more concretely before we go into tomorrow's meeting and demo it. - or, change it somehow. @LindsayYoung I'm going to timebox it to 30 minutes, and calendar us for tomorrow morning.
I'm going to jump into that meeting, if y'all don't mind. I promise not to sidetrack, but I definitely want to be a fly on the wall.
You're always welcome to join, @emileighoutlaw !
I think the InVision prototype looks fantastic! I have language thoughts, but I think it's a little too early for that so I'll stick to bigger/more structural notes right now. :+1:?
Search and download advanced data tables
(rather than view)This is the featurette section for novice users, right? This wouldn't be comprehensive (and tell me if it's an outrageous idea), but I think it would be most clear to readers and meet their needs if the options were:
- Candidates and their committees
- PACs*\
- Individual contributors
- Corporations and labor organizations
- Elections
***I know this wouldn't be comprehensive of all outside committees, but my understanding is that the vast majority of folks are interested in PACs and Super PACs
p.s. I've been thinking about the language on the Advanced data tables
page. Been jamming on that here, if anyone wants to take a look:
Some changes based on chatting with Lindsay this morning, and marking a spot for an area she brought up earlier that we should have tables on, Elections.
The Totaled Receipts/Disbursements didn't make much sense (I was interpreting incorrectly) so they've been removed. Added in in place of them is Financial Report Summary data for committees, which will be very similar to the FEC's existing 2016 Committee Report Summary These are marked in orange.
Thank you for kicking off the language and wording review Emileigh! I :heart: Search and download advanced data tables
, and look forward to the more detailed changes. I'll try to get in what I can into the prototype as fast as I can!
On structure, I totally see the user intention driving the change of "Outside committees" to "PACs", but wonder if we want to exclude other types, or if we want to maybe specify but not limit. Something like "PACs and other outside committees" or... "Outside committees (including PACs and SuperPACs)" in a way that allows it to help users find it within the broader category. I'm concerned that we wouldn't want to do a whole featurette section on JUST PACs, though we'd certainly want that to be one of the detail views.
Question, what was your thoughts behind dropping transactions from the featurettes @emileighoutlaw ?
I love
Outside committees (including PACs and Super PACs)
Great thought! I originally wasn't sure how much even within the featurette we want to talk about Joint Fundraising Committees and Party Committees. But there is an appetite for that? (and we think there's valuable info in there)?
I think I'm not opposed to including transactions, but I think it might need to be more specific language or more specific content (or both). From the Transactions
section of Advanced data table
we've pulled out Individual contributors
already into our list. What else do we think we want to tease out for novice users?
Alright! After lots of painstaking work, I think we have a really good outline for all of the new browse pages. Still subject to word-smithing and potentially moving pages around based on more research and testing, but this identifies the main categories for the datatable pages, as well as each page within them.
Notably, after our last session, we agreed that "e-Filings" doesn't need to be it's own category, or really even exist as a separate page. Instead, we want to explore having it as an option on all pages to toggle between raw eFilings data and "processed data".
This is a separate story, though, so I'll make a new story card for it.
Closing this.
Per the design session today, we want to explore having parent-child browse pages, which would allow us to create more specialized views and filters for more specific types of, say, filings or committees.
I'm going to work on mapping out what those pages and their respective filters and columns could be.