The section that pulls in the data dictionary (in getcensus_catalog and repeated in getcensus_main after the API call) retrieves the estimate ID and label but not the concept (i.e. the table name). Since the concept/table name often defines the universe (ex. households, families, race/ethnicity), I think it's important to have visible to the user.
The fix would be to change how the program pulls in the data dictionary JSON so that it pulls the concept element in addition to ID and label elements. For the getcensus_catalog, the concept element could simply be put into a new column. For getcensus_main, it's trickier.... it could be put into variable notes, but the program already uses variable notes to house labels that'd been abbreviated.
The section that pulls in the data dictionary (in
getcensus_catalog
and repeated ingetcensus_main
after the API call) retrieves the estimate ID and label but not the concept (i.e. the table name). Since the concept/table name often defines the universe (ex. households, families, race/ethnicity), I think it's important to have visible to the user. The fix would be to change how the program pulls in the data dictionary JSON so that it pulls the concept element in addition to ID and label elements. For thegetcensus_catalog
, the concept element could simply be put into a new column. Forgetcensus_main
, it's trickier.... it could be put into variable notes, but the program already uses variable notes to house labels that'd been abbreviated.