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 3: | Line 3: | ||
To use: | To use: | ||
<pre>{{Data Integrity Check}}</pre> | <pre>{{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 | |||
}}</pre> | |||
* 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. | |||
[[Category:Data Integrity Check wiki infrastructure]] | [[Category:Data Integrity Check wiki infrastructure]] | ||
| Line 21: | Line 20: | ||
</noinclude>[[Category:Data Integrity Checks]] | </noinclude> ({{#if:{{{1|}}}|[[Has_IntegrityCheckStatus::{{{1}}}]]|unknown status, see [[Template:CCMDB Data Integrity Checks]] for details{{#set:Has_IntegrityCheckStatus=unknown}} }}) <includeonly>[[Category:Data Integrity Checks]]</includeonly> | ||
<div style="clear:right;"> | |||
{| class="wikitable" border="1" style="float:right" | |||
| style="text-align: center; background-color:#99c2ff;" colspan="2" | [[Data Integrity Checks]] | |||
|- | |||
| style="background:silver; color:arsenic" align="right"| '''Summary: ''' | |||
| {{{DIC_summary|not entered}}} | |||
|- | |||
| style="background:silver; color:arsenic" align="right"| '''Related: ''' | |||
| {{{DIC_related_concepts|not entered}}} | |||
|- | |||
| style="background:silver; color:arsenic" align="right"| '''Firmness: ''' | |||
| {{{DIC_firmness |not entered}}} | |||
|- | |||
| style="background:silver; color:arsenic" align="right"| '''Coding: ''' | |||
| {{{DIC_coding |not entered}}} | |||
|- | |||
| style="background:silver; color:arsenic" align="right"| '''Status: ''' | |||
| {{{DIC_status |not entered}}} | |||
|- | |||
| style="background:silver; color:arsenic" align="right"| '''Implementation Date: ''' | |||
| {{{DIC_implementation_date |not entered}}} | |||
|} </div> | |||
Revision as of 09:43, 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.
(unknown status, see Template:CCMDB Data Integrity Checks for details)
| Data Integrity Checks | |
| Summary: | not entered |
| Related: | not entered |
| Firmness: | not entered |
| Coding: | not entered |
| Status: | not entered |
| Implementation Date: | not entered |