Releases: SEED-platform/seed
Releases · SEED-platform/seed
Release 2.6.1-patch3
Updated 2.6.1 release with 4 patches applied
-
SEED Version 2.6.1-Patch3
- Feature #2134, New column setting to allow a field's empty values to be recognized as normal, non-empty values during record merges.
-
SEED Version 2.6.1-Patch2
- Fixed #2119, Re-enable created and updated fields for master records on the front end
-
SEED Version 2.6.1-Patch1
- Fixed #2076, ESPM import no longer works due to ESPM website updates
-
SEED Version 2.6.1-Patch0
Release 2.6.1-patch2
- Fixed #2119, Re-enable created and updated fields for master records on the front end
Release 2.6.1-patch1
- Fixed #2076, ESPM import no longer works due to ESPM website updates
Release 2.6.0-patch00
This patch has address a couple issues including:
- Use previous version of base image for docker builds (both SEED and PostgreSQL). This is due to Ubuntu edge repo no long including the correct version of Postgis.
- Update the deployment to automatically read the version of redis, postgres, and OEP from the docker-compose.build.yml file
- Fix data comparisons when merging records
- Fixed #2039, Portfolio Manager Login URL Changed
- Fixed #2058, Portfolio Manager URL Changed (Flapping Issue)
- Fixed #2076, ESPM import no longer works due to ESPM website updates
Release 2.6.1-patch0
510b262
This commit was signed with the committer’s verified signature.
axelstudios
Alex Swindler
Release 2.7.0-Beta
SEED Version 2.7.0-Beta includes several significant updates that need to be thoroughly tested on production data
before being deployed. The most notable changes:
- User can define which fields to match/merge/pair/link
- Properties and Tax Lots are now linked across multiple years or compliance cycles
- Users can define mapping profiles to save/recall mappings easier
- 55 closed issues/new features
Date Range: 09/30/19 - 12/20/19
Closed Issues and Features:
- Fixed #94, Document how mapping works in the SEED-Platform / seed wiki
- Feature #417, Reports -- Save the last settings
- Improved #656, Add filename to modal reporting matches when there are no matches
- Feature #709, Allow user to disable columns in import files and handle redundant column names in import files
- Fixed #1024, Can define user account without an organization
- Fixed #1117, Filter doesn't display all the rolled up data under some circumstances
- Improved #1361, Add a bit of space on left of mapping grid
- Fixed #1375, DQ Check - Save makes labels disappear on Admin Screen
- Improved #1409, Indicate that building/property records have merged/matched records
- Fixed #1480, Five digit zip codes with leading 0
- Fixed #1511, DQ results: Program doesn't tell user that a rule can't be applied due to data definition
- Improved #1563, Need an indicator that a filter has been applied to the data
- Fixed #1571, Update verbiage in dialog box(s) to reflect merging and pairing rather than matching
- Feature #1715, Add "Only Show Populated Columns" option to Detail List Settings
- Fixed #1740, Add UBID to BuildingSync and ensure it imports into SEED
- Fixed #1817, DQ: Program "hangs" when DQ rules can't be applied
- Fixed #1818, DQ: Program shows labels across all cycles in Filter by Labels list after running DQ check
- Fixed #1845, DQ Checking hanging in mapping due (possibly) to units issue
- Fixed #1873, data quality type error
- Fixed #1945, 403 (Forbidden) when trying to geocode records from Inventory List view
- Fixed #1963, Allow user to specify which fields are to be used for geocoding
- Maintenance #1965, Re-enable sentry on systems
- Fixed #1970, Problem importing a file into a specific org
- Fixed #1977, Review and update post-import file summary
- Fixed #1979, Detail View Edit of Custom ID 1 sometimes produces an error
- Fixed #1982, Display geojson map
- Fixed #1989, Unmerging records loses pairing
- Fixed #1990, Nonexistent properties/taxlots return bad responses
- Fixed #1991, Column Settings - Sort by MATCH CRITERIA needs some tweaks
- Fixed #1996, Release specific installation constraint of PostGIS docker container
- Fixed #2005, Unable to build docker image - Could not find library geos_c
- Fixed #2010, Mapping: Instructions: Group Matching fields by table
- Fixed #2015, Importing certain column names can break all future imports
- Fixed #2031, Importing mixed types with duplicate records can cause a 500
- Fixed #2039, Portfolio Manager Login URL Changed
- Fixed #2052, Column Settings: Saving Geocoding field definitions: getting 400 and 502 errrors
- Fixed #1348, DQ Checking -- for Valid data, not errors in data
- Fixed #786, Save Changes button sequence in Data Cleansing Admin
- Fixed #1998, First edit including lat long change doesn't trigger manual geocoding logic
- Improved #1592, Prevent adding an org with existing name
- Fixed #1592, Data Mapping for imported files does not reflect the actual mapping for that data file
- Feature #1591, Detail Screen: Highlight the changes in the columns
- Feature #1232, Need easy way to view data year over year
- Fixed #1946, Meter data visible on some cycles but not all
- Feature #1759, Save mappings for specific input file data sources (ESPM, Tax Lot, Building List)
- Fixed #994, It is possible to have orphaned user accounts without an associated organization
- Fixed #2057, Tax Lot Excel export 500 error
- Fixed #1913, Add Notes info to export
- Fixed #1713, Return progress status immediately when uploading large files
Release 2.6.1
Date Range: 08/09/19 - 09/30/19
Closed Issues and Features:
- Fixed #961, Inventory Detail UI Refinements
- Fixed #1571, Update verbiage in dialog box(s) to reflect merging and pairing rather than matching
- Fixed #1844, Can't map a field called Gross Floor Area without units
- Fixed #1857, Geocoding -- Tax Lot vs Property tables
- Fixed #1883, Can't create new users (as superuser)
- Fixed #1942, On import, duplicates are not flagged when ULID/UBIDs are involved
- Fixed #1944, ULID doesn't report that it could generate Lat/Long, but then does generate them
- Fixed #1950, ULID-only mapping - Geocoding confidence text is wrong
Release 2.6.0
Add time series related functionality. Make sure to review the migrations.mst on the upgrade.
Date Range: 05/04/19 - 08/09/19
Closed Issues and Features:
- Feature #835, Expand default Portfolio Manager field mapping to include report for timeseries data
- Feature #1861, Allow renaming of columns
- Feature #1871, Allow redis passwords
- Feature #1879, profile_id as query param and part of v2.1 API
- Feature #1888, Export Measures and Scenario Data in XLSX Format
- Feature #1917, Importing ESPM Meter data for multiple buildings
- Feature #1919, Meter Feature Improvements
- Feature #1927, Make table headers sticky
- Feature #1929, Update BuildingSync to BuildingSync 2.0-pr1
- Improved #1930, Upgrade UBID Dependency to Latest
- Fixed #442, Write unit test for simple_modal_service
- Fixed #1844, Can't map a field called Gross Floor Area without units
- Fixed #1867, Allow Bldg to be parsed as part of the normalized address
- Fixed #1875, Extra data not showing up in the pairing page
- Fixed #1881, Problem importing data
- Fixed #1887, Labels can be associated to Properties/TaxLots across Orgs (via Rules)
- Fixed #1893, Labels need to be associated to PropertyViews and TaxLotViews
- Fixed #1894, Meters could be lost during Property Merge and Unmerge
- Fixed #1895, Cannot import ESPM spreadsheets that have meter data
- Fixed #1896, Cannot import Green Button Data -- 500 error clicking on Energy link in Property Detail View
- Fixed #1903, 500 Internal Server Error trying to rename columns in Column Settings if the column already exists
- Fixed #1912, Error importing Green Button meter data
- Fixed #1916, Changed units for meters in Settings doesn't appear in the Inventory Meter view
- Fixed #1918, ESPM Meter Types that SEED doesn't recognize
- Fixed #1920, Incorrect meter display settings being used on Meter Detail Page.
- Fixed #1922, nginx page on staging
- Fixed #1923, Limit log files in Docker
Release 2.5.2
Release 2.6.0-Beta (Meters and Interval Data)
2.6.0-beta includes support for meters and time series data storage. In order to use this release, you must first install timescaledb. Note that
this is a Beta release and should not be used on production datasets until we have completed
testing.