search

SEED-platform / seed

Standard Energy Efficiency Data (SEED) Platform™ is a web-based application that helps organizations easily manage data on the energy performance of large groups of buildings.
Other
107 stars 55 forks source link

Tax Lot histories are generated when Tax Lot field paired with Property, even though the records are duplicates and should be ignored #2029

Closed RDmitchell closed 2 years ago

RDmitchell commented 4 years ago

Expected Behavior

When an ESPM file where all fields are mapped to Property except for Jurisdiction Tax Lot, which is mapped to Tax Lot, the program should not generate a new column for each ESPM file that is imported where nothing changes about the Jurisdiction Tax Lot ID.

Actual Behavior

The program is generating a history column in the Tax Lot Detail view every time an ESPM file is imported and has a field (Jurisdiction Tax Lot ID) mapped to Tax lot, even though nothing changes about the Jurisdiction Tax Lot value

Steps to Reproduce

Here is a link to the folder for this issue, which contains the example files imported in the testing, as well as two documents explaining the steps. https://drive.google.com/drive/folders/1ww5oOMtohoXsmbQPtDAsW3ULY0t7zNBA?usp=sharing

The two docs are:

Instance Information

Instance: dev1 SHA: 6dad9f771

RDmitchell commented 4 years ago

Instance: dev1 SHA: 6dad9f7

When I just import the sample Tax Lot file twice (with 2 different names) and no changes and no cross-mappings to the Property table, the program properly ignores all the records because it considers them duplicates, and the 2nd file does not appear in the Tax Lot Detail view for any of the records (because they were all ignored).

So I think it has to do with the case when fields are cross mapped between the Property and Tax Lot tables. It might have to do with the Geocoding Confidence, but it might be something completely different.

And I believe this same behavior exists in the production version we are running, which is

2.6.0.a655675d

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 2 years ago

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.