-
Notifications
You must be signed in to change notification settings - Fork 43
Design review
User journey #347
Streamlines the user experience by reducing step from viewing to editing. On load all categories are collapsed. On opening category the fields which have map colours/styles attached are visible. Clicking on those changes map style and prompts user to click building to edit.
Remove 'view map' stage and load straight on 'view data' page. Make editing/saved feel more like a within-form change - active/disabled fields
On initial load a building is preselected (UCL Senate house?). This displays the current edit page (graphics to be refined). Never without a selected building.
Colour all/any #367
For selected fields entered on the website a colour map is provided which updates when you enter/change data. Where we don't colour all we send an acknowledgment to thank user and let them know data was captured.
Similar UI/UX to current like me and location, for each piece of data added the colour tint updates after you hit save. Some maps use tint some use different colours.
Questions;
- How and when to change what is shown, on save display updated map.
- Colours for fields
- Impact on scalability and performance
- Choose colours
- Associate map style with every field
- limiting map zoom in edit to min zoom ~15
Pick from drop down / autocomplete #365
Prevents issues with free text and malicious entry, links to moderation mechanism and linked fields mechanism. Broadly as existing drop downs but with autocomplete when more than x input options/
In streetname you can only pick from names in OS open names list, maybe with add new that is then sent for moderation. Works on land use cat i.e. Type in Industrial get prompted for Industrial - Factory?
List of possible entries stored in db, then made accessible to UI. For postcodes this could alternately be a REGEX, for numbers a limit on input type
Collate lists of names, integrate with moderation mechanism (post oct?)
Declarative flow #368
If you enter one field, related fields are enabled and become visible and act as prompt to complete the category.
Planning category; Only show 3 main fields for category, if you enter one of these others appear based on that selection.
- Click on field
- Map style changes as colour any/all
- On save map updates, colour changes
- Next field becomes extra fields become visible
- User can tab to next changing map style to field style, is removing colour completely or just changing tint. Categorical categories (age and community) more complex than location / like me example.
https://github.com/tomalrussell/colouring-london/issues/300
Feature tour / overlay introduction #336
On first sign in overlay feature tour, many open packages for this. Also offer video/GIF guide as some people prefer that and easy to share on social media etc.
Required to know first visit or dismissed
I enter data into a field and hit return or tab to next, data is saved map is restyled. Can tile server be set so that the once building edit is clicked the tile is sent to render for all possible updates? Don't understand who tile rendering works.
Shows edit history, see last edit item for details.
Show last edit for selected fields (Polly query on how a viewer sees last n edits)
When viewing the building data you also see the date of last edit (day/month/year?) and who made the edit. Is there a risk of disclosing personal data here, ie does the edit get logged as the team or individual (individual makes sense)
Database last edit log for field is called and displayed by the field.
Works with declarative mechanism to complete related field when field entry is given.
Age category. Enter year and decade and century are then populated, for autogenerated fields entry is locked and can only be overwritten by changing the generating field. Land use category, some provides the class field and the grouping and order get completed.
For age some simple client side javascript.
A tick box applied to designated fields to allow users to verify the data and or data source. Works in combination with soft verification. If more than 5 verifications, overwrite of field triggers moderation process, unless building is demolished.
Building date is 1850, user sees the date and also original user is 18th_century_team user
confirms the 1850 date and verifies.
Tick box next to field(s). Monitor for user engagement over first 6 months, this is very useful for those looking at the data out if it's used.
Database fields, would need extra field for every applicable field.
Allows source to be added for designated field. Harness declarative function by prompting (requiring?) the source to be added. This works in combination with related edit. Design option for each field, after entering data prompt for source on required fields. After entry source is hidden by default but can be viewed.
I enter the date, I'm then prompted/required to pick my source from the drop down, if url then I'm asked to input this. If entering different date to one already shown previous source is archived, ie you can't attach new date without updating source.
As above, front end work to make function. Db to set up fields for categories.
Setup declarative system.
Gives prompt that if you've filled in one field you'll maybe know the other ie roof form / roof material.
Collects demolition history and use history, json b list. Which logs this. Refer to Github issue #266
Db columns for history fields
For the few free text options we have (mainly design team and building name). We need moderation mechanism so that when text entered it is passed for moderation before being visible, once moderated it is accepted and locked. This links to drop down and auto complete, if a new source is added and accepted that should then be available as autocomplete/drop down in available fields.
Sets restriction on what can be entered into related field. Needs careful think through to prevent unexpected restrictions, review what fields this would apply to.
Roof type and roof material, if flat roof can only be certain material type.
None needed?
Displays map filtered by a specific field in the database
Show me every victorian building or mosque
Elastic search box, see superset table example. Enter multiple items, these get passed to db as sql search (danger of injection attack, use autocomplete to validate and reject text?)
Big item
Takes category/selected fields and then applies them to multiple footprints.
See Github #282 and #283