CFE editing - need integrity checks in place to catch editing errors
- Admit transfer discharge range as from CCMDB
Why not to do this inline?
- What would trigger the checks? We don't have "complete" to trigger a check, so what would trigger it? on_change has problems when used on comparison of multiple fields.
Best to not do this inline after all.
- We'll want to add some "post processing checks" that Pagasa would run after all edits for a day. To be done between Quality Assurance queries in CFE and actually setting records to "vetted".
What sort of checks do we actually want?
|
- This would best be based on things Pagasa is likely to check and change, and I think she most likely changes the following:
- So checks I can think of would be:
- All S, B, T have to be before D
- any T has to be after the B it's linked to
- any S/B has to be before any CCI and ICD10, and D has to be after these
- Pagasa, Julie, can you think of other things to check? Would running these queries just before vetting work for Pagasa? Ttenbergen 16:24, 2022 August 9 (CDT)
|
Related articles