Template:Data Integrity Check: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
mNo edit summary
mNo edit summary
 
(25 intermediate revisions by the same user not shown)
Line 1: Line 1:
<noinclude>
<noinclude>
This template manages information related to [[Data Integrity Checks]].  
This template manages information related to [[Data Integrity Checks]]. the template call is usually managed by [[Form:Data Integrity Check]].  


To use:  
To use:  
<pre>{{Data Integrity Check
<pre>{{Data Integrity Check}}
| DIC_summary = what is the check (one-liner)
</pre>
| DIC_related_concepts = list of related pages (probably the one it's on, but there might be others...)
'''and then use form'''
| 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_timing = complete always
| DIC_app = which of the following are checking this: CCMDB.mdb, Centralized data front end.accdb, 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, not feasible)
| 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.  
* 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.  
===Cargo declaration===
{{#cargo_declare:
_table = DataIntegrityChecks
|Summary=Wikitext
|Status=text
|App=page
|Timing=text
|ImplementationDate=date
|Coding=text
|Firmness=text
|L_Problem=boolean
|Backlogged=boolean
}}




Line 21: Line 28:




</noinclude> <div style="clear:right;">
 
{| class="wikitable" border="1" style="float:right; width: 100%"
 
 
 
===actual template code===
</noinclude>
{| class="wikitable" border="1" style="width: 100%"
| style="text-align: center; background-color:#99c2ff;" colspan="2" | [[Data Integrity Checks]]
| style="text-align: center; background-color:#99c2ff;" colspan="2" | [[Data Integrity Checks]]
|-
|-
Line 29: Line 41:
|-
|-
| style="background:silver; color:arsenic" align="right"| '''Related: '''
| style="background:silver; color:arsenic" align="right"| '''Related: '''
| {{{DIC_related_concepts|not entered}}}
| {{#if:{{{DIC_related_concepts|}}}|{{#arraymap:{{{DIC_related_concepts}}}|;|x|[[x]]}} }}
|-
|-
| style="background:silver; color:arsenic" align="right"| '''Firmness: '''
| style="background:silver; color:arsenic" align="right"| '''Firmness: '''
Line 35: Line 47:
|-
|-
| style="background:silver; color:arsenic" align="right"| '''Timing: '''
| style="background:silver; color:arsenic" align="right"| '''Timing: '''
| {{{DIC_timing |complete (assumed default)}}}
| {{{DIC_timing | always}}}
|-
|-
| style="background:silver; color:arsenic" align="right"| '''App: '''
| style="background:silver; color:arsenic" align="right"| '''App: '''
Line 42: Line 54:
| style="background:silver; color:arsenic" align="right"| '''Coding: '''
| style="background:silver; color:arsenic" align="right"| '''Coding: '''
| {{{DIC_coding |not entered}}}
| {{{DIC_coding |not entered}}}
|-
| style="background:silver; color:arsenic" align="right"| '''Uses [[L Problem table]]: '''
| {{#ifeq:{{{DIC_app}}}|Centralized data front end.accdb|{{{DIC_LProblem|not entered}}}|not relevant for this app}}
|-
|-
| style="background:silver; color:arsenic" align="right"| '''Status: '''
| style="background:silver; color:arsenic" align="right"| '''Status: '''
Line 48: Line 63:
| style="background:silver; color:arsenic" align="right"| '''Implementation Date: '''
| style="background:silver; color:arsenic" align="right"| '''Implementation Date: '''
| {{{DIC_implementation_date |not entered}}}
| {{{DIC_implementation_date |not entered}}}
|} </div> {{
|-
| style="background:silver; color:arsenic" align="right"| '''Backlogged: '''
| {{{DIC_backlogged|true}}} <!-- default to true if not entered -->
|} <includeonly><div style="display: none;">
 
* Cargo
{{#cargo_store:
_table = DataIntegrityChecks
|Summary={{{DIC_summary|not entered}}}
|Status={{{DIC_status|needs review}}}
|App={{{DIC_app|not entered}}}
|Timing= {{{DIC_timing |always}}}
|ImplementationDate={{{DIC_implementation_date|}}}
|Coding={{{DIC_coding |not entered}}}
|Firmness={{{DIC_firmness |not entered}}}
|L_Problem={{{DIC_LProblem|false}}}
|Backlogged={{{DIC_backlogged|true}}}
}}
 
* SMW
{{#set: DICLProblem={{{DIC_LProblem|false}}} }}{{
#set: DICStatus={{{DIC_status|needs review}}} }} {{
#set: DICStatus={{{DIC_status|needs review}}} }} {{
#set: DICApp={{{DIC_app|not entered}}} }} {{
#set: DICApp={{{DIC_app|not entered}}} }} {{
#set: DICSummary={{{DIC_summary|not entered}}} }}<includeonly>[[Category:Data Integrity Checks]]{{#if:{{{DIC_app}}}|[[Category:{{{DIC_app}}}]]|}}&nbsp;</includeonly>
#set: DICSummary={{{DIC_summary|not entered}}} }}{{
#if:{{{DIC_related_concepts|}}}|{{#arraymap:{{{DIC_related_concepts}}}|;|x|{{#set:DICRelatedConcepts=x}} }}|}}
 
* Categories:
[[Category:Data Integrity Checks]]
{{#if:{{{DIC_app}}}|[[Category:{{{DIC_app}}}]]|}}&nbsp;  
 
* form:
{{#default_form:Data Integrity Check}}
</div></includeonly>

Latest revision as of 09:37, 2022 January 12

This template manages information related to Data Integrity Checks. the template call is usually managed by Form:Data Integrity Check.

To use: 

{{Data Integrity Check}}

and then use form

  • 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.

Cargo declaration

This template defines the table "DataIntegrityChecks". View table.




actual template code

Data Integrity Checks
Summary: not entered
Related:
Firmness: not entered
Timing: always
App: not entered
Coding: not entered
Uses L Problem table: not relevant for this app
Status: not entered
Implementation Date: not entered
Backlogged: true
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Template:Data_Integrity_Check&oldid=153966"