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
but the dq_flags_staging dataframe doesn't have the flags filtered by when folks entered. If we create dq_flags_staging but restrict the benefits and income flags just to clients entering program in that time period, we end up with fewer programs in the detail dataframe.
I think that means that we can have entries in the numerator that aren't necessarily included in the denominator--is that what we want? It seems like we might want to restrict our flags to the entries that we're flagging as relevant to the time period for that flag type.
The text was updated successfully, but these errors were encountered:
I agree with you, and I think this is something I realized last year but didn't have time to correct and felt like it was a low priority thing to fix. I think I'm going to leave this open and if we're able to fix it this year then good, otherwise it's something we can fix for next year.
Would it cause problems elsewhere if we added entry exit IDs to our list of our variables to keep in the data quality script? If not, this should be a relatively easy fix and I can knock it out!
At 585, we're calculating out the data quality flags with this chunk here
but the
dq_flags_staging
dataframe doesn't have the flags filtered by when folks entered. If we createdq_flags_staging
but restrict the benefits and income flags just to clients entering program in that time period, we end up with fewer programs in thedetail
dataframe.I think that means that we can have entries in the numerator that aren't necessarily included in the denominator--is that what we want? It seems like we might want to restrict our flags to the entries that we're flagging as relevant to the time period for that flag type.
The text was updated successfully, but these errors were encountered: