You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current sales view, default.vw_pin_sale, uses only sales from the iasWorld SALES table. This table is updated on a long lag, and is often missing sales from the tables that feed it (MyDec extracts from the Illinois DOR).
We should create a new experimental sales table that combines sales data from multiple sources, such that a sale will appear in the view if it appears in any of the sources. To start, let's combine the iasWorld SALES table (iasworld.sales) and MyDec (sale.mydec). We should default to using data/information from the SALES table, but if that doesn't exist, we should fallback to MyDec.
Reach goal: We also used to have a separate feed of Cook County Recorder of Deeds (CCRD) sales. Such sales sometimes only appear in the CCRD database, so it would be good to get this feed back. If we do gain access to such a feed, we should combine it with the other two with the priority: iasworld > mydec > ccrd.
The sale view should contain almost all the same columns as the existing default.vw_pin_sale (sales val results, price, date, buyer/seller name, etc.). However, we can drop the extraneous MyDec columns from this version of the view. The sale view should have a new column indicating the source of the sale, one of: iasworld, mydec, or ccrd.
9/12/2024 Update
After discussing with Billy and Dan we are going to take a different direction. We are going to add the mydec data into the existing vw_pin_sale data. We will use coalesce statements to prioritize iasworld data and use an indicator column to let us know where the doc_no was pulled from
The text was updated successfully, but these errors were encountered:
The current sales view,
default.vw_pin_sale
, uses only sales from the iasWorldSALES
table. This table is updated on a long lag, and is often missing sales from the tables that feed it (MyDec extracts from the Illinois DOR).We should create a new experimental sales table that combines sales data from multiple sources, such that a sale will appear in the view if it appears in any of the sources. To start, let's combine the iasWorld
SALES
table (iasworld.sales
) and MyDec (sale.mydec
). We should default to using data/information from theSALES
table, but if that doesn't exist, we should fallback to MyDec.Reach goal: We also used to have a separate feed of Cook County Recorder of Deeds (CCRD) sales. Such sales sometimes only appear in the CCRD database, so it would be good to get this feed back. If we do gain access to such a feed, we should combine it with the other two with the priority:
iasworld
>mydec
>ccrd
.The sale view should contain almost all the same columns as the existing
default.vw_pin_sale
(sales val results, price, date, buyer/seller name, etc.). However, we can drop the extraneous MyDec columns from this version of the view. The sale view should have a new column indicating the source of the sale, one of:iasworld
,mydec
, orccrd
.9/12/2024 Update
After discussing with Billy and Dan we are going to take a different direction. We are going to add the mydec data into the existing
vw_pin_sale
data. We will use coalesce statements to prioritize iasworld data and use an indicator column to let us know where thedoc_no
was pulled fromThe text was updated successfully, but these errors were encountered: