CFE Inline Integrity Checks: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
|||
Line 5: | Line 5: | ||
== What sort of checks do we actually want? == | == What sort of checks do we actually want? == | ||
Pagasa agreed that the most likely items to be changed that need to trigger a check are [[Service tmp entry]] and [[Boarding Loc]] and [[Transfer Ready DtTm tmp entry]] and [[Dispo DtTm]]s, and they need to be checked. | |||
{{DT | | {{DT | | ||
Line 23: | Line 20: | ||
** T should not have missing time or should not have check mark. - --[[User:JMojica|JMojica]] 10:11, 2022 August 10 (CDT) | ** T should not have missing time or should not have check mark. - --[[User:JMojica|JMojica]] 10:11, 2022 August 10 (CDT) | ||
}} | }} | ||
The checks could run at change time, or just before vetting. | |||
== Related articles == | == Related articles == |
Revision as of 09:59, 2022 September 6
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?
Pagasa agreed that the most likely items to be changed that need to trigger a check are Service tmp entry and Boarding Loc and Transfer Ready DtTm tmp entry and Dispo DtTms, and they need to be checked.
|
The checks could run at change time, or just before vetting.
Related articles
Related articles: |