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
Decision made on 12/06/2023:The mapping in the table above between Census Keys and GSA/FAC Options is correct and can be implemented as part of the data migration logic. On Census side the S key stands for Special Purpose Framework.
Handling SP_Framework Basis
Census Option
GSA/FAC Option
"cash"
"cash_basis"
"other"
"other_basis"
"regulatory"
???
"contractual"
"contractual_basis"
"tax"
"tax_basis"
Decision made on 12/06/2023:The GSA/FAC validation schema should be updated to include the regulatory_basis option.
Decision made on 12/06/2023:The mapping in the table above is approved.
Handling of PDF Files:
Are we expecting to receive PDFs from Census?
Decision made on 12/06/2023:Yes, Census will provide PDFs to the GSA/FAC team. Currently, handling these files is considered out of scope.
Handling Missing Auditee UEI:
Confirm that missing auditee UEI will be replaced with GSAUEINOTFND.
Decision made on 12/06/2023:Use the GSA_MIGRATION keyword as the default value for any replacements.
Transformations Not Yet Activated:
For audits with "U", "u", "rd", or "RD" in the CFDA attribute and an empty award identification, we plan to use f"ADDITIONAL AWARD INFO - DBKEY {dbkey}". Is this correct?
Decision made on 12/06/2023:Use the GSA_MIGRATION keyword as the default value for any replacements.
If the audit's LOANS attribute is "Y" and the loan balance is empty, it will be filled with 1. Is this correct?
Decision made on 12/06/2023:Use the GSA_MIGRATION keyword as the default value for any replacements. Update the GSA/FAC validation schema to allow this keyword.
Decision made on 12/06/2023:The transformation should only replace zero passthrough amounts with empty strings when the is_passed flag is N.
Cluster Name Validation:
What is the procedure for handling cases where the cluster_name is not in the cluster name list, thus failing validation?
Decision made on 12/06/2023:Allow all cluster_name values encountered to pass validation.
Handling 'N' in Audit's DIRECT Attribute:
If the audit's DIRECT attribute is "N" and the passthrough name or ID is empty, confirm that they can be filled with "NO PASSTHROUGH NAME PROVIDED" and "NO PASSTHROUGH ID PROVIDED" respectively.
Decision made on 12/06/2023:Use the GSA_MIGRATION keyword as the default value for any replacements.
How should to handle program numbers that fail to validate against our current regex? Should we rewrite them to "FIX," "UNK," or some other designation?
Decision made on 12/06/2023:If the agency prefix is validated successfully and the extension fails, replace the extension with GSA_MIGRATION. However, if the prefix itself does not validate, then the report migration should be failed..
audit_information.py
Is it right to default dollar_threshold to 750,000 when no value is found, or use GSA_MIGRATION? I have seen different values for dollar_threshold in historic data, and that made me wonder if inserting a default value there might not be right. Also, I cannot think of a reason why this would be left empty, so I am more inclined to use the magic word GSA_MIGRATION here, but I am curious to know the team's decision.
Decision made on 12/12/2023:Use the GSA_MIGRATION keyword as the default value.
findings.py
This is a simple one: in xform_prior_year_findings, do we default prior year findings to N/A when empty, or GSA_MIGRATION? Even though this is missing data, I am more inclined to use N/A here since it will only affect cases where users were not expected to insert any meaningful data, and we favored N/A instead of an empty cell in the 2023 validation.
Decision made on 12/12/2023:Default empty prior year fields to N/A and document.
report_id_generator.py
I saw here that there is a risk of collusion in the way we generatereport_id, and I am curious to know why. We use both the year and the dbkey in the report_id, so I would expect this to be unique. If it is not, then we have a bigger problem than the report_id because all our queries assume year/dbkey uniquely identifies a submission report.
Decision made on 12/12/2023:After a team analysis, it was determined that a collusion case is very unlikely to occur. Consequently, the ticket #2680 has been closed and marked as 'unplanned'.
general_information.py and secondary_auditors.py
We may want to handle 4-digit and 8-digit ZIP codes in our first iteration. I have seen multiple instances like this and feel it would be right to do so. Options are: to let them through, or to prefix with a 0, or anything else the team agrees on. Decision made on 12/12/2023:4-digit or 8-digit zips must be prepend with 0.
notes_to_sefa.py
We don't have contains_chart_or_table in the historic data for this workbook, and because the value is disseminated, we want to agree on how we handle this. The code defaults toN, that is False, but we could also use GSA_MIGRATION, or better yet, find out where this field is hidden if it exists.
Decision made on 12/12/2023:Default empty fields to GSA_MIGRATION and document.
The text was updated successfully, but these errors were encountered:
This ticket is to compile a list of key data mappings and questions in our data migration logic for the team to review/approve.
P.S.: For pattern matching, we ignore case and space occurrences.
Mappings used in Audit Information :
Decision made on 12/06/2023: The mapping in the table above between Census Keys and GSA/FAC Options is correct and can be implemented as part of the data migration logic. On Census side the S key stands for Special Purpose Framework.
Handling SP_Framework Basis
Decision made on 12/06/2023: The GSA/FAC validation schema should be updated to include the
regulatory_basis
option.Decision made on 12/06/2023: The mapping in the table above is approved.
Decision made on 12/06/2023: Yes, Census will provide PDFs to the GSA/FAC team. Currently, handling these files is considered out of scope.
GSAUEINOTFND
.Decision made on 12/06/2023: Use the
GSA_MIGRATION
keyword as the default value for any replacements.Transformations Not Yet Activated:
f"ADDITIONAL AWARD INFO - DBKEY {dbkey}"
. Is this correct?Decision made on 12/06/2023: Use the
GSA_MIGRATION
keyword as the default value for any replacements.1
. Is this correct?Decision made on 12/06/2023: Use the
GSA_MIGRATION
keyword as the default value for any replacements. Update the GSA/FAC validation schema to allow this keyword.Negative Loan Balances:
Decision made on 12/06/2023: Update the GSA/FAC validation schema to allow negative loan balance.
Handling Zero Passthrough Amounts:
Decision made on 12/06/2023: The transformation should only replace zero passthrough amounts with empty strings when the
is_passed
flag isN
.Cluster Name Validation:
Decision made on 12/06/2023: Allow all
cluster_name
values encountered to pass validation.Handling 'N' in Audit's DIRECT Attribute:
Decision made on 12/06/2023: Use the
GSA_MIGRATION
keyword as the default value for any replacements.Decision made on 12/06/2023: TBD .
Decision made on 12/06/2023: If the agency prefix is validated successfully and the extension fails, replace the extension with
GSA_MIGRATION
. However, if the prefix itself does not validate, then the report migration should be failed..dollar_threshold
to 750,000 when no value is found, or useGSA_MIGRATION
? I have seen different values fordollar_threshold
in historic data, and that made me wonder if inserting a default value there might not be right. Also, I cannot think of a reason why this would be left empty, so I am more inclined to use the magic wordGSA_MIGRATION
here, but I am curious to know the team's decision.Decision made on 12/12/2023: Use the
GSA_MIGRATION
keyword as the default value.xform_prior_year_findings
, do we default prior year findings toN/A
when empty, orGSA_MIGRATION
? Even though this is missing data, I am more inclined to useN/A
here since it will only affect cases where users were not expected to insert any meaningful data, and we favoredN/A
instead of an empty cell in the 2023 validation.Decision made on 12/12/2023: Default empty prior year fields to
N/A
and document.report_id
, and I am curious to know why. We use both the year and thedbkey
in thereport_id
, so I would expect this to be unique. If it is not, then we have a bigger problem than thereport_id
because all our queries assume year/dbkey uniquely identifies a submission report.Decision made on 12/12/2023: After a team analysis, it was determined that a collusion case is very unlikely to occur. Consequently, the ticket #2680 has been closed and marked as 'unplanned'.
Decision made on 12/12/2023: 4-digit or 8-digit zips must be prepend with
0
.contains_chart_or_table
in the historic data for this workbook, and because the value is disseminated, we want to agree on how we handle this. The code defaults toN
, that is False, but we could also useGSA_MIGRATION
, or better yet, find out where this field is hidden if it exists.Decision made on 12/12/2023: Default empty fields to
GSA_MIGRATION
and document.The text was updated successfully, but these errors were encountered: