PLUTO QA Page: recs from GIS

While jointly doing QA of PLUTO with GIS team, we recorded a list of various QA page improvements. Listing them here. These improvements/QA checks can later have their own child GH issues.

• Source Data table: add column to indicate version type (does the version reflect when the data was pulled, ingested by DE, or Socrata/Bytes version?)

• All visuals: across all data product pages, make sure the colors are consistent. Also, switch colors for yellow to represent current version.

• All visuals: add a value thingy when hovering over a data point. Otherwise, when the difference for a given field between 2 lines is vast, one of the lines appears to be zero.

• Building area graph: Add columns for absolute change.

• All outlier tables: normalize numbers (no decimals with 8 places); add a button to export tables to csv/excel.

• Unreasonably small apartments table: some indicate that NYCHA filter worked. Maybe update total # of records above the table.

• Vanished/new bbls table: make bbl a string type.

• Logging of streamlit changes: i.e. "changed a header for table X on this date" or "add a new table on that date".

Start by reviewing the unchecked items for the Source Data table, all visuals, the vanished/new BBLs table, and Streamlit change logging. Split the list into child issues, identify the relevant QA page entry points, and define completion checks for each requested improvement before making changes.