Closed RDmitchell closed 7 years ago
I think that this will disappear once we have unique names. If we enforce uniqueness, then we could remove the need for this "duplicates" section in the table.
For now, it seems that no duplicates are being generated in mapping. However, if there ever are, this will still be an issue. Am closing with the idea that if it comes up for a specific case, we'll open up another issu.e
Just imported Kansas City building list and see duplicates. This is on the pm import branch from Nick. Maybe it doesn't have these fixes in it? Am going to reopen this just to make sure it gets retested when all the code is merged.
SHA: 1d26e16 instance: seeddev org: LBNL 202 browser: chrome, incognito
When the program finds a duplicate field, it puts them at the top of the Mapping screen.
In V2.0, we need to allow the user to resolve the duplicates by changing the field names, and then also have a way for the user to assign those fields (presumably after resolving the duplicates?) to the appropriate table, either Tax Lot or Property.
Right now, you can't do that (code as of 10/10/2016)