cfinst / cfinst.github.io Goto Github PK

complete tables as CSV for now
maybe later filtered based on "what's visible now"

Transition from using a static database dump to a live database.

Note: This issue is directly from the Statement of Work, and may need to be broken up into smaller issues.

The numeric fields can be represented using colors that reflect which range they fall into.

For this, we'll need to:

• Detect whether or not the current field is numeric.
• If it is, then use https://github.com/d3/d3-scale/blob/master/README.md#quantize-scales to produce colors based on a computed set of ranges. We can start by using equal-intervals and see if that works well. The ranges should be "nice", so I think we can use the scales in conjunction with scale.nice and scale.ticks to generate the ranges.

Here's what I see:

Probably a relative paths issue - the favicon appears locally, but is not appearing at http://www.seemantk.com/cfi/grid/

• Fulfill the visual goals (what users should be able to see).
• Help users answer questions (such as given above).

Note: This issue is directly from the Statement of Work, and may need to be broken up into smaller issues.

Colors, fonts, layouts and finishing touches.

Note: This issue is directly from the Statement of Work, and may need to be broken up into smaller issues.

I would love to be able to send links to issues and pull requests to the CFI folks. In order for them to be able to access those links, they need to create GitHub accounts and be granted access to this repository.

This button seems to be broken now, in all sections except "Other Restrictions". Odd.. It almost seems like an issue with the code that is adding the event listener to the button.

(To address color perception for the different shades)

I'd be curious to experiment with adding a linked hover interaction. This would make it easier to correlate between the two views. I envision we could try the following:

• Hovering on a state in the map highlights the corresponding column in the grid.
• Hovering over a cell in the grid would cause its current column and corresponding state in the map to highlight.

One way to do the highlighting would be using an outline around the state and column. Something similar is implemented in this example http://curran.github.io/model/examples/d3LinkedChoropleth/

Using the data hierarchy expressed in the initial spec from CFI, we will construct a navigational interface to allow exploration of the dataset in digestible chunks.

Note: This issue is directly from the Statement of Work, and may need to be broken up into smaller issues.

In "Other Restrinctions", the colors for "Yes" and "Changed mid-cycle" seem to have gotten mixed up between the legend and the viz.

Undo commit c6ba380 "Swap textarea for Bootstrap well for .field-description"

This is to restore the thought-out behavior introduced by @seemantk and inadvertently clobbered by me.

The rationale is to have a fixed height box, so the interface is not jumping around when you switch fields. Also, the asterisk makes the "Additional notes" appear below the fold.

This seems like low hanging fruit that would be a big win.

As suggested in https://github.com/seemantk/cfi/pull/91/files/18cbad0be9f1c276e85a73538c79342a1ff80c20

The website will be deployed and released

Note: This issue is directly from the Statement of Work, and may need to be broken up into smaller issues.

Following up on the Jekyllization, since the field info is now in _data/sections in the appropriate controls.yml file, the *-fields.csv files in /data are now obsolete, as data entry should be done via the github interface.

Let's ideate on how to make the info available to data downloaders.

During the call today, both Michael and Ronda observed that the lack of color contrast between the circular grid cells compromised the overall usability of the viz. Thus, #46 addresses changing the cells to rectangular, and this one is for the color pallette

Create a new page dedicated to providing various data download links. To start, this could link to all of the raw CSV files. There should also be some way to navigate from the limits visualization page into the data download page, maybe a link that says "more download options".

Add "Party" as a donor option in contribution limits section (using Brendan's instructions per email).

@seemantk I feel like you'd have a better idea of how to go about this, as it requires modification of the handling of fields for the contribution limits section.

Add an indication of which year is being displayed on the map. This could be a simple text element on the top, or in some other location, just saying the year.

I just noticed that after sorting by a year, resizing the page causes the states to sort alphabetically. This looks to be an unintended consequence of the way the resize propagates to rendering.

I unfortunately introduced a bug in #88 where if you load the contributions tab, then change the recipient to "Party", we get some black colors. I have no idea why.

@seemantk Maybe you could find the source, I had trouble narrowing it down.

Add a statement to the project saying that:
the code is released under the GPL3 license, and
the data is released under Creative Commons Attribution 4.0 International license

Ronda confirmed with the designers that the major colors are:

• red: R:175/G:0/B:0
  • hex: #af0000
• blue: R:0 / G:24 /B:117
  • hex: #001875

Create a button that will download the currently visible data, for the current configuration of the visualization only, as CSV.

• $2,500 -> $2,501
• "$1,000 or less"
• "$10,000 or more, with a limit"
• "Unlimited", with an empty circle.

Tie breakers at infinity are the main issue.

Now there is a "Download Currently Shown Data" button that downloads CSV data for the currently selected field only. Here's a sample of the CSV output:

State,Year,IndividualToCandLimit_H_Max
"LA",1996,"5000"
"WV",1996,"2000"
"SD",1996,"500"
"NM",1996,""
"NV",1996,"2000"
"VT",1996,"2000"
"AK",1996,"2000"
"HI",1996,"2000"
"KS",1996,"1000"
"SC",1996,"3500"
"OK",1996,"5000"
"MN",1996,"600"
"AL",1996,""
"ID",1996,""
"PA",1996,""
"NE",1996,""

The information about unlimited vs. prohibited is missing.

This issue is about adding the missing information about prohibited and unlimited. The empty strings should be replaced by "No limit" or "Prohibited" (or something similar).

The viz can take advantage of more screen real estate as well

Document in the README the command that can be used to generate the CSV files from the original MDB files. This will facilitate the workflow for updating the data whenever we receive a new database dump.

Currently the "Current View" download button only works in Chrome, not firefox.

The "Download Entire Limits Data" button no longer works at all in Chrome. This may have something to do with the introduction of encodeURIComponent() in #77 . Possibly the DataURL is too long?

When clicking on a year in the Y axis, the X axis (State) values should sort according to values for that year.

Remove "Prohibited" as a choice in drop-down for contributions from individuals, PACs, parties.
Retain for contributions from Corporations and Labor.

Currently the map comes up blank on initial load. Let's try having it show the most recent year by default on initial load.

• Download the raw dataset for any chosen view.
• Download the full dataset.

Note: This issue is directly from the Statement of Work, and may need to be broken up into smaller issues.

Pending input from CFI.

Currently the years axis on the right appears far away from the grid.

I suggest we move it to be flush against the right side of the grid, to match with the left side.

Now that the legends are no longer data-driven (instead are driven purely from the configuration), we need to go through each field of each section and make sure the legend items present match up with the values that are present in the data.

As one instance, in Public Financing, there are values "Mixed" and "none", which are not accounted for in the legend. This may be part of the issue with the mismatched colors - new data values are causing the colors in the legend to loop around. One thing we could do to help fix this is pad the color range with random colors, just so we will easily know when this is happening.

Maybe the best solution here would be to use the configurations as a starting point for the legends, then fill in the legends with more colors automatically if more values are discovered in the data.

where they should say "Unlimited".

This issue is about implementing an interface idea we discussed recently, where there would be a user interface element below the map for selecting the year. This would obviate the need for the year label on top of the map.

Possible solutions we discussed included

• Drop-down menu
• Group of buttons, one for each year
  
• Slider with tick marks and tick labels

Hey @seemantk , I just noticed that http://www.seemantk.com/downloads.html has temporary content there. Just wanted to make sure we keep track of this.