data

.gitattributes

@@ -35,9 +35,6 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 *.zip filter=lfs diff=lfs merge=lfs -text
 *.zst filter=lfs diff=lfs merge=lfs -text
 *tfevents* filter=lfs diff=lfs merge=lfs -text
-gt_v5/**/*.csv filter=lfs diff=lfs merge=lfs -text
-gt_v5_databricks/**/*.csv filter=lfs diff=lfs merge=lfs -text
-gt_redshift_v5/**/*.csv filter=lfs diff=lfs merge=lfs -text
 # Audio files - uncompressed
 *.pcm filter=lfs diff=lfs merge=lfs -text
 *.sam filter=lfs diff=lfs merge=lfs -text

README.md

@@ -1,32 +1,3 @@
----
-license: cc-by-sa-4.0
----
-
-# ELT-Bench Inputs
-
-This dataset contains the 100 ELT-Bench task inputs for three data
-warehouses:
-
-| Data warehouse | Directory |
-| --- | --- |
-| Snowflake | `inputs/` |
-| Databricks | `inputs_databricks/` |
-| Redshift | `inputs_redshift/` |
-
-Every directory is self-contained. Each task includes its
-destination-specific `config.yaml` and `data_model.yaml`, together with a
-copy of the shared table schemas under `schemas/`.
-
-## Ground Truth
-
-The v5 ground-truth output tables are provided separately for each data
-warehouse:
-
-| Data warehouse | Ground-truth directory |
-| --- | --- |
-| Snowflake | `gt_v5/` |
-| Databricks | `gt_v5_databricks/` |
-| Redshift | `gt_redshift_v5/` |
-
-Each directory contains 202 evaluation CSV files organized as
-`<database>/<output_table>.csv`.
+---
+license: cc-by-sa-4.0
+---

{inputs_databricks/address → address}/data_model.yaml

@@ -7,12 +7,12 @@ models:
       - name: name
         description: the name of the state
       - name: county_with_highest_average_income_per_household
-        description: the county with the highest average income per household in the state, with ties broken by the ascending order of the county
+        description: the county with the highest average income per household in the state, with ties broken by the ascending order of the country
       - name: num_asian
         description: the number of Asian in the state, replace NULL values with 0.
       - name: num_counties
         description: the number of counties in the state, replace NULL values with 0.
       - name: higher_avg_female_per
         description: Set to 1 if the state’s percentage of female population is higher than the average percentage of female population across all states, otherwise, set to 0
-      - name: greater_than_15_CBSA_metro
-        description: Set to 1 if the state has greater than 15 distinct CBSA officers of metro type, otherwise, set to 0
+      - name: greater_than_50_CBSA_metro
+        description: Set to 1 if the state has greater than 50 CBSA officers of metro type, otherwise, set to 0

address/schemas/country.csv

@@ -0,0 +1,4 @@
+column_name,column_description
+zip_code,the zip code of the state in the country
+county,the country 
+state,the state of the country

{inputs_snowflake/address → address}/schemas/zip_data.csv

@@ -2,7 +2,7 @@ column_name,column_description
 zip_code,the zip code of the postal point
 city,the city where the postal point locates
 state,the state of the city
-multi_county,whether the county that the city belongs to is multi_county
+multi_county,whether the country that the city belongs to is multi_country
 type,the type of the postal point
 organization,the organization to which the postal point belongs
 time_zone,the time zone of the postal point location
@@ -11,7 +11,7 @@ latitude,the latitude of the postal point location
 longitude,the longitude of the postal point location
 elevation,the elevation of the postal point location
 state_fips,state-level FIPS code
-county_fips,county-level FIPS code
+county_fips,country-level FIPS code
 region,the region where the postal point locates 
 division,the division of the organization 
 population_2020,the population of the residential area in 2020

{inputs_redshift/airline → airline}/data_model.yaml

@@ -6,7 +6,7 @@ models:
         description: The airline code.
       - name: airline_name
         description: The airline name.
-      - name: flight_number_had_the_longest_delay_in_departure
+      - name: flight_number_had_the_lonest_delay_in_departure
         description: the flight number of the flight operated by the airline that had the longest delay in departure, with ties broken by the ascending order of the flight number
       - name: num_flights_operate_in_2018
         description: the number of flights operated by the airline in 2018, replace NULL values with 0.

{inputs_snowflake/amplitude → amplitude}/data_model.yaml

