Design for new data summary language

[kathycarothers]

User Story

The regulated community needs to understand that the data summaries take time to update. In some cases they are not updated right away.

Background

In #2924 we worked out the language to post on the website to alert the regulated community that the data takes time to update.

Completion Criteria

• Identify and mock-up where to place language on the website. Here is one idea from @AmyKort
  

• Create a front-end ticket to make the change to the hard-coding to implement this wording:

Newly filed summary data may not appear for up to 48 hours.

[dorothyyeager]

Include front-end deadline of 7/14 in the follow-up ticket.

[JonellaCulmer]

@kathycarothers @PaulClark2 To start, I want to make sure we have an inventory of all the places this language is needed. Is below correct?

• Data tables
• Visualizations
• Candidate profile pages
• Committee profile pages

[kathycarothers]

@JonellaCulmer @PaulClark2 That would be correct

[PaulClark2]

@JonellaCulmer you're list looks correct to me.

[JonellaCulmer]

@kathycarothers @PaulClark2 @AmyKort Below is a list of all the places I believe we need to include this new language. Please let me know if any of these places are incorrect or if I'm missing a page.

Data tables: Presidential candidates, Senate candidates, House of Representatives candidates

Visualizations: Cumulative amount raised by committees, Cumulative amount spent by committees, Office/party totals raised and Top raising bar chart, Office/party totals spent and Top spending bar chart

Candidate profile pages: Financial summary tab, Raising tab, Spending tab, Spending by others to support or oppose

Committee profile pages: Financial summary tab, Raising tab, Spending tab

[JonellaCulmer]

@kathycarothers @PaulClark2 @AmyKort Draft mock-ups are below. I considered something a little more involved with messages, but think that even though this information may not apply all the time, this implementation seems simpler. Some of this placement seems a bit heavy. I'm trying to balance the need for this language to be prominent with all the places that require it. If you feel we can scale back anywhere, I would appreciate your thoughts.

Datatables

New language placed in a message on the bottom of the filter panel

Cumulative amount raised and spent line charts

New language placed at the bottom of the charts.

Office/party totals (raised and spent) and Top spending candidates (raised and spent)

New language added at the bottom of both charts on both the raising and spending chart pages.

Candidate and committee profile page - financial summary

New language introduced at the bottom of each table.

Candidate and committee page - raising tab

New language added at the bottom of the Total receipts table

Candidate and committee page - spending tab

New language added at the bottom of the total disbursements table

Candidate profile page - spending by others to support or oppose

New langauge added at the bottom of the IE table. This section was trickier since it combines the summary figures with individual transactions. Let me know if folks feel that this is a confusing placement.

[kathycarothers]

@JonellaCulmer I like what you did with the placement of the language. I do agree with you on the last chart you provided for the IE table. The language at the bottom could be confusing, or people can get lost in the language. I don't think those two sentences should be combined. Maybe put it on a separate line or move it to the top?!?! I am not sure. hmmmmm
@AmyKort @PaulClark2

[PaulClark2]

@JonellaCulmer I'm not sure. I makes sense to me but I know what we are trying to say. I wonder if @kathycarothers' suggestion would help. It would certainly make it clearer to users that the two notes below the table are independent.

[JonellaCulmer]

Thanks @kathycarothers and @PaulClark2. Please see the updated mockup below to move the language up by the totals figures. It makes sense up here and is similar to the placement in other instances.

[kathycarothers]

@JonellaCulmer @PaulClark2 I think that will work. I like the change.

[PaulClark2]

@JonellaCulmer I agree with @kathycarothers . I like the change.

[JonellaCulmer]

Closing in favor of implementation issue #3040