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 52: | Line 52: | ||
#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}}}]]|}} </includeonly> | #if:{{{DIC_related_concepts|}}}|{{#arraymap:{{{DIC_related_concepts}}}|;|x|{{#set:DICRelatedConcepts=x}} }}|}}<includeonly>[[Category:Data Integrity Checks]]{{#if:{{{DIC_app}}}|[[Category:{{{DIC_app}}}]]|}} .</includeonly> | ||
Revision as of 08:15, 2019 February 7
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 |