bcgov / bcgov/STRR

UI - Improve Manual Address Entry Experience & Guidance for Strata Hotels and Platforms

Open
#1,258 0 comments 0 reactions 1 assignee Claimed by @J-Baese View on GitHub
STR
Dominant language
Python
Stars
2
Forks
22
Avg merge
2d 35m
Merged PRs (30d)
11

Description

### **Background / Problem Statement - Copy from Hosts Background bcgov/entity#29784**

Users are consistently entering incorrect address information in their applications. A review of the STR Registry database and user feedback identified recurring issues such as:

**Street Number entered in the Unit Number field**
- **Example:** Unit Number: 8209 | Street Number: Binnie | Street Name: Road
- **Expected:** Unit Number: {empty} | Street Number: 8209 | Street Name: Binnie Road

**Street Name entered in the Street Number field**
- Example: Unit Number: 1195 | Street Number: 18th | Street Name: Ave

**Mailing Address used instead of Physical Address**

**Entering both a Site Name and Street Address**
- Only one type should be entered, either Site Name or Street Address, never both.

### **Scope**
This update applies to two flows: Strata Hotels and Platforms.

______________________

### **User Stories**
**Address Formatting & Guidance**

Note "Applicant" refers to Strata Hotels and Platforms

- _As an Applicant,_ I want to see guidance text (when first completing my application) showing examples of urban, rural, and non–Canada Post addresses and how to enter them correctly, so I can ensure my submission is accurate.

- _As an Applicant,_ I want to see similar guidance when reviewing my property address, so I can confirm the property info is correct and matches STR Registry requirements.

**STR Registry as Source of Truth**
- _As an Applicant,_ I want to be informed that the STR Registry address is the official record for my property registration, so my platform hosting activities are not disrupted.

**Platform Address Match & User Responsibility**
- _As an Applicant,_ I want to be informed that platform address information must exactly match the STR Registry address.

- _As an Applicant,_ I want guidance that if a platform’s address is incorrect, I must contact the platform directly to request an update.

> _*Needs its own Ticket_ **Platform Validation Notification**
_As an Applicant,_ I want a notification in the “To Do” section of my dashboard when platform validation fails, so I can take corrective action quickly.

____________________

### **User Experience References**
> 📄 [Validation Matrix: Manual Address Fields](https://docs.google.com/spreadsheets/d/11KDcUt_g1rBYYnBVmO15GwXM62zu1OYLc5VpCOBtv-U/edit?usp=sharing)

> 🎨 [Figma Design File](https://www.figma.com/design/a4H3s0ebAxwv8ZniyNAt4g/STRR-Host-Registration---Redesign?node-id=6822-308638)

____________________

### **Acceptance Criteria**
📌 **Address Formatting Guidance**
Given the user is completing their application or reviewing their address;
Then they must be shown examples and clear instructions for entering urban, rural, and non–Canada Post addresses correctly.

📌 **STR Registry as Source of Truth**
Given the user is reviewing or entering their address;
Then display guidance that the STR Registry is the authoritative source for address records and overrides any platform-stored values.

📌 **Platform Address Requirements**
Given the user clicks the "Guidance" button next to the address field;
Then show a pop-up explaining the address on platforms must match the STR Registry exactly.

📌 **Contact Platform Guidance**
Given the user views address guidance;
Then they are informed that address issues on platforms must be corrected by contacting the platform directly.

> _Add to new ticket: 📌 **Notification on Platform Validation Failure**
Given a platform validation fails after submission;
Then display a “To Do” item on the user’s dashboard indicating the failure and prompt corrective action._

________________________

### **Manual Address Component Updates**

- [ ] Remove extra text in manual address component _(See Designs)_
- [ ] Add Alert bar into manual address component
- [ ] Remove 'Country' field
- [ ] Move 'Unit Number' below Street Number/Name
- [ ] Update input fields with **floating labels** (Nuxt 3.1.3)
- [ ] Add Hint text to fields
- [ ] Implement field logic from the **Validation Matrix**
- [ ] Make **Site Name and Street Number/Name** fields mutually exclusive – only one may be completed at a time.
- [ ] Add a **Help button** with:
- Definitions for Unit Number, Street Number, Street Name, Site Name
- Examples of valid address types
- Clarification on not using mailing addresses

___________________

**Analysis and recommendations for address entry issues (Scott)**
https://1drv.ms/p/c/e52b0821ec98a357/EYkgyfddxZ5AqXXEH7kSAeYBZl2SGO7Q_nj-AbnlA8fFow?e=8BFXkP

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.