L Problem table: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 24: | Line 24: | ||
|join on=DataIntegrityChecks._pageName=_pageData._pageName,DataIntegrityChecks._pageName=Discussions._pageName | |join on=DataIntegrityChecks._pageName=_pageData._pageName,DataIntegrityChecks._pageName=Discussions._pageName | ||
|fields= | |fields= | ||
DataIntegrityChecks._pageName=page, Status, Timing, Summary, | DataIntegrityChecks._pageName=page, Status, Timing, Summary, Status, L_Problem | ||
|where=App="Centralized data front end.accdb " and (Status<>"retired" and Status<>"declined") and L_Problem=true | |where=App="Centralized data front end.accdb " and (Status<>"retired" and Status<>"declined") and (L_Problem=true or L_Problem is null) | ||
|order by=question | |order by=question | ||
|limit=0 | |limit=0 | ||
| Line 33: | Line 33: | ||
|rows per page=1000 | |rows per page=1000 | ||
}} | }} | ||
, question | |||
== Related Articles == | == Related Articles == | ||
{{Related Articles}} | {{Related Articles}} | ||
Revision as of 22:17, 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
Link to table of cross-checks that use L_Problem table to exclude false-positives
, question