Laurie
Laurie
See [Google doc with more context](https://docs.google.com/document/d/1YFz0kWXHOhd5_giHo6V0hi6CnQ6wVaDs2hfVHA9qRK8/edit#heading=h.eixyhp4llk1s). This ticket represents the outreach to Littlepay for context on the behavior we're observing.
As an analytics engineer, I want all of our columns to be documented in dbt so that future maintainers and users of the warehouse will understand what each column is...
`[Errno 2] No such file or directory` is our most common cause of validation failures. (In the midnight UTC hour on 6/29/23, occurred for 13 distinct URLs, 4 of them...
As a data user, I don't want the unmaintained `uri` field to exist on the mart `dim_gtfs_datasets` table because it is deceptive and may lead to people using an outdated...
As a Payments data user, I may want to analyze denied device transactions to better understand the entire Payments life cycle. Littlepay has produced three different files related to device...
As an analytics engineer, I want all of our columns to be documented in dbt so that future maintainers and users of the warehouse will understand what each column is...
As an analytics engineer, I want to deprecate outdated & unused tables and views in our data warehouse to reduce the risk of users accidentally using incorrect or obsolete data...
In several of our agencies' Littlepay data, either all or ~half of micropayments have a `charge_type` value of `pending_charge_fare` which is not documented in LP's data documentation. As a data...
**As far as I know, no one is using fare systems data in the warehouse at time of writing (November 2023). This ticket will only become relevant if that changes.**...
As a Cal-ITP data consumer, I would like Composer to be upgraded to ensure continuity of Airflow workflows and avoid potential failures due to using an unsupported Composer version. Context:...