Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create csv file and web page for potential targets for tax filers, drawn from IRS spreadsheets #20

Closed
donboyd5 opened this issue Mar 2, 2024 · 5 comments

Comments

@donboyd5
Copy link
Collaborator

donboyd5 commented Mar 2, 2024

@nikhilwoodruff @martinholmer

I wrote code in R to:

  • Get IRS spreadsheets that contain summary data about tax filers for various years.
  • Extract and organize the relevant data
  • Save the data with potential targets to a csv file in this folder
  • Create a web page that
    • has the code (folded)
    • displays the potential targets in a Datatable explorer that allows filtering and sorting
    • has links to the code and to other relevant information

The code is written to minimize the risk of error inherent in extracting bits and pieces from different sections of multiple spreadsheets, and to make it easy and low-risk-of-error to add more targets from individual spreadsheets or to add additional IRS spreadsheets.

The data can be used to create summary and distributional targets for PUF variables for tax filers. The data are a superset of variables we'll want for targeting. Hence I call them "potential" targets. In early stages, we'll only target a small number of values. Later, we may target many more, but still not target everything that is in the csv file.

I expect that eventually we'll translate the potential-targets-getting code to python, although that may occur after Phase 3 of the project. The csv file (after review) may be all we need in Phases 2 and 3. Alternatively, we could move the R project into the PSL project.

@martinholmer
Copy link
Collaborator

@donboyd5, Has issue #20 (from early March) been resolved?
If so, you should close #20.
If not, please add to issue #20 that explaining what else needs to be done.

@martinholmer
Copy link
Collaborator

On July 16, @martinholmer asked this about issue #20:

@donboyd5, Has issue #20 (from early March) been resolved?
If so, you should close #20.
If not, please add to issue #20 that explaining what else needs to be done.

There has been no additions to issue #20 since July 16, so it is being closed.

@donboyd5
Copy link
Collaborator Author

@martinholmer Thanks for closing. Once we have a contract in place I'll open a new issue with planned steps for states and CDs.

@martinholmer
Copy link
Collaborator

@donboyd5 said in closed issue #20:

Once we have a contract in place I'll open a new issue with planned steps for states and CDs.

Please make the issues action-oriented so that merging a pull request will close the issue.
Any commentary that is not immediately action-oriented should be put in a GitHub Discussion.

@donboyd5
Copy link
Collaborator Author

donboyd5 commented Sep 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants