Skip to content
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

As a researcher/journalist, I want to quickly and easily identify the most recent filings near a filing deadline so that I can feel confident that I'm seeing all there is to see #1741

Closed
2 tasks
Tracked by #137
jenniferthibault opened this issue Feb 2, 2018 · 5 comments
Milestone

Comments

@jenniferthibault
Copy link
Contributor

jenniferthibault commented Feb 2, 2018

Users looking at election summary pages might not notice that recent eFiling data does not show in processed data. As a first step, we're going to improve the language introducing our Processed and Raw data toggle.

  • Develop new language for Processed
  • Develop new language for Raw

This is a placeholder issue for longer-term design improvements to issues identified in https://github.com/18F/fec-cms/issues/1735#issuecomment-362743038

@AmyKort
Copy link

AmyKort commented Feb 9, 2018

cc @llienfec

@AmyKort AmyKort added this to the Sprint 5.1 milestone Feb 9, 2018
@llienfec
Copy link
Contributor

llienfec commented Feb 9, 2018

We are working to improve the descriptive language for the processed and raw data tabs. The main goal is to help users understand the differences and trade-offs when looking at/using the two data types.

Current drafts:

Processed

Processed data has been categorized by the FEC. It may not include the most recently submitted electronic filings. Raw data may show more recent filings.

Raw

Raw data comes from electronic filings as they are received by the FEC. It does not include paper filings and the data has not been categorized by the FEC. Processed data shows data that has been categorized.

@AmyKort
Copy link

AmyKort commented Feb 12, 2018

I'm happy with both of these. What do you think, @PaulClark2 and @jwchumley ?

@PaulClark2
Copy link
Contributor

The proposed language works for me.

@AmyKort
Copy link

AmyKort commented Feb 14, 2018

We've agreed on this language, so I'm closing this ticket. I'll come back and update it with the implementation ticket when I have it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants