32 lines
No EOL
2.1 KiB
Markdown
32 lines
No EOL
2.1 KiB
Markdown
# Data Issue with Resolutions Center Manual Forms
|
|
|
|
### Context
|
|
|
|
We currently extract data from the **Resolutions Center**, stored in **Cosmos DB**, and use it to build models and tables in the **DWH**. These are then consumed by some reports, including the **Resolution Incidents** report.
|
|
|
|
Historically, based on initial conversations with the Resolutions team (especially Manu), we established that certain fields, particularly **Guest**, **Host**, and **Booking** data, were **mandatory** for all resolution records. Our models and data tests were built with this assumption, and we have strict tests to flag missing values for these fields.
|
|
|
|
### Current Issue
|
|
|
|
Recently, we have been receiving alerts from our data tests, flagging missing mandatory fields. Upon further investigation, Ant informed us that some **manual forms** created within the Resolutions Center (used for external partners like **Guesty** and **Holidu**) may not contain complete Guest, Host, or Booking information.
|
|
|
|
This is a change from our initial understanding and introduces exceptions to the previously enforced rules.
|
|
|
|
### Implications
|
|
|
|
1. **Data Tests**
|
|
- Our current tests assume these fields must always be present.
|
|
- We will need to update them to **exclude manual forms** from this requirement (e.g., using a flag or identifying logic for manual entries).
|
|
2. **Model Logic**
|
|
- We need to verify if downstream models depend on the presence of these fields.
|
|
- Any logic assuming complete Guest/Host/Booking data should be reviewed for potential failure or bias.
|
|
3. **Resolution Incident Report**
|
|
- Check if the **Resolution Incidents report** is affected by these manual forms.
|
|
- If so, we may need to add filters, fallback logic, or a dedicated section for manual forms.
|
|
|
|
### Next Steps
|
|
|
|
- [ ] Update data tests to handle manual forms differently.
|
|
- [ ] Review downstream model dependencies and document any required changes.
|
|
- [ ] Assess the impact on the Resolution Incident report and plan necessary adjustments.
|
|
- [ ] Align with Resolutions team to confirm any other exceptions or changes in data expectations. |