Template:Infobox command structure/doc - Revision history

GavinRobinson: typo

2017-04-23T17:33:29Z

typo

GavinRobinson: documented citation parameter

2017-04-23T17:18:17Z

documented citation parameter

GavinRobinson: updating

2016-02-13T08:49:33Z

updating

GavinRobinson: updating for new infobox

2016-01-22T16:01:25Z

updating for new infobox

GavinRobinson: updating to match current practice

2015-07-26T11:01:23Z

updating to match current practice

Mia: Added components to Subordinate unit level description

2015-02-02T20:06:19Z

Added components to Subordinate unit level description

Mia: Updating documentation

2014-12-09T17:15:33Z

Updating documentation

Mia: Removed broken internal link

2014-12-04T01:09:49Z

Removed broken internal link

Mia: /* Command structure box */ Added relationship_type

2014-11-24T01:22:29Z

‎Command structure box: Added relationship_type

Mia at 01:06, 24 November 2014

2014-11-24T01:06:41Z

@@ Line 50: / Line 50: @@
 * '''parent''' or '''subordinate''' &ndash; ''optional'' &ndash; the page name of ''one'' of the unit's parent units or subordinate units. Use only one of theses parameters in each instance. The value of this parameter is automatically turned into a wikilink so there's no need to add link markup. It must contain only one unit page name and no ref tags or any other text.
 * '''parent_level''' or '''subordinate_level''' &ndash; ''optional'' &ndash; the level of the parent or subordinate unit given in the 'parent' or 'subordinate' parameter. Don't enter the level of the unit whose page the infobox is on. See below for more details and examples.
-* '''ref''' &ndash; references to sources that support the information entered in the other parameters. This will automatically create a footnoe. You don't need to use ref tags.
+* '''ref''' &ndash; references to sources that support the information entered in the other parameters. This will automatically create a footnote. You don't need to use ref tags.

@@ Line 10: / Line 10: @@
 | parent_level = none
 | relationship_type = Administrative
 }}
 {{Infobox command structure
-| command_start_date = May 1915<ref name="LLTBerks">{{Cite TLLT|http://www.1914-1918.net/berks.htm|The Royal Berkshire Regiment in 1914-1918}}</ref>
+| command_start_date = May 1915
 | command_end_date =
 | parent = 145th Infantry Brigade, UK
 | parent_level = {{BritishBrigade}}
 | relationship_type = Tactical
 }}
@@ Line 36: / Line 38: @@
 | subordinate =
 | subordinate_level =
 }}
 </pre></div>
@@ Line 47: / Line 50: @@
 * '''parent''' or '''subordinate''' &ndash; ''optional'' &ndash; the page name of ''one'' of the unit's parent units or subordinate units. Use only one of theses parameters in each instance. The value of this parameter is automatically turned into a wikilink so there's no need to add link markup. It must contain only one unit page name and no ref tags or any other text.
 * '''parent_level''' or '''subordinate_level''' &ndash; ''optional'' &ndash; the level of the parent or subordinate unit given in the 'parent' or 'subordinate' parameter. Don't enter the level of the unit whose page the infobox is on. See below for more details and examples.
@@ Line 55: / Line 59: @@
 * '''Administrative''' means relationships that were only administrative and had no tactical or operational role. eg the relationship between a British infantry battalion and its parent regiment, or between a British regiment and its record office.
 * '''Tactical''' means relationships that were mostly tactical with little or no administrative role. eg the relationship between a British battalion and its parent brigade, or a British brigade and its parent division.
-* '''Tactical and Administrative''' means relationships that combined most or all tactical and administrative functions. This is mainly used for the continental system in which tactical and administrative hierarchies were unified up to division level. eg the relationship between an American infantry battalion and its parent regiment, or between an American regiment and its parent brigade. There might be a few cases where this type applies to relationships in the British Army, but these are rare because levels the lower levels of sub-units are mostly not represented by unit pages on this site.
+* '''Tactical and Administrative''' means relationships that combined most or all tactical and administrative functions. This is mainly used for the continental system in which tactical and administrative hierarchies were unified up to division level. eg the relationship between an American infantry battalion and its parent regiment, or between an American regiment and its parent brigade. There might be a few cases where this type applies to relationships in the British Army, but these are rare because the lower levels of sub-units are mostly not represented by unit pages on this site.
 * '''Affiliation''' means a less formal relationship that didn't involve tactical command or administrative records. Affiliated units might share a name or badge with a parent regiment but were otherwise separate. This type of relationship can sometimes be international, for example, some Canadian militia units were affiliated with British regiments.

@@ Line 55: / Line 55: @@
 * '''Administrative''' means relationships that were only administrative and had no tactical or operational role. eg the relationship between a British infantry battalion and its parent regiment, or between a British regiment and its record office.
 * '''Tactical''' means relationships that were mostly tactical with little or no administrative role. eg the relationship between a British battalion and its parent brigade, or a British brigade and its parent division.
