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
|
- added: 2021-07-27
- action: 2022-08-09
|
Related articles