@@ -3,9 +3,9 @@ models:
     description: Each record represents event data, enhanced with event type data and unnested event, group, and user properties. 
     columns:
       - name: unique_event_id
-        description: A surrogate key that uniquely identifies each event, derived from event_id, device_id, client_event_time, and amplitude_user_id. Use the dbt utils package to generate the surrogate key.
+        description: A surrogate key that uniquely identifies each event, derived from event_id, device_id, and client_event_time.
       - name: unique_session_id
-        description: A surrogate key that uniquely identifies each session, derived from user_id and session_id. Use the dbt utils package to generate the surrogate key.
+        description: A surrogate key that uniquely identifies each session, derived from user_id and session_id
       - name: amplitude_user_id
         description: Unique key for each user, which is user_id by default. If user_id does not exist, use amplitude_id
       - name: event_id
@@ -20,23 +20,21 @@ models:
           client_upload_time) 2015-08-10T12:00:00.000000 We use this timestamp to
           organize events on Amplitude charts. Note: If the difference between
           server_received_time and client_upload_time is less than 60 seconds, the
-          event_time will not be adjusted and will equal the client_event_time.
-        format: YYYY-MM-DD HH:MM:SS.fff
+          event_time will not be adjusted and will equal the client_event_time
       - name: event_day
         description: Day of event time
-        format: YYYY-MM-DD
       - name: unique_event_type_id
-        description: A surrogate key that uniquely identifies each event type, derived from event_type_id and project_name. Use the dbt utils package to generate the surrogate key.
+        description: A unique identifier for each event type.
       - name: event_type_id
         description: Event type ID
       - name: event_type_name
         description: Event type name
       - name: session_id
-        description: The session start time in milliseconds since epoch.All events within the same session share the same session ID. By default, the setting in Amplitude for the session property is session ID. All events with the same session ID and the same user ID will be grouped into the same session. The session ID does not have to be unique across multiple users. Session IDs for events sent via the Amplitude SDKs are automatically generated and managed.
+        description: The session start time in milliseconds since epoch.All events within the same session share the same session ID. By default, the setting in Amplitude for the session property is session ID. All events with the same session ID and the same user ID will be grouped into the same session. The session ID does not have to be unique across multiple users. Session IDs for events sent via the Amplitude SDKs are automatically generated and managed. However, for events sent via the HTTP API, Amplitude defaults to a session ID of -1. This means the event is excluded from all session metrics.
       - name: session_event_number
-        description: The number of the event within the session, ordered by time of event, with ties broken by event unique ID ascending.
+        description: The number of the event within the session, ordered by time of event.
       - name: user_event_number
-        description: The sequential number of the event within the user's activity, ordered by event time ascending, with ties broken by event unique ID ascending.
+        description: A sequential count of events triggered by a user, indicating the order of events within a user’s activity.
       - name: group_types
         description: Group types. "Groups" in the source table, renamed here. See the Accounts documentation for more information.
       - name: user_id
@@ -44,10 +42,10 @@ models:
           A readable ID specified by you.
           Amplitude uses a combination of three different methods to identify your users: device IDs, Amplitude ID, and user IDs. The first comes directly from your users' devices, while the second is an ID that Amplitude automatically creates once it has enough information to conclusively identify a unique user. The user ID, however, is something you'd set up.
           In Amplitude, a user ID is a unique identifier applied to individual users. Using them is optional, but recommended: your product should set a user ID once a user has created an account, logged in, or is otherwise identified in your product.
-          Amplitude can use a user ID to reconcile events across multiple devices under the same user ID. Additionally, a user's event data will be merged on the backend so that all anonymous events prior to the assignment of a user ID will be connected to the correct user. For this reason, you can wait to assign user IDs if that makes sense for your product. Conversely, this is also why you should not set user IDs for anonymous users. Once set, user IDs in Amplitude cannot be changed.
+          Amplitude can use a user ID to reconcile events across multiple devices under the same user ID. Additionally, a user's event data will be merged on the backend so that all anonymous events prior to the assignment of a user ID will be connected to the correct user. For this reason, you can wait to assign user IDs if that makes sense for your product. Conversely, this is also why you should not set user IDs for anonymous users.
+          Once set, user IDs in Amplitude cannot be changed.Once set, user IDs in Amplitude cannot be changed.
       - name: user_creation_time
         description: Event_time (UTC) of the user's first event
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: amplitude_id
         description: An internal ID used to count unique users.
       - name: app
