Release 1.2.2
Reporting and Graphs
- PR #400: This is the first implementation of the reporting page, which shows two configurable graphs in the Building section, under the new "Reports" tab. Three new methods were created on the backend (in views.py) to provide data to the charts on the client. Gathering the required data from the seed_buildingsnapshot table is somewhat involved as the charts need historical dat. We therefore can't rely just on the data captured in the last good canonical building, but instead must traverse the parents of the canonical building to gather historical data. (Issue #178)
- PR #404: Even though the query initially run specifies a date range that is abandoned to walk the tree of a canonical building's parents. Since this is using the tree there may be some other records with no year_ending date. Added a check to ignore them from processing. This fixed some issues with graphs not being generated. (Issue #402)
- PR #413: Added check to force any buildings with a gross_floor_area > 1 million to be put in the 'over 1,000k' bin. (Issue #410)
- PR #415: Previously only got data from unmerged building snapshot records. Changed that to use only data from merged records (the current canonical building and previous canonical buildings). This ensures that the data being graphed represented the merged information from all relevant data sets (such as buildings lists and Portfolio Manager data merged into one building record / building snapshot record)
- PR #416: Changed the reporting code to filter out canonical buildings where the 'active' property is set to false. This ensures that "deleted" buildings are not included in the data that is graphed. (Issues #406 & #412)
- PR #403: Replaces static URL. Instead, now injecting urls object and
using urls.static_url property to build URL.
Data Importing
Building List -- Filtering
Building List -- Control over field sort order and column width
- PR #399: Fixing sort order problem for status column
- PR #374: Fix resize columns (Issue #71)
- PR #356: Adding directive to resize table columns, feature to sort table columns (Issue #71)
Data Cleansing
- PR #398: Enabled cleansing date range checking (Issue #384). Also fixes CI.
- PR #376: Data cleansing dialog
- PR #353: Update celery to 3.1. enable celery results
Matching -- General
- PR #394: When unmerging buildings, it was possible for the building to get left in an error state. In the case where the building which is being removed from a set of other builds happens to be the one that has the active canonical building (within the tree of building snapshots), then when that building snapshot is unmerged from the tree, it's canonical building will end up with no canonical snapshot. When this happens, it stops being returned in queries for buildings, and thus disappears from the front end. (Issue #386)
- PR #391: Modified matching dialog message. (Issue #340)
- PR #352: Matching detail screen show extra_data column content (Issue #345)
Matching -- Address Normalization
- PR #389: Account for null values in the normalized connonical building address
- PR #362: Address direction normalize (Issue #315)
- PR #380: Normalize street type (Issue #378)
Admin / Account Management Features
- PR #372: Change width for admin remove buildings (Issue #372)
- PR #377: Added new SEED_ACCOUNT_CREATION_BCC setting and updated account invitation task to use it.
- PR #368: Admin building and user count (Issue #324)
Portfolio Manager Web Services Connection
Misc
- PR #379: Fixes pytest.ini to point to the correct DJANGO_SETTINGS_MODULE
- PR #361: Remove WOOPRA config (Issue #90)
- PR #351: Centralized caching - removes the vast majority of direct cache.set/cache.get calls, and centralized them in a new cache utility that standardizes format, functionality, and let's us easily debug any time the cache is modified.