લખાણ પર જાઓ

ઢાંચો:Infobox military unit/doc

વિકિપીડિયામાંથી

Military unit infobox

[ફેરફાર કરો]
502nd Parachute Infantry Regiment
502d PIR Coat Of Arms
સક્રિય1942–present
દેશUnited States
શાખાArmy
પ્રકારParachute infantry
આનો ભાગ છે101st Airborne Division
મુખ્યમથકFort Campbell
હૂલામણાં નામો"Five-Oh-Deuce" or "The Deuce"
યુદ્ધ ઘોષStrike
યુદ્ધોWorld War II

War on Terrorism

DecorationsPresidential Unit Citation (5),
Valorous Unit Award (5),
Croix de Guerre
સેનાપતિઓ
નોંધપાત્ર
સેનાપતિઓ
George V. H. Moseley, Jr.,
John H. Michaelis

A military unit infobox may be used to summarize information about an individual military unit or formation, such as a regiment or division..

The infobox should be added using the {{infobox military unit}} template, as shown below:

{{infobox military unit
|unit_name= 
|image=
|caption=
|dates= 
|country= 
|allegiance=
|branch= 
|type= 
|role= 
|size= 
|command_structure=
|garrison=
|garrison_label=
|nickname=
|patron=
|motto=
|colors=
|colors_label=
|march=
|mascot=
|equipment=
|equipment_label=
|battles=
|anniversaries=
|decorations=
|battle_honours=
|battle_honours_label=
|disbanded=
|flying_hours=
|website=
<!-- Commanders -->
|commander1=
|commander1_label=
|commander2=
|commander2_label=
|commander3=
|commander3_label=
|commander4=
|commander4_label=
|notable_commanders=
<!-- Insignia -->
|identification_symbol=
|identification_symbol_label=
|identification_symbol_2=
|identification_symbol_2_label=
|identification_symbol_3=
|identification_symbol_3_label=
|identification_symbol_4=
|identification_symbol_4_label=
<!-- Aircraft -->
|aircraft_attack=
|aircraft_bomber=
|aircraft_electronic=
|aircraft_fighter=
|aircraft_helicopter=
|aircraft_helicopter_attack=
|aircraft_helicopter_cargo=
|aircraft_helicopter_multirole=
|aircraft_helicopter_observation=
|aircraft_helicopter_transport=
|aircraft_helicopter_trainer=
|aircraft_helicopter_utility=
|aircraft_interceptor=
|aircraft_patrol=
|aircraft_recon=
|aircraft_trainer=
|aircraft_transport=
|aircraft_tanker=
}}

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 WP:MILMOS#CITE).

  • unit_name the formal name of the unit.
  • image optional an image of the unit insignia (cap badges, tartan or colours), if available; other images may be used if this cannot be obtained. The image must be given in the form [[File:Example.jpg|300px]]; in particular, the thumb attribute must not be selected.
  • caption optional the text to be placed below the image.
  • dates the period (usually in years) when the unit was active; alternately, the dates may be indicated by using one—or both—of the separate start_date and end_date parameters.
  • country optional if the unit is part of the armed forces of a sovereign state, the name of that state.
  • allegiance optional used to indicate the allegiance of units which are not part of the regular armed forces of a sovereign state; can usually be omitted otherwise. In the case of National Guard or Naval Militia units, the State of origin should be indicated.
  • branch optional the service branch, in militaries that have them; typically army, navy, air force, etc.
  • type optional the general type of unit, e.g., cavalry, infantry, artillery, etc. More specific types (airborne infantry, light cavalry, etc.) may be given as appropriate.
  • role optional typical strategic or tactical use of unit, e.g., shock troop, special operations, mechanized infantry, ceremonial guard, etc.
  • size optional the size of the unit; this may include both average and lifetime figures, and should indicate equipment (planes, tanks, cannon, etc.) where applicable. For U.S. units, this should only include Organic elements, not Assigned or Attached elements.
  • command_structure optional the larger unit(s) of which the unit is a part. This should not be used to provide an exhaustive history of the unit, which is more appropriate in the article itself, for units existing over a long period. For complicated cases, using the auxiliary command structure box may be appropriate.
  • garrison optional location of the unit's home base; this is generally applicable only to units in existence.
  • garrison_label optional the label to use for the garrison field (above).
  • nickname optional any commonly-used nicknames for the unit.
  • patron optional the patron the unit was named after; this is only applicable in armed forces where units are named after individuals.
  • motto optional the official unit motto (with translation, if necessary).
  • colors optional the unit colors; this may refer to either the actual colors used on the uniform, or to the colours of the unit.
  • colors_label optional the label to use for the colors field (above).
  • march optional the tune(s) commonly or officially played when the unit ceremonially marches; there may be several.
  • mascot optional any official or unofficial animal or character maintained by the unit.
  • equipment optional for units strongly associated with specific equipment or vehicles, such as tanks, artillery, or aircraft, a brief list of the notable types used by the unit; if the number of entries is large, it is recommended that this field not be used, and that the full list be given in the article text instead.
  • equipment_label optional the label to use for the equipment field (above).
  • battles optional any notable engagements in which the unit participated. The decision of what constitutes a notable engagement is left to the editors of the specific article.
  • battles_label optional the label to use for the battles field (above); this defaults to "Engagements" if left blank.
  • anniversaries optional any anniversaries that a unit celebrates.
  • decorations optional any decorations (such as the Presidential Unit Citation) that the unit as a whole has received.
  • battle_honours optional for units in countries that award some type of formal battle honours, the battle honours that the unit has received; while this may have some overlap with the battles field above, the two are not necessarily equivalent.
  • battle_honours_label optional the label to use for the battle_honours field (above); this defaults to "Battle honours" if left blank.
  • disbanded optional for units that have been disbanded, the dates and any other relevant notes regarding the disbanding.
  • flying_hours optional if the formation is an aerial one, the total hours flown.
  • website optional the official website of the formation, if any.

Commander parameters:

The infobox allows for up to three current commanders to be specified; the exact roles or titles of these individuals should be specified via the corresponding label parameters.

  • commander1 optional a current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
  • commander1_label optional the label to use for the field above; for historical reasons, this defaults to "Current commander" if left blank.
  • commander2 optional a second current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
  • commander2_label optional the label to use for the field above; for historical reasons, this defaults to "Ceremonial chief" if left blank.
  • commander3 optional a third current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
  • commander3_label optional the label to use for the field above; for historical reasons, this defaults to "Colonel of the Regiment" if left blank.
  • commander4 optional a fourth current commander of the unit; this can be the acting commander, the ceremonial commander, the chief of staff, or any other leader.
  • commander4_label optional the label to use for the field above; for historical reasons, this defaults to "Command Sergeant Major" if left blank.
  • notable_commanders optional any notable former commanders of the unit; judgement of notability is left to individual article editors.

Insignia parameters:

  • identification_symbol optional the unit's identification symbol (such as a patch, tartan, or tactical identification flash).
  • identification_symbol_label optional the label to use for the identification symbol field (above).
  • identification_symbol_2 optional another identification symbol.
  • identification_symbol_2_label optional the label to use for the second identification symbol field (above).
  • identification_symbol_3 optional another identification symbol.
  • identification_symbol_3_label optional the label to use for the third identification symbol field (above).
  • identification_symbol_4 optional another identification symbol.
  • identification_symbol_4_label optional the label to use for the fourth identification symbol field (above).

Aircraft parameters:

  • aircraft_attack optional for aviation units, the attack aircraft flown by the unit.
  • aircraft_bomber optional for aviation units, the bomber aircraft flown by the unit.
  • aircraft_electronic optional for aviation units, the electronic warfare aircraft flown by the unit.
  • aircraft_fighter optional for aviation units, the fighter aircraft flown by the unit.
  • aircraft_helicopter optional for aviation units, the helicopter aircraft flown by the unit.
  • aircraft_helicopter_attack optional for aviation units, the attack helicopter aircraft flown by the unit.
  • aircraft_helicopter_cargo optional for aviation units, the cargo helicopter aircraft flown by the unit.
  • aircraft_helicopter_multirole optional for aviation units, the multirole helicopter aircraft flown by the unit.
  • aircraft_helicopter_observation optional for aviation units, the observation helicopter aircraft flown by the unit.
  • aircraft_helicopter_trainer optional for aviation units, the trainer helicopter aircraft flown by the unit.
  • aircraft_helicopter_utility optional for aviation units, the utility helicopter aircraft flown by the unit.
  • aircraft_interceptor optional for aviation units, the interceptor aircraft flown by the unit.
  • aircraft_patrol optional for aviation units, the patrol aircraft flown by the unit.
  • aircraft_recon optional for aviation units, the reconnaissance aircraft flown by the unit.
  • aircraft_trainer optional for aviation units, the trainer aircraft flown by the unit.
  • aircraft_transport optional for aviation units, the transport aircraft flown by the unit.
  • aircraft_tanker optional for aviation units, the aerial refueling aircraft flown by the unit.

Note that the various xyz_label fields above are intended for overriding the default labels on these fields as needed for particular countries or services; in most cases, however, the default value is sufficient, and the fields need not be included.

Command structure box

[ફેરફાર કરો]


A command structure box may be used to summarize information about an individual military unit's parent and subordinate units; it should generally be used in conjunction with {{infobox military unit}}. If needed, multiple boxes may be used to show the unit's command structure during different periods.

The box should be added using the {{command structure}} template, as shown below:

{{command structure
|name= 
|date=
|parent=
|subordinate=
}}

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 WP:MILMOS#CITE).

  • name the name of the unit or formation.
  • date optional the dates during which the given structure was in place.
  • parent optional the unit's parent unit.
  • subordinate optional the unit's subordinate units.

Service record box

[ફેરફાર કરો]


Combat service
Part of 7. Unterseebootsflottille (1938–41)
Identification codes M 18 837 (feldpost)
Commanders Günther Prien (1938–41)
Operations 10 patrols
Victories 30 ships (162,769 GRT) sunk,
1 warship (29,150 tons) sunk,
8 ships (62,751 GRT) damaged

A service record box may be used to summarize information about an individual military unit's or ship's service history; it should generally be used in conjunction with the appropriate primary infobox. If needed, multiple boxes may be used to separate the service record for different periods; for example, a unit that fought in several wars may have separate boxes for each.

The box should be added using the {{service record}} template, as shown below:

{{service record
|is_ship=
|is_multi=
|label= 
|partof=
|codes=
|commanders=
|operations=
|victories=
|awards=
}}

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 WP:MILMOS#CITE).

  • is_ship optional "yes" if the box is being used inside a compound ship infobox.
  • is_multi optional "yes" if multiple instances of the box are being used inside a single compound ship infobox.
  • label optional the label to use for the box; this defaults to "Service record" if left blank.
  • partof optional the unit or formation of which the subject unit or ship was a part; multiple units may be listed with the corresponding dates.
  • codes optional the identification codes carried by the unit or ship; these should generally be labeled according to what the code indicates.
  • commanders optional the notable commanding officers for the period covered.
  • operations optional the operations (such as battles, wars, campaigns, patrols, cruises, etc.) in which the subject unit or ship participated; these may be given as a list, or described in a more condensed form.
  • victories optional the victories or successes in the subject's service history. For units, this may be battles won; for submarines or merchant raiders, the ships and tonnage sunk; and so forth.
  • awards optional the awards, decorations, or other honors received by the subject unit or ship.

The HTML mark-up produced by this template includes an hCard microformat that makes an organization's details readily parsable by computer programs. This aids tasks such as the cataloguing of articles and maintenance of databases. For more information about the use of microformats on Wikipedia, please visit the Microformat WikiProject.

Subtemplates

Please do not remove instances of these subtemplates.

Classes used

The HTML classes this microformat uses include:

  • adr
  • agent
  • category
  • country-name
  • extended-address
  • fn
  • geo
  • label
  • latitude
  • locality
  • longitude
  • nickname
  • note
  • org
  • region
  • street-address
  • url
  • vcard
Please do not rename or remove these classes
nor collapse nested elements which use them.