Template:Data Integrity Check: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 42: | Line 42: | ||
| {{{DIC_implementation_date |not entered}}} | | {{{DIC_implementation_date |not entered}}} | ||
|} </div> <includeonly>[[Category:Data Integrity Checks]] | |} </div> <includeonly>[[Category:Data Integrity Checks]] | ||
{{#set: | {{#set: DICStatus::{{{DIC_status|needs review}}} }} <!-- is default because if not needed, should have different value --> | ||
</includeonly> | </includeonly> | ||
Revision as of 10:10, 2018 August 23
This template manages information related to Data Integrity Checks.
To use:
{{Data Integrity Check
| DIC_summary = what is the check (one-liner)
| DIC_related_concepts = list of related pages (probably the one it's on, but there might be others...)
| DIC_firmness = hard check (not allowed) or soft check (allowed, but give error; in CFE this means it has to go into the ... table, and cross checks have to consider that table)
| DIC_app = which of the following are checking this: CCMDB, CFE, SAS (new template call for each)
| DIC_coding = how to find this in containing program, eg. SAS file, function name, query name...
| DIC_status = implementation status (needs review, ready to implement, implemented)
| DIC_implementation_date = date change was rolled out / first applied
}}
- if ready to implement, the template should also put the check on the Requested Changes Page. Now there is a tricky thing! Means we actually need to template requested changes in the first place. And if we go there, should a requested change turn into a log entry? It all becomes really disjointed but also powerful.
| Data Integrity Checks | |
| Summary: | not entered |
| Related: | not entered |
| Firmness: | not entered |
| Coding: | not entered |
| Status: | not entered |
| Implementation Date: | not entered |