You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we surface information about how a building is related to the "seed address" of a portfolio via a barely-noticeable link/button on the building info page called "How is this building associated to this portfolio?":
It might be helpful to users to also have a column called "How is it related to ?" in the portfolio tab that explains, briefly, how the building in a given row is related to the seed address. For instance, it could have values like "Same business address", "Same business entity", "Same head officer: JOE SMITH", and so on. Even better would be to make this column sortable, though that could get complicated when we consider that there are multiple ways an address could be related.
Aside from being potentially useful, this could be another way in which, through the information we surface, we implicitly give users a better understanding of how these portfolios are being inferred.
The text was updated successfully, but these errors were encountered:
Currently we surface information about how a building is related to the "seed address" of a portfolio via a barely-noticeable link/button on the building info page called "How is this building associated to this portfolio?":
It might be helpful to users to also have a column called "How is it related to ?" in the portfolio tab that explains, briefly, how the building in a given row is related to the seed address. For instance, it could have values like "Same business address", "Same business entity", "Same head officer: JOE SMITH", and so on. Even better would be to make this column sortable, though that could get complicated when we consider that there are multiple ways an address could be related.
Aside from being potentially useful, this could be another way in which, through the information we surface, we implicitly give users a better understanding of how these portfolios are being inferred.
The text was updated successfully, but these errors were encountered: