Open maurolepore opened 1 month ago
Hi @kalashsinghal thanks for your support here. Let's prioritize tomorrow in the sprint. I'm also still waiting for response from Yana, who (I believe) has worked on something similar in the past. Maybe we can use that as input.
EDIT 2024-05-28: Here is the latest version of data dictionary from the logical data model. It's not really up-to-date and mainly contains input data, not the output data, so probably not a big help :)
Addendum: Here is a Wikipedia article about data dictionaries. It lists out possible data attributes that are listed in such dictionairies. I think Mauro's template already captures the most relevant ones, but probably good to think about whether we think additional columns could be useful. For filling out the column "definition" in Mauro's template, we can also utilize the documentation in tiltIndicator and tiltIndicatorAfter which already defines many of the columns.
@kalashsinghal and @Tilmon please edit this googlesheet
@maurolepore please see this comment for the data dictionary from the DT, just for reference: https://github.com/2DegreesInvesting/tiltWebTool/issues/12#issuecomment-2133975210
I'll work on it next week.
--
@kalashsinghal, this is the ticket, and the attached .csv files were generated as you say -- "from profile_emissions and profile_sector functions of tiltIndicatorAfter".
reprex
## Emissions ``` r sector <- readr::read_csv("tiltIndicatorAfter-v0.0.0.9040-emissions.csv") #> Rows: 42 Columns: 5 #> ── Column specification ──────────────────────────────────────────────────────── #> Delimiter: "," #> chr (4): dataset, level, name, type #> lgl (1): definition #> #> ℹ Use `spec()` to retrieve the full column specification for this data. #> ℹ Specify the column types or set `show_col_types = FALSE` to quiet this message. ``` ``` r head(sector) #> # A tibble: 6 × 5 #> dataset level name type definition #>