L Problem table: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "cross check " to "cross check "
No edit summary
Line 18: Line 18:
|Notes || text || further explanations, eg why the error was not corrected or why it is a false positive
|Notes || text || further explanations, eg why the error was not corrected or why it is a false positive
|}
|}
=== List of cross-checks that use L_Problems ===
{{#cargo_query:
tables=DataIntegrityChecks,Discussions,_pageData
|join on=DataIntegrityChecks._pageName=_pageData._pageName,DataIntegrityChecks._pageName=Discussions._pageName
|fields=
CONCAT("\[\{\{fullurl:",DataIntegrityChecks._pageName, "{{!}}action=edit\}\} edit]")=edit,
DataIntegrityChecks._pageName=page, Status, Timing, Firmness, Summary, question, who
|where=App="Centralized data front end.accdb " and (Status<>"retired" and Status<>"declined") and L_Problem=true
|order by=question
|limit=0
|more=Show table of cross-checks that use this table to exclude false-positives
|default=Nothing found
|format=dynamic table
|rows per page=1000
}}


== Related Articles ==
== Related Articles ==

Revision as of 09:34, 22 July 2025

The L_Problem table in Centralized data.mdb contains known data errors to exclude them from several CFE Data Integrity Checks. This could be needed because we deliberately decided they were not worth fixing, or because a cross check delivers a false positive in some circumstances.

It is manually populated by the data processor as she encounters the errors or false positives, for example as part of vetting.

L_Problem contains the fields

field type description
D_ID long unique record ID
Query text One of the following:
Notes text further explanations, eg why the error was not corrected or why it is a false positive

List of cross-checks that use L_Problems

More...

Related Articles

Related articles: