data-dwh-dbt-project/models/intermediate/resolutions/schema.yml
Oriol Roqué Paniagua 8bc525e4c2 Merged PR 5589: Limits data test coverage on resolutions data
# Description

This relates to the data alerts on resolutions models.

We have one incident status that refers to the record having missing information. The record that is currently triggering this alerts is indeed tagged as such.

The idea is to:
* Create a new boolean that flags if the incident has missing information. This is propagated stg to reporting.
* Apply a where clause to any existing data alert that might be susceptible to fail due to not having enough quality, in staging and reporting.
* Remove over coverage in intermediate since it's already happening in reporting. However we keep a few not-null tests and the PK on critical information (i.e., id_booking).

# Checklist

- [X] The edited models and dependants run properly with production data.
- [X] The edited models are sufficiently documented.
- [X] The edited models contain PK tests, and I've ran and passed them.
- [NA] I have checked for DRY opportunities with other models and docs.
- [NA] I've picked the right materialization for the affected models.

# Other

- [ ] Check if a full-refresh is required after this PR is merged.

Related work items: #31668
2025-07-01 09:44:54 +00:00

331 lines
10 KiB
YAML

version: 2
models:
- name: int_resolutions__incidents
description: |
"This table contains all incidents recorded by the resolutions team in Cosmos DB.
It includes details about the incident, the user who reported it, the associated booking,
the accommodation, the host, and the guest. Additionally, it tracks the resolution process,
including the compensation amount requested by the host, the proposed settlement calculated
by the system, and the final agreed-upon settlement amount."
columns:
- name: id_incident
data_type: text
description: "Unique identifier for the incident."
data_tests:
- not_null
- unique
- name: id_verification
data_type: text
description: "Superhog unique validation ID, coming from other APIs."
- name: current_status_name
data_type: text
description: "Current status of the incident."
data_tests:
- not_null
- name: is_incident_missing_details
data_type: boolean
description: |
Flag to indicate if the incident is currently missing details.
This is used to limit the data tests coverage.
- name: is_submission_complete
data_type: boolean
description: "Flag to indicate if the submission is complete."
- name: current_agent_name
data_type: text
description: "Name of the agent who is currently handling the incident."
- name: document_version
data_type: text
description: |
"Reported document source, such as ResCentre, API, or manual form."
- name: created_at_utc
data_type: timestamp
description: "Timestamp when the incident was created."
data_tests:
- not_null
- name: created_date_utc
data_type: date
description: "Date when the incident was created."
data_tests:
- not_null
- name: updated_at_utc
data_type: timestamp
description: "Timestamp when the incident was last updated."
- name: updated_date_utc
data_type: date
description: "Date when the incident was last updated."
- name: first_comment_at_utc
data_type: timestamp
description: "Timestamp of the first comment on the incident."
- name: last_comment_at_utc
data_type: timestamp
description: "Timestamp of the last comment on the incident."
- name: comment_count
data_type: bigint
description: "Number of comments submitted on the incident."
- name: time_to_first_comment_in_hours
data_type: numeric
description: "Time taken to reach the client for the first time."
- name: first_status_at_utc
data_type: timestamp
description: "Timestamp of the first status change on the incident."
- name: last_status_at_utc
data_type: timestamp
description: "Timestamp of the last status change on the incident."
- name: resolution_time_in_hours
data_type: numeric
description: "Time taken to resolve the incident, in hours, if completed."
- name: number_damaged_items
data_type: bigint
description: "Number of items reported as damaged in the incident."
- name: original_value_amount_in_host_currency
data_type: numeric
description: |
"Original value of the damaged items in the host currency."
- name: original_value_amount_in_gbp
data_type: numeric
description: |
"Original value of the damaged items in GBP."
- name: asked_repair_amount_in_host_currency
data_type: numeric
description: |
"Amount requested by the host for repair in the host currency."
- name: asked_repair_amount_in_gbp
data_type: numeric
description: |
"Amount requested by the host for repair in GBP."
- name: accepted_amount_in_host_currency
data_type: numeric
description: |
"Final accepted settlement amount in the host currency."
- name: accepted_amount_in_gbp
data_type: numeric
description: |
"Final accepted settlement amount in GBP."
- name: host_currency
data_type: text
description: "Host or local currency"
- name: guest_verification_status
data_type: text
description: "Guest verification status for this booking."
- name: lower_protection_limit_usd
data_type: numeric
description: "Lower protection limit in USD."
- name: upper_protection_limit_usd
data_type: numeric
description: "Upper protection limit in USD."
- name: calculated_payout_amount_in_txn_currency
data_type: numeric
description: "Calculated payout amount in local currency."
- name: calculated_payout_currency
data_type: text
description: "Currency of the calculated payout amount."
- name: calculated_payout_amount_in_gbp
data_type: numeric
description: "Calculated payout amount in GBP."
- name: submitted_payout_amount_in_txn_currency
data_type: numeric
description: "Submitted payout amount in local currency."
- name: submitted_payout_currency
data_type: text
description: "Currency of the submitted payout amount."
- name: submitted_payout_amount_in_gbp
data_type: numeric
description: "Submitted payout amount in GBP."
- name: calculated_guest_charge_amount_in_txn_currency
data_type: numeric
description: "Calculated guest charge amount in local currency."
- name: calculated_guest_charge_currency
data_type: text
description: "Currency of the calculated guest charge amount."
- name: calculated_guest_charge_amount_in_gbp
data_type: numeric
description: "Calculated guest charge amount in GBP."
- name: submitted_guest_charge_amount_in_txn_currency
data_type: numeric
description: "Submitted guest charge amount in local currency."
- name: submitted_guest_charge_currency
data_type: text
description: "Currency of the submitted guest charge amount."
- name: submitted_guest_charge_amount_in_gbp
data_type: numeric
description: "Submitted guest charge amount in GBP."
- name: id_user_host
data_type: text
description: |
"Unique Id that identifies the host."
- name: host_account_name
data_type: text
description: "Name of the host account."
- name: host_email
data_type: text
description: "Email of the host."
- name: host_last_name
data_type: text
description: "Last name of the host."
- name: host_first_name
data_type: text
description: "First name of the host."
- name: host_phone_code
data_type: text
description: "Phone code of the host."
- name: host_phone_number
data_type: text
description: "Phone number of the host."
- name: id_user_guest
data_type: text
description: "Superhog code that uniquely identifies a single guest."
- name: guest_email
data_type: text
description: "Email of the guest."
- name: guest_last_name
data_type: text
description: "Last name of the guest."
- name: guest_first_name
data_type: text
description: "First name of the guest."
- name: guest_phone_code
data_type: text
description: "Phone code of the guest."
- name: guest_phone_number
data_type: text
description: "Phone number of the guest."
- name: is_guest_deposit_retained
data_type: boolean
description: "In case a deposit has been collected from the guest,
whether it has been retained or not."
- name: is_guest_deposit_collected
data_type: boolean
description: "If the host has collected a deposit from the guest."
- name: deposit_retained_amount_in_txn_currency
data_type: numeric
description: "Amount of the deposit retained in local currency."
- name: deposit_retained_currency
data_type: text
description: "Currency of the deposit retained."
- name: has_guest_contributed_to_cost
data_type: boolean
description: "If the guest has agreed to contribute to the cost
when talking to the host"
- name: has_host_taken_preventative_steps
data_type: boolean
description: "If the host has taken any action to prevent the damage
or further damage once identified"
- name: guest_contribution_amount_in_txn_currency
data_type: numeric
description: "Amount of the guest contribution, in case they did,
in local currency."
- name: guest_contribution_currency
data_type: text
description: "Currency of the guest contribution."
- name: guest_contribution_amount_in_gbp
data_type: numeric
description: "Amount of the guest contribution, in case they did,
in GBP."
- name: is_guest_contacted_about_damage
data_type: boolean
description: "If the host has contacted the guest about the damage caused"
- name: id_accommodation
data_type: numeric
description: "Superhog code that uniquely identifies a single accommodation."
- name: accommodation_name
data_type: text
description: "Accommodation name."
- name: check_in_at_utc
data_type: timestamp without time zone
description: "Timestamp of the check-in date in UTC of the booking."
- name: check_in_date_utc
data_type: date
description: "Date of the check-in date in UTC of the booking."
- name: check_out_at_utc
data_type: timestamp without time zone
description: "Timestamp of the check-out date in UTC of the booking."
- name: check_out_date_utc
data_type: date
description: "Date of the check-out date in UTC of the booking."
- name: id_booking
data_type: numeric
description: "Superhog unique booking ID"
data_tests:
- not_null
- relationships:
to: ref('stg_core__booking')
field: id_booking
- name: booking_status
data_type: text
description: "Status of the booking."
- name: id_reservation
data_type: text
description: "External unique ID for the reservation."