EARD will likely need to know more level of detail than the current flag-based columns provide. currently, theres a comma-separated list of all variable IDs that contributed to a question flag. but that makes it difficult to know which source datasets those variable IDs came from
we will likely wait until after the app is launched and EARD has feedback to get their input on how best to do this. two approaches we've discussed are described below
wide GFT flag source outputs
one column for every question flag X source dataset
e.g. natural_resources_forever_wild, shadow_nat_resources_forever_wild, cats_permit
add new columns to the current final table because GFT app needs a single table (~60 columns)
EARD will likely need to know more level of detail than the current flag-based columns provide. currently, theres a comma-separated list of all variable IDs that contributed to a question flag. but that makes it difficult to know which source datasets those variable IDs came from
we will likely wait until after the app is launched and EARD has feedback to get their input on how best to do this. two approaches we've discussed are described below
wide GFT flag source outputs
natural_resources_forever_wild,shadow_nat_resources_forever_wild,cats_permitlong GFT flag source outputs
...