Skip to content
This repository has been archived by the owner on Dec 23, 2017. It is now read-only.

Feature/data explinations #746

Merged
merged 8 commits into from
Sep 25, 2015
Merged

Feature/data explinations #746

merged 8 commits into from
Sep 25, 2015

Conversation

LindsayYoung
Copy link
Contributor

  • Add date disclaimer for schedule A and B
  • Add link to page of the record for Schedule A and B
  • Standardize some capitalization: @emileighoutlaw asked for sentences case
  • We had "date" as a heading in cases were there were 2 kinds of dates so I added "disbursement date" or "receipt date"
  • Changed receipt date to filing date in the schedule A and B panel descriptions, because recipt date is confusing on the recipes page.
  • I moved description and memo text next to each other because the memo filed can sometimes flesh out the description.

fix #736
fix #726

Added a filing section that links to the page of the record.
 - made recipt_date into filing date because it was confusing on the receipts tab
 - standardized some capitalization
@emileighoutlaw
Copy link
Contributor

Content looks good from my end.

@LindsayYoung
Copy link
Contributor Author

@noahmanger this adds some fine print in the filters. I also specified what date we are looking at in the tables when there are more than one date and for committees, I changed "file date" to "first file date" because I thought it was kind of confusing without the first. I wanted to flag this to your attention because those changes that makes some headings a little longer, and I know space is at a premium.

<table>
<tr>
<td class="panel__term">Filing date</td>
<td>{{{ datetime receipt_date }}}</td>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be filing_date ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They use "receipt date" for the day the filing was received by the FEC. But that becomes confusing on the Receipts page, where there is "receipt date" and "contribution receipt date" I thought if we called "receipt date" "filing date" that makes the two dates more clear. I changed it on the disbursements since those tables are similar and if there is a section called receipts, receipt date might be confusing. If you have a better idea of how to make it less confusing we can change it.

</tr>
<tr>
<td class="panel__term">View report page</td>
<td><a href="{{{ pdf_url }}}" target="_blank">View on fec.gov</a></td>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This duplicates the "view original image" link at the top of the panel.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, I am blind. Thanks for spotting that!

A thought on the language, what if it says-- "View report page" instead of "View original image" Does @emileighoutlaw or @noahmanger have strong feelings on this micro copy?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about "View original report" ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are showing the page that the record is on, which is handy because the reports can be thousands of pages.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like "View report page", but then in the filings panels we'd need it to be "View report". Right now we use "View original image" for both.

I was looking at this and think it might make sense for the link under filing date to link to the full report, just so people can have it. I think we should also identify the report it was filed on by name, so you can see, e.g. April Quarterly 2015.

@noahmanger
Copy link
Contributor

I can style the disclaimers in a separate PR after we merge this.

@jmcarp
Copy link
Contributor

jmcarp commented Sep 25, 2015

What do we need to do to get this ready for merge @LindsayYoung @noahmanger? I'd like to get rid of the duplicate pdf links, and it sounds like we may want to change some text, but hopefully we can resolve other issues in separate patches.

@LindsayYoung
Copy link
Contributor Author

Merging and doing additional, small changes sounds good to me.

@jmcarp jmcarp merged commit e536663 into develop Sep 25, 2015
@jmcarp jmcarp deleted the feature/data-explinations branch October 2, 2015 16:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
4 participants