Thanks! I do think this could be helpful. For tax team purposes we'll typically want to use individual occupations, but these categories were helpful for the ARPA CTC dashboard run, and maybe they would come in handy for a tax team purpose that we haven't thought of yet.
I wonder about having it be a program vs. creating the variables in the tax model dataset? That way it would be handy for non-tax model uses. But I don't have strong feelings about that.
I'm inclined to stick with the NAICS/SOC code values, just because on various occasions I've found myself referring back to code lists (sometimes to reconcile slight changes to titles or groupings) and renumbering would complicate that.
Thanks! I do think this could be helpful. For tax team purposes we'll typically want to use individual occupations, but these categories were helpful for the ARPA CTC dashboard run, and maybe they would come in handy for a tax team purpose that we haven't thought of yet.
I wonder about having it be a program vs. creating the variables in the tax model dataset? That way it would be handy for non-tax model uses. But I don't have strong feelings about that.
I'm inclined to stick with the NAICS/SOC code values, just because on various occasions I've found myself referring back to code lists (sometimes to reconcile slight changes to titles or groupings) and renumbering would complicate that.
Originally posted by @shingtgen in https://github.com/CenterOnBudget/acs-tax-model-v2/issues/34#issuecomment-2075153192