Design changes

This document describes the design changes we need for scout

Multi city scout

We are currently in the process of updating scout to be able to serve multiple cities. Most of the infrastructure code to support this has been written but we need some design work to make the new features obvious and easy to use

The following needs to be designed

1. A page to view the list of available cities / portals and allowing the user to select the one they want to focus on. The number of these portals will start out small but could increase to over 100

2. An indicator on each dataset sheet and page that shows which portal the dataset comes from.

3. Reworking the collections page to incorporate datasets from multiple cities.

Consolidated column names

We are starting to look at ways of trying to consolidate column names in such a way that for example "school id" "school_id" "School" "SchoolID" are all consolidated under a single label "school_id". These new labels will be used in the home page filters and in the identification of join columns.

It would be good however to find a way in the design to indicate the consolidated column and the original column name. This is necessary because the column name in the dataset will still be the non-consolidated one.

Design challenges here :

1. Indicating that column names are being grouped together because we believe they are the same type of ID.
2. Making a visual distinction between consolidated column names and final column names.