-* '''Tactical and Administrative''' refers to the continental system in which tactical and administrative hierarchies were unified up to division level. eg the relationship between an American infantry battalion and its parent regiment, or between an American regiment and its parent brigade. You might also find "Both" used to refer to this kind of relationship on this site, but this needs to be replaced with the more explicit "Tactical and Administrative".
+* '''Tactical and Administrative''' means relationships that combined most or all tactical and administrative functions. This is mainly used for the continental system in which tactical and administrative hierarchies were unified up to division level. eg the relationship between an American infantry battalion and its parent regiment, or between an American regiment and its parent brigade. There might be a few cases where this type applies to relationships in the British Army, but these are rare because levels the lower levels of sub-units are mostly not represented by unit pages on this site.
-* '''Affiliation''' means a less formal relationship that didn't involve tactical command or administrative records. Affiliated units might share a name or badge with a parent regiment but were otherwise separate. This type is new and has not yet been used on any pages.
+* '''Affiliation''' means a less formal relationship that didn't involve tactical command or administrative records. Affiliated units might share a name or badge with a parent regiment but were otherwise separate. This type of relationship can sometimes be international, for example, some Canadian militia units were affiliated with British regiments.
 ==== Levels ====

@@ Line 5: / Line 5: @@
 {{Infobox command structure
 | command_start_date = 1/4/1908
 | parent = Royal Berkshire Regiment, UK
-| parent_level =
+| parent_level = none
 | relationship_type = Administrative
 }}
 {{Infobox command structure
-| name = 1/4th Battalion Royal Berkshire Regiment, UK
+| command_start_date = May 1915<ref name="LLTBerks">{{Cite TLLT|http://www.1914-1918.net/berks.htm|The Royal Berkshire Regiment in 1914-1918}}</ref>
-| command_start_date = May 1915
+| command_end_date =
-| parent = 145th Infantry Brigade, UK<ref name="LLTBerks">[http://www.1914-1918.net/berks.htm The Long, Long Trail The Royal Berkshire Regiment page]</ref>
+| parent = 145th Infantry Brigade, UK
-| parent_level = Brigade
+| parent_level = {{BritishBrigade}}
 | relationship_type = Tactical
 }}
@@ Line 33: / Line 29: @@
 <div style="width:350px;background:#dddddd;border: 1px solid black;padding:0.5em  1em 0.5em 1em"><pre>
 {{Infobox command structure
 | command_start_date =
 | command_end_date =
@@ Line 44: / Line 39: @@
 </pre></div>
-'''Note''': When using parameters, avoid the ambiguous abbreviation "N/A", and instead use "unknown" or "none". All subjective or qualitative judgements and numerical quantities or statistics must be cited to a reliable source (see https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Military_history).
+'''Note''': When using parameters, avoid the ambiguous abbreviation "N/A", and instead use "unknown" or "none". Please cite reliable sources where possible using <nowiki><ref> </nowiki> tags. These should be placed in the date fields after the dates, not in the parent or subordinate fields.
-* '''name''' &ndash; the name of the unit or formation. Defaults to the page name so doesn't need to be entered.
+* '''name''' &ndash; no longer used.
 * '''command_start_date''' &ndash;  the date when this relationship started.
-* '''command_start_date''' &ndash;  the date when this relationship ended.
+* '''command_end_date''' &ndash;  the date when this relationship ended.
-* '''relationship_type''' &ndash; ''optional'' &ndash; the type of relationship. See below for more details and examples.
+* '''relationship_type''' &ndash; the type of relationship. See below for more details and examples.
-* '''parent''' &ndash; ''optional'' &ndash; one of the unit's parent units.
+* '''parent''' or '''subordinate''' &ndash; ''optional'' &ndash; the page name of ''one'' of the unit's parent units or subordinate units. Use only one of theses parameters in each instance. The value of this parameter is automatically turned into a wikilink so there's no need to add link markup. It must contain only one unit page name and no ref tags or any other text.
-* '''parent_level''' &ndash; ''optional'' &ndash; the level of the parent unit. See below for more details and examples.
+* '''parent_level''' or '''subordinate_level''' &ndash; ''optional'' &ndash; the level of the parent or subordinate unit given in the 'parent' or 'subordinate' parameter. Don't enter the level of the unit whose page the infobox is on. See below for more details and examples.
-* '''subordinate''' &ndash; ''optional'' &ndash; one of the unit's subordinate units.
 ==== Relationship Types ====
@@ Line 66: / Line 60: @@
 ==== Levels ====
-Levels are only used for relationships that have some tactical role. They do not apply to purely administrative relationships. Level names have not been finalised but will probably follow the continental system:
+Levels are only used for relationships that have some tactical role. They do not apply to purely administrative relationships. For administrative relationships, a value of 'none' can be entered or the field can be left blank. Level names have not been finalised but will probably follow the continental system:
 * Army Group
@@ Line 78: / Line 72: @@
 In this system, the brigades used by British Empire forces were the equivalent of regiment level. There was no eqivalent of the continental brigade in the British system. Currently {{tl|BritishBrigade}} is used as a placeholder where a unit's parent is a British-style brigade.
-You only need to enter the level of the other unit in the relationship (that is, the parent or child of the current unit). The level of the unit whose page the infobox is on isn't normally entered.
+You only need to enter the level of the other unit in the relationship (that is, the parent or child of the current unit). The level of the unit whose page the infobox is on shouldn't be entered.
-<references/>
+[[Category:Infobox templates]]

@@ Line 2: / Line 2: @@
 ==Usage==
 }}
-==== Command structure box ====
+=== Command structure box ===
 {{Infobox command structure
-| name = 1/4th Battalion, Royal Berkshire Regiment, British infantry
+| name = 1/4th Battalion Royal Berkshire Regiment, UK
-| command_start_date = May 1915
+| command_start_date = 1/4/1908
-| parent = 48th (South Midland) Division<ref name="LLTBerks">[http://www.1914-1918.net/berks.htm The Long, Long Trail The Royal Berkshire Regiment page]</ref>
+| parent = Royal Berkshire Regiment, UK
-| parent_level = Division
+| parent_level =
-| relationship_type = Tactical
+| relationship_type = Administrative
 | subordinate =
 | subordinate_level =
@@ Line 15: / Line 15: @@
 {{Infobox command structure
-| name = 1/4th Battalion, Royal Berkshire Regiment, British infantry
+| name = 1/4th Battalion Royal Berkshire Regiment, UK
 | command_start_date = May 1915
-| parent = 145th Brigade<ref name="LLTBerks">[http://www.1914-1918.net/berks.htm The Long, Long Trail The Royal Berkshire Regiment page]</ref>
+| parent = 145th Infantry Brigade, UK<ref name="LLTBerks">[http://www.1914-1918.net/berks.htm The Long, Long Trail The Royal Berkshire Regiment page]</ref>
 | parent_level = Brigade
 | relationship_type = Tactical
@@ Line 24: / Line 24: @@
 }}
-A command structure box may be used to summarise information about an individual military unit's parent and subordinate units; it should generally be used in conjunction with {{tlx|Infobox military unit}}.  Where necessary, multiple boxes may be used to show the unit's command structure during different periods.
 The box should be added using the {{tlx|Infobox command structure}} template, as shown below:
@@ Line 30: / Line 33: @@
 <div style="width:350px;background:#dddddd;border: 1px solid black;padding:0.5em  1em 0.5em 1em"><pre>
 {{Infobox command structure
-| unit_name = (should automatically come from the page title)
+| unit_name = (usually omitted because it defaults to the page title)
 | command_start_date =
 | command_end_date =
 | parent =
 | parent_level =
 | subordinate =
 | subordinate_level =
@@ Line 43: / Line 46: @@
 '''Note''': When using parameters, avoid the ambiguous abbreviation "N/A", and instead use "unknown" or "none". All subjective or qualitative judgements and numerical quantities or statistics must be cited to a reliable source (see https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Military_history).
-* '''name''' &ndash; the name of the unit or formation.
+* '''name''' &ndash; the name of the unit or formation. Defaults to the page name so doesn't need to be entered.
-* '''date''' &ndash; ''optional'' &ndash; the dates during which the given structure was in place.
+* '''command_start_date''' &ndash;  the date when this relationship started.
-* '''parent''' &ndash; ''optional'' &ndash; the unit's parent unit.
+* '''command_start_date''' &ndash;  the date when this relationship ended.
-* '''parent_level''' &ndash; ''optional'' &ndash; the level of the parent unit, e.g. brigade, division, army
+* '''relationship_type''' &ndash; ''optional'' &ndash; the type of relationship. See below for more details and examples.
-* '''relationship_type''' &ndash; ''optional'' &ndash; e.g. administrative, tactical, or both
+* '''parent''' &ndash; ''optional'' &ndash; one of the unit's parent units.
-* '''subordinate''' &ndash; ''optional'' &ndash; the unit's components subordinate units. <includeonly>{{#ifeq:{{{noheader|}}}|yes||
+* '''parent_level''' &ndash; ''optional'' &ndash; the level of the parent unit. See below for more details and examples.
 [[Category:Military auxiliary infobox templates|Command structure]]
-* '''subordinate_level''' &ndash; ''optional'' &ndash; the level of the subordinate unit, e.g. regiment, battalion, company
 }}</includeonly>
 <references/>