@@ -56,18 +54,14 @@ models:
         description: Project ID
       - name: client_event_time
         description: Local timestamp (UTC) of when the device logged the event.
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: client_upload_time
         description: The local timestamp (UTC) of when the device uploaded the event.
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: server_received_time
         description: Amplitude timestamp (UTC) of when servers received the event
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: server_upload_time
         description: Amplitude timestamp (UTC) of when the event data was uploaded to Amplitude servers
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: country
-        description: Country where event was registered.
+        description: Country
       - name: data
         description: Dictionary where certain fields such as first_event and merged_amplitude_id are stored.
       - name: device_id
@@ -82,28 +76,24 @@ models:
         description: The count of events in a session
       - name: session_started_at
         description: The time of the first event in a session
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: session_ended_at
         description: The time of the last event in a session
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: user_session_number
-        description: A sequential identifier for each session initiated by a user, ordered by session start time, helping to track a user's sessions over time.
+        description: A sequential identifier for each session initiated by a user, helping to track users across sessions.
       - name: session_started_at_day
         description: The date on which a session started.
-        format: YYYY-MM-DD
       - name: session_ended_at_day
         description: The date on which a session ended.
-        format: YYYY-MM-DD
       - name: session_length_in_minutes
         description: The length of the session, in minutes
       - name: is_first_user_session
-        description: Boolean of whether or not a session is the user's first session. Use 1 for true and 0 for false.
+        description: Boolean of whether or not a session is the user's first session
      
   - name: amplitude__sessions
     description: Each record represents a distinct session with aggregated metrics for that session.
     columns:
       - name: unique_session_id
-        description: A surrogate key that uniquely identifies each session, derived from user_id and session_id. Use the dbt utils package to generate the surrogate key.
+        description: A surrogate key that uniquely identifies each session, derived from user_id and session_id
       - name: user_id
         description: >
           A readable ID specified by you.
@@ -115,22 +105,18 @@ models:
         description: The count of events in a session
       - name: session_started_at
         description: The time of the first event in a session
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: session_ended_at
         description: The time of the last event in a session
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: session_length_in_minutes
         description: The length of the session, in minutes
       - name: session_started_at_day
         description: The day the session started
-        format: YYYY-MM-DD
       - name: session_ended_at_day
         description: The day the session ended
-        format: YYYY-MM-DD
       - name: user_session_number
-        description: A sequential identifier for each session initiated by a user, ordered by session start time, helping to track a user's sessions over time.
+        description: The number of the session, within a user's lifetime
       - name: is_first_user_session
-        description: Boolean of whether or not a session is the user's first session. Use 1 for true and 0 for false.
+        description: Boolean of whether or not a session is the user's first session
 
   - name: amplitude__user_enhanced
     description: Each record represents a distinct user with aggregated metrics for that user.
@@ -139,13 +125,10 @@ models:
         description: Unique key for each user, which is user_id by default. If user_id does not exist, use amplitude_id
       - name: user_created_at
         description: Event_time (UTC) of the user's first event
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: first_session_at
         description: Timestamp of user's first recorded activity
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: last_session_at
         description: Timestamp of user's most recent activity
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: total_events_per_user
         description: The total number of events for a certain user
       - name: total_sessions_per_user

{inputs_snowflake/app_store → app_store}/data_model.yaml

@@ -11,7 +11,7 @@ models:
       - name: num_nan_or_null_comment_reviews
         description: the number of reviews the app recieved whose comment is 'nan' or null, replace NULL values with 0.
       - name: per_ratio_between_positive_and_negative_setiments
-        description: The percentage ratio between the number of positive and negative sentiments for the app, calculated using the formula (Positive / Negative) * 100.
+        description: The percentage ratio between positive and negative sentiments for the app
       - name: num_reviews_with_neutral_attitude
         description: The number of reviews with a neutral attitude for the app, replace NULL values with 0.
       

{inputs_databricks/apple_store → apple_store}/data_model.yaml

@@ -1,6 +1,6 @@
 models:
   - name: apple_store__device_report
-    description: Each record represents daily subscription metrics by app_id, source_type and device. Rows exist only where app_store_device or crashes_device have data. Other source tables contribute metric values only.
+    description: Each record represents daily subscription metrics by app_id, source_type and device
     columns:
       - name: date_day
         description: The date of the report and respective recorded metric(s); follows the format YYYY-MM-DD.
