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

Ingest BOR appeal data into lake #548

Closed
ccao-jardine opened this issue Jul 17, 2024 · 1 comment · Fixed by #553
Closed

Ingest BOR appeal data into lake #548

ccao-jardine opened this issue Jul 17, 2024 · 1 comment · Fixed by #553
Assignees

Comments

@ccao-jardine
Copy link
Member

Goal:

Build a pipeline to bring Cook County Board of Review (BOR) appeal decision history data into our lake so that we can smoothly integrate it with CCAO reporting, such as giving context and understanding large BOR reductions.

Desired use cases:

  • We can include the appeal ChangeReason description when we report on a BOR appeal. This helps distinguish BOR reductions which might have been recommended by the Assessor (or statutory) from those which aren't.
  • We can use the appeal docket number (specifically, what looks like a concatenation of AppealTrk and AppealSeq), and use that in BOR reduction reporting to identify the number of PINs in the docket, and the summed AVs of PINs in the docket at each stage.
  • As above, we could compare PINs in a commercial docket to PINs in our own commercial database to identify and investigate diffs.
  • We can use it to identify PINs, regions, or property classes that consistently receive reductions at both the CCAO and BOR to identify process changes for 1st pass so that the PIN doesn't have to appeal.

Source data:

The BOR publishes data on its appeal decision history here.

Specifics:

  • Please create a new db for this, ccbor
  • I suppose we don't need to ingest data we already have (such as PIN10, long, lat) but it's not a problem for me if we do ingest it.
@ccao-jardine
Copy link
Member Author

@dfsnow, feel free to work or reassign!

@dfsnow dfsnow assigned wrridgeway and unassigned dfsnow Jul 17, 2024
@wrridgeway wrridgeway linked a pull request Jul 23, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

3 participants