-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
include information about the data, links to additional data sets and API within the campaign finance data section #833
Comments
actually i'm already seeing that i missed some of the data sets! I'll see if they break the pattern on Monday. |
Updates on this, from this morning's pairing with @jenniferthibault, @emileighoutlaw and @nickykrause :
will upload an image when s3 comes back on line! |
Turns our there were more 🐇 s left in the 🎩 and @noahmanger helped me find them in a great quick review! Check them out in this 🖌 InVision and click around, just about everything is linked to where the sitemap says it should go. Summary of changes
Just about everything here will need @emileighoutlaw for content and someone for data subject matter expertise, especially:
Next steps
|
Had a really productive review session with @PaulClark2 on Friday that led to a few more changes to the Advanced Data section. The 🖌 InVision prototype has been updated with those changes. Changes:
Remaining to-do's
@nickykrause / @onezerojeremy this should be in good shape for testing this week! |
@jenniferthibault I'm usually never one to say no to an interpretive dance, but I looked through the prototype on my own. Looks great! I really like what we've got going here. It's very easy to find what's there and understand what you're looking at. We have a lot of data and I think it's often very hard to get oriented, or even know what questions to ask about the information you want to search. This is a great solution for that. I am also a huge fan of the terms of use at the bottom of each page, given what comes above it. It looks like there are going to be a lot of little language issues to iron out. Will you let me know when it's time to focus on that? |
Oh that's great, @AmyKort! You are fast ⚡️ and I'll save the interpretive movement for our next workshop. You're absolutely right there's a lot of small copy areas we're going to need your help + @emileighoutlaw 's for nailing down. Emileigh, how would you like to break that work down? |
We do not need to find a home for http://www.fec.gov/finance/disclosure/PostCycleSummaryDataFiles.shtml on the new website. |
Thanks! Mockups updated. |
@jenniferthibault we can also remove the links to House independent expenditure map and to Senate independent expenditure map |
Great! That helps cut down on some clutter under that item too. Updated! |
Tracking the implementation of this over in fecgov/openFEC-web-app#1877 |
The sitemap/IA has us adding a few new data sources and information about them to the campaign finance data section.

We also are looking for a way to re-incorporate the API back into the site architecture.
Here's a first take at those.
So the about the data page has good explanatory content about where to find certain aspects of the data, and importantly, the terms-of-use-esque language forbidding the use of this data for commercial ends. I think both of these bits of data feel like they belong as part of the data footer, as it provides a way to surface the warning anywhere someone might wonder about how it can be used, which is to say, while browsing the data sections in places where the underlying data is exposed (on the candidate and committee pages, on the data tables, on the advanced data landing page). Here are two looks at that:
1.1: data footer where about the data and api are added to footer menu, terms of use are directly exposed
1.2: data footer where about the data and api are added to footer menu, terms of use are included via a sentence which links directly to the sale and use section of the about the data page.

To me, this feels like another section of Advanced data. Still not sure how we want to call out the difference in the links to the legacy content, but leaving that alone for now, each of the links to the data download and other sources are included as links in a new section very tentatively titled "Bulk data downloads and other sources". This is also felt like another place to call out the API, which can be viewed as another data source.
2.2 Here's basically the same layout, but instead of adding the API to the other sources, it shows up as a "more ways to explore the data" card.

for more on the nav, see 827
Obviously all this is very drafty, but should give us something to talk about on Monday! :)
The text was updated successfully, but these errors were encountered: