Template:Data Integrity Check: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 3: Line 3:


To use:  
To use:  
<pre>{{Data Integrity Check
<pre>{{Data Integrity Check}} and then use form
| 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...) '''separate them with ; semicolons'''
| 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, declined, not feasible)
| DIC_implementation_date = date change was rolled out / first applied
}}


== Related articles ==
== Related articles ==
Line 47: Line 38:
| 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]]: '''
| {{{DIC_LProblems |not entered}}}
|-
|-
| style="background:silver; color:arsenic" align="right"| '''Status: '''
| style="background:silver; color:arsenic" align="right"| '''Status: '''
Line 54: Line 48:
| {{{DIC_implementation_date |not entered}}}
| {{{DIC_implementation_date |not entered}}}
|} </div> {{
|} </div> {{
#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}}} }}{{
#set: DICSummary={{{DIC_summary|not entered}}} }}{{
#if:{{{DIC_related_concepts|}}}|{{#arraymap:{{{DIC_related_concepts}}}|;|x|{{#set:DICRelatedConcepts=x}} }}|}}<includeonly>[[Category:Data Integrity Checks]]{{#if:{{{DIC_app}}}|[[Category:{{{DIC_app}}}]]|}}&nbsp;</includeonly>
#if:{{{DIC_related_concepts|}}}|{{#arraymap:{{{DIC_related_concepts}}}|;|x|{{#set:DICRelatedConcepts=x}} }}|}}<includeonly>[[Category:Data Integrity Checks]]{{#if:{{{DIC_app}}}|[[Category:{{{DIC_app}}}]]|}}&nbsp;</includeonly>

Revision as of 19:10, 2018 October 29

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

== Related articles ==
{{Related Articles}}

  • 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:
Firmness: not entered
Timing: complete (assumed default)
App: not entered
Coding: not entered
Uses L Problem table: not entered
Status: not entered
Implementation Date: not entered