@@ -29,18 +29,18 @@ models:
       - name: total_downloads
         description: Total Downloads is the sum of Redownloads and First Time Downloads.
       - name: active_devices
-        description: The count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
+        description: The count of active_device is the count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
       - name: active_devices_last_30_days
-        description: The count of devices that ran the app at least one time and for at least two seconds on the date_day of the report minus 30 days (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices last 30 days or no value from the source report that day.
+        description: The count of active_devices_last_30_days is the count of devices that ran the app at least one time and for at least two seconds on the date_day of the report minus 30 days (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices last 30 days or no value from the source report that day.
       - name: deletions
-        description: The count of deletions. A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
+        description: A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
       - name: installations
-        description: The count of installations. An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
+        description: An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
       - name: sessions 
         description: Sessions is the count of the number of times the app has been used for at least two seconds (User Opt-In only). If the app is in the background and is later used again, that counts as another session. A value of 0 indicates there were 0 sessions or no value from the source report that day.
 
   - name: apple_store__source_type_report
-    description: Each record represents daily metrics by app_id and source_type. Rows exist only where app_store_device has a record. Other source tables contribute metric values only.
+    description: Each record represents daily metrics by app_id and source_type
     columns:
       - name: date_day
         description: The date of the report and respective recorded metric(s); follows the format YYYY-MM-DD.
@@ -61,16 +61,16 @@ models:
       - name: total_downloads
         description: Total Downloads is the sum of Redownloads and First Time Downloads.
       - name: active_devices
-        description: The count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
+        description: The count of active_device is the count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
       - name: deletions
-        description: The count of deletions. A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
+        description: A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
       - name: installations
-        description: The count of installations. An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
+        description: An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
       - name: sessions 
         description: Sessions is the count of the number of times the app has been used for at least two seconds (User Opt-In only). If the app is in the background and is later used again, that counts as another session. A value of 0 indicates there were 0 sessions or no value from the source report that day.
 
   - name: apple_store__overview_report
-    description: Each record represents daily metrics for each app_id. One row per (date_day, app_id) where app_store_device has a record. Other source tables contribute metric values only .
+    description: Each record represents daily metrics for each app_id
     columns:
       - name: date_day
         description: The date of the report and respective recorded metric(s); follows the format YYYY-MM-DD.
@@ -91,16 +91,16 @@ models:
       - name: total_downloads
         description: Total Downloads is the sum of Redownloads and First Time Downloads.
       - name: active_devices
-        description: The count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
+        description: The count of active_device is the count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
       - name: deletions
-        description: The count of deletions. A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
+        description: A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
       - name: installations
-        description: The count of installations. An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
+        description: An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
       - name: sessions 
         description: Sessions is the count of the number of times the app has been used for at least two seconds (User Opt-In only). If the app is in the background and is later used again, that counts as another session. A value of 0 indicates there were 0 sessions or no value from the source report that day.
 
   - name: apple_store__platform_version_report
-    description: Each record represents daily metrics for each by app_id, source_type and platform version. Rows exist only where app_store_platform_version or crashes_platform_version have data. Other source tables contribute metric values only.
+    description: Each record represents daily metrics for each by app_id, source_type and platform version
     columns:
       - name: date_day
         description: The date of the report and respective recorded metric(s); follows the format YYYY-MM-DD.
@@ -129,19 +129,19 @@ models:
       - name: total_downloads
         description: Total Downloads is the sum of Redownloads and First Time Downloads.
       - name: active_devices
-        description: The count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
+        description: The count of active_device is the count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
       - name: active_devices_last_30_days
-        description: The count of devices that ran the app at least one time and for at least two seconds on the date_day of the report minus 30 days (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices last 30 days or no value from the source report that day.
+        description: The count of active_devices_last_30_days is the count of devices that ran the app at least one time and for at least two seconds on the date_day of the report minus 30 days (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices last 30 days or no value from the source report that day.
       - name: deletions
-        description: The count of deletions. A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
+        description: A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
       - name: installations
-        description: The count of installations. An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
+        description: An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
       - name: sessions 
         description: Sessions is the count of the number of times the app has been used for at least two seconds (User Opt-In only). If the app is in the background and is later used again, that counts as another session. A value of 0 indicates there were 0 sessions or no value from the source report that day.
 
 
   - name: apple_store__app_version_report
-    description: Each record represents daily metrics for each by app_id, source_type and app version. Rows exist only where usage_app_version or crashes_app_version have data. Other source tables contribute metric values only.
+    description: Each record represents daily metrics for each by app_id, source_type and app version
     columns:
       - name: date_day
         description: The date of the report and respective recorded metric(s); follows the format YYYY-MM-DD.
@@ -156,12 +156,12 @@ models:
       - name: crashes
         description: The number of recorded crashes experienced (User Opt-In only); a value of 0 indicates there were 0 crash reports or no value from the source report that day.
       - name: active_devices
-        description: The count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
+        description: The count of active_device is the count of devices that ran the app at least one time and for at least two seconds on a given day (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices or no value from the source report that day.
       - name: active_devices_last_30_days
-        description: The count of devices that ran the app at least one time and for at least two seconds on the date_day of the report minus 30 days (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices last 30 days or no value from the source report that day.
+        description: The count of active_devices_last_30_days is the count of devices that ran the app at least one time and for at least two seconds on the date_day of the report minus 30 days (User Opt-In only); this metric is presumed to be de-duplicated daily as received from the source data, therefore, aggregating over a span of days is better done in the UI. A value of 0 indicates there were 0 active devices last 30 days or no value from the source report that day.
       - name: deletions
-        description: The count of deletions. A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
+        description: A deletion occurs when a user removes your app from their device (User Opt-In only). Data from resetting or erasing a device’s content and settings is not included. A value of 0 indicates there were 0 deletions or no value from the source report that day.
       - name: installations
-        description: The count of installations. An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
+        description: An installation event is when the user opens the App after they've downloaded it (User Opt-In only). If the App was downloaded but not opened or opened offline, this will not count; if the user opts out of sending data back to Apple, there will also be no data here. A value of 0 indicates there were 0 installations or no value from the source report that day.
       - name: sessions 
         description: Sessions is the count of the number of times the app has been used for at least two seconds (User Opt-In only). If the app is in the background and is later used again, that counts as another session. A value of 0 indicates there were 0 sessions or no value from the source report that day.

{inputs_snowflake/asana → asana}/data_model.yaml

@@ -10,16 +10,12 @@ models:
         description: Boolean that is true if the task is currently marked complete.
       - name: completed_at
         description: Timestamp of when the task was marked complete.
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: created_at
         description: Timestamp of when the task was created
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: due_date
         description: Date the task is due, if provided.
-        format: YYYY-MM-DD
       - name: task_modified_at
         description: Timestamp of when the task was last modified
-        format: YYYY-MM-DD HH:MM:SS.fff
       - name: task_description
         description: Free-form text describing the task, as seen in the UI.
       - name: workspace_id
@@ -82,15 +78,12 @@ models:
         description: Boolean representing if the project has been archived in the UI
       - name: created_at
         description: Timestamp of when the project was created
-        format: YYYY-MM-DD H[H]:MM:SS
       - name: current_status
         description: The most recent progress status update for the project (free-form string)
       - name: due_date
         description: The date the project is due on, if given
-        format: YYYY-MM-DD H[H]:MM:SS
       - name: last_modified_at
         description: Timestamp of when the project was last modified (doesn't include comments or tasks)
-        format: YYYY-MM-DD H[H]:MM:SS
       - name: owner_user_id
         description: Foreign key referencing the USER who owns the project.
       - name: number_of_users_involved
@@ -115,7 +108,7 @@ models:
       - name: number_of_active_projects
         description: Count of non-archived projects
       - name: active_projects
-        description: Comma-separated string of non-archived project IDs associated with the team, sorted alphabetically by project ID. NULL if the team has no active projects.
+        description: Aggregated list of non archived projects associated with the team
       - name: number_of_archived_projects
         description: Count of archived projects
   
@@ -128,9 +121,8 @@ models:
         description: UI-facing name of the tag
       - name: created_at
         description: Timestamp of when the tag was created
-        format: YYYY-MM-DD H[H]:MM:SS
       - name: number_of_open_tasks
-        description: Count of the currently open tasks with this tag.
+        description: Count of the currently open tasks with this tag. 
       - name: number_of_assigned_open_tasks
         description: Count of the open and assigned tasks with this tag. Set to 0 if NULL.
       - name: number_of_tasks_completed