<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.dafne.bi-services.sk/index.php?action=history&amp;feed=atom&amp;title=Tag</id>
	<title>Tag - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.dafne.bi-services.sk/index.php?action=history&amp;feed=atom&amp;title=Tag"/>
	<link rel="alternate" type="text/html" href="https://wiki.dafne.bi-services.sk/index.php?title=Tag&amp;action=history"/>
	<updated>2026-10-23T19:25:47Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.34.4</generator>
	<entry>
		<id>https://wiki.dafne.bi-services.sk/index.php?title=Tag&amp;diff=80&amp;oldid=prev</id>
		<title>Dafne: Documentation import</title>
		<link rel="alternate" type="text/html" href="https://wiki.dafne.bi-services.sk/index.php?title=Tag&amp;diff=80&amp;oldid=prev"/>
		<updated>2026-08-06T13:36:49Z</updated>

		<summary type="html">&lt;p&gt;Documentation import&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;A &amp;#039;&amp;#039;&amp;#039;tag&amp;#039;&amp;#039;&amp;#039; is an informative label attached to a [[Task]]. Tags carry no effect on planning or execution; they exist for reporting, filtering and aggregation.&lt;br /&gt;
&lt;br /&gt;
A task may carry several tags. Tags are typically used to record which consumers depend on a task&amp;#039;s output.&lt;br /&gt;
&lt;br /&gt;
== Attributes ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Attribute !! Description&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Name&amp;#039;&amp;#039;&amp;#039; || Name of the tag.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Description&amp;#039;&amp;#039;&amp;#039; || Free text.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Typical use ==&lt;br /&gt;
The usual pattern is to tag tasks by the department or system that consumes their data. A shared task carries every tag that applies to it:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;ETL_CUSTOMER&amp;lt;/code&amp;gt; — tagged &amp;#039;&amp;#039;Sales&amp;#039;&amp;#039; and &amp;#039;&amp;#039;Accounting&amp;#039;&amp;#039;&lt;br /&gt;
* &amp;lt;code&amp;gt;ETL_ORDER&amp;lt;/code&amp;gt; — tagged &amp;#039;&amp;#039;Sales&amp;#039;&amp;#039;&lt;br /&gt;
* &amp;lt;code&amp;gt;ETL_PROFITLOSS&amp;lt;/code&amp;gt; — tagged &amp;#039;&amp;#039;Accounting&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Downstream tasks can then be tagged according to the actual use of the data rather than according to where it happens to be computed.&lt;br /&gt;
&lt;br /&gt;
== What tags are used for ==&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Filtering the Monitor.&amp;#039;&amp;#039;&amp;#039; A tag filter restricts the task list to the tasks feeding one consumer. This is the quickest way to answer whether a particular department&amp;#039;s data is ready. See [[Monitor console]].&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Statistics.&amp;#039;&amp;#039;&amp;#039; Processing statistics can be aggregated by tag.&lt;br /&gt;
&lt;br /&gt;
== What tags do not do ==&lt;br /&gt;
Tags have &amp;#039;&amp;#039;&amp;#039;no effect on scheduling&amp;#039;&amp;#039;&amp;#039;. They do not create dependencies, do not influence priority and do not group tasks for the purposes of limits. Use a [[Group]] where the intention is to affect execution, and a tag where the intention is only to label.&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Task]]&lt;br /&gt;
* [[Group]]&lt;br /&gt;
* [[Monitor console]]&lt;/div&gt;</summary>
		<author><name>Dafne</name></author>
		
	</entry>
</feed>