CFE Inline Integrity Checks: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
Line 1: Line 1:
===CFE editing - need integrity checks in place to catch editing errors===
Pagasa edits in CFE, and right now there are no checks in place for typos in these edits.
*Admit transfer discharge range as from CCMDB


=== Why not to do this inline? ===
== When and how would these checks run? ==
* 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.
Cross-checks in CCMDB are triggered by collectors checking the various "complete" boxes, but there is no equivalent to this in CFE, especially since Pagasa can legitimately edit tables directly or via query, so these checks would likely need to be triggered manually, likely between [[Quality Assurance queries in CFE]] and actually setting records to "vetted".  
'''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? ===
== What sort of checks do we actually want? ==
{{Discuss |  
{{Discuss |  
* This would best be based on things Pagasa is likely to check and change, and I think she most likely changes the following:  
* This would best be based on things Pagasa is likely to check and change, and I think she most likely changes the following:  

Revision as of 16:28, 2022 August 9

Pagasa edits in CFE, and right now there are no checks in place for typos in these edits.

When and how would these checks run?

Cross-checks in CCMDB are triggered by collectors checking the various "complete" boxes, but there is no equivalent to this in CFE, especially since Pagasa can legitimately edit tables directly or via query, so these checks would likely need to be triggered manually, likely 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)
  • SMW


  • Cargo


  • Categories

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=CFE_Inline_Integrity_Checks&oldid=157055"