Template:ISO 4217/cite

Template documentation follows
Note: the template above may sometimes be partially or fully invisible.
Visit "Template:ISO 4217/cite/doc" to edit its documentation if it is available. (How does this work?)

Template {{ISO 4217/cite}} allows the sources for the ISO 4217 Standard to be referenced. The Standard is published by SIX Group.

Usage

Hello currency world.{{ISO 4217/cite|source=List One, List Three}} →

Quote

— Source

Base is the SIX Group website, which has four source files (available for download). {{ISO 4217/cite}} allows listing them as a reference footnoote, or in a biography bulleted list.

Within this template, each source is a single, complete {{Cite web}} citation. They can be used as <ref>{{ISO 4217/cite/List One}}</ref>.

Example List One example: {{ISO 4217/cite/List One}} →

Quote

— Source

Cite source

The Standard is maintained and published by SIX Group. Sources are from their source site."List One: Currency, fund and precious metal codes" (XLS). www.six-group.com. SIX Group. 2022-09-23.

The full Standard consists of four lists, named List One (active currencies), List Two (special funds), List Three (obsolete currencies), and Amendments (for example, announcements). The lists are downloadable documents (XLS, doc). They are published at the SIX Group website.

Parameters

{{ISO 4217
|source = 
|access-date=
|name   =
|prefix =
|format =
}}

• |source= (required; A=a)

|source=List One, List Two, List Three, Amendments, all, SIX Group

Synonyms: see table

For example for List One: |source=List One, list one, One, one, 1, L1, l1

• |access-date=

|access-date=2022-10-25 →

Quote

— Source

• |name=, |format=

|name=ISOsource-XXX → {{ISO 4217/cite|source=Two|name=ISOsource-XXX}} can be called by {{ISO 4217/cite/name|name=ISOsource-XXX}} (<ref name="ISOsource-XXX">)

|prefix=Introducing text, or blank (default: ISO 4217 Standard definition:)

{{ISO 4217/cite|source=List Two|format=plain}} →

|format=plain (no <ref>-tag)

• |prefix=

|prefix=Introducing text, or blank (default: ISO 4217 Standard definition:)

{{ISO 4217/cite|source=List Two|format=plain}} →

Examples

Define and call by |name=ISOsource-XXX

Define:{{ISO 4217/cite|source=List Two|name=ISOsource-XXX}} → Define.

Since the name is set, |name=ISOsource-XXX, we can reuse the ref:

Call by name.{{ISO 4217/cite/name|name=ISOsource-XXX}} → Call by name.

Options

Options used.{{ISO 4217/cite |source=List Three |format=plain |prefix=Introducing text |access-date=2022-10-25 }} → Options used.Introducing text

• "List Three: Codes for historic denominations of currencies and funds" (XLS). www.six-group.com. SIX Group. 2018-08-22. Retrieved 2022-10-25.

Defaults.{{ISO 4217/cite|source=List Three}} → Defaults.

Options used.{{ISO 4217/cite |source=List Three |format=plain |prefix=Introducing text |access-date=2022-10-25 }} → Options used.Introducing text

• "List Three: Codes for historic denominations of currencies and funds" (XLS). www.six-group.com. SIX Group. 2018-08-22. Retrieved 2022-10-25.

Updates

after sep 22 2022

• amendment 174: HRK added to EUR List one. (1-1-2023)

Using {{ISO 4217/cite}}

Through {{ISO 4217/cite}}, the sources can be listed, as plain {{Cite web}} bulletlist or as <ref>{{Cite web}}</ref>.

{{ISO 4217/cite
|source=<!-- |source=One, Three|; A=a; some list is expected. -->
<!-- |source=List One, One, 1, List Two, two, 2, List Three, three, 3, List Four, four, 4, All, SIX, six group, 0, 1, 2, 3, 4 -->
|prefix=<!-- optional; can be =<blank>; default is "ISO 4217 Standard definition:" -->
|format=plain<!-- optional, plain={{Cite web}} bulletlist; default=list in a <ref> footnote -->
|name=<!-- default: <ref name="ISO 4217">; can be called by {{ISO 4217/cite/name}} -->
}}

Sources for the ISO 4217 Standard
Website SIX Group
	"Data Standards, ISO 4217 - Currency Code Maintenance: Get the Correct Currency Code". www.six-group.com. SIX Group. 2022-10-01.
	{{ISO 4217/cite/SIX Group}}
	|source=SIX, SIX Group, six, 0
List One
	"List One: Currency, fund and precious metal codes" (XLS). www.six-group.com. SIX Group. 2022-09-23.
	{{ISO 4217/cite/List One}}
	|source=List One, one, 1
List Two
	"List Two: Fund codes registered with the Maintenance Agency" (XLS). www.six-group.com. SIX Group. 2018-08-29.
	{{ISO 4217/cite/List Two}}
	|source=List Two, two, 2
List Three
	"List Three: Codes for historic denominations of currencies and funds" (XLS). www.six-group.com. SIX Group. 2018-08-22.
	{{ISO 4217/cite/List Three}}
	|source=List Three, three, 3
Amendments
	"Overview Amendments" (XLSX). www.six-group.com. SIX Group. 2022-09-23.
	{{ISO 4217/cite/Amendments}}
	|source=Amendments, four, 4
	|source=All will list |source=One, Two, Three, Four

Note: the Amendments are not separately available. See the website.

Latest: #173 (Sierra Leone; TURKEY to TÜRKİYE = List-1, TRY)

"Amendment 173" (PDF). SIX Group. 2022-09-23. Retrieved 2022-10-17.

Subtemplates

• {{ISO 4217/cite/format}}

{{ISO 4217/cite/SIX Group}}

{{ISO 4217/cite/List One}}

{{ISO 4217/cite/List Two}}

{{ISO 4217/cite/List Three}}

{{ISO 4217/cite/Amendments}}

Data Analysis

anomalities in sp

bolívar/bolivar, (e.c.u), Pa’anga, TÜRKİYE/türki̇ye/Turkish (<span class="nowrap">'"`UNIQ--templatestyles-0000004E-QINU`"'<span class="monospaced">U+0130</span>&#x20;</span><span style="font-size:125%;line-height:1em">&#x0130;</span> '"`UNIQ--templatestyles-00000050-QINU`"'<span class="unichar-name">&lt;reserved-0130></span>)

DATA ANALYSIS

• KEY= code, List, entity, end-date, (not

  startdate, num)

1. What does number say?
2. xls: data in extra column
3. Minor-unit="0, NA, -blank-" varies wotout difference ; 0=trivial,
4. ZWD, VEF in L3: double, with different withdr-date & no start date = inconclusive overlap.
5. uc/lc inconsistent:

BOP	Peso boliviano
USN	US Dollar (Next day)
USN	US Dollar [next day]
USS	US Dollar (Same day)

1. non-en letters Åland, (turkey),
2. abbr or without dots (pref: with); UAE vs E.C.U ??)
3. country name not in curry name

BDT	Taka	BANGLADESH
BWP	Pula	BOTSWANA
BOV	Mvdol	BOLIVIA (PLURINATIONAL STATE OF)
MWK	Kwacha	MALAWI!
AOA	Kwanza	ANGOLA!
BUK	Kyat	BURMA !!
MMK	Kyat	MYANMAR!!
ILP	Pound	ISRAEL
! (well, unq because not PSterling..)
ECS	Sucre	ECUADOR
XSU	Sucre	SISTEMA UNITARIO DE COMPENSACION REGIONAL DE PAGOS "SUCRE"

1. name change L1-L3

ZWD	Zimbabwe Dollar
ZWD	Zimbabwe Dollar (old)

1. yes or no genitive?

Maldive Rupee
Mozambique Escudo

1. anomalities in sp

bolívar/bolivar, (e.c.u), Pa’anga, TÜRKİYE/türki̇ye/Turkish (<span class="nowrap">'"`UNIQ--templatestyles-00000053-QINU`"'<span class="monospaced">U+0130</span>&#x20;</span><span style="font-size:125%;line-height:1em">&#x0130;</span> '"`UNIQ--templatestyles-00000055-QINU`"'<span class="unichar-name">&lt;reserved-0130></span>)

SLE, SLL both in list one, same (Q4587) !

VED, VES both in list one, same (Q203757) !

Data summary

• rows: 281 + 9 + 162 = 452

rows with code: 278 + 9 + 162 = 449 (excl Antarctica, ...)

• unq code (id-a): 182 + 0 + 124 = 304
• code both act and obs: 10. In 21 rows; ANG 3x. Also MINOR-UNIT: 2/blank all.

• countries: unq "country" name: 292 (after some equalising = entity2: ~281 unq)

Anomalies

• "Funds" in List 2: 9

In list 1 marked: 8 (column F=hidden?!)

• Missing in col F: USN/Next Day
• List Three has 9 funds
• "THE CONGO"
• "Türkiye" or "Türkİye" A163? U+0130 İ <reserved-0130>

todo

β-templates /code

|format=no name, or add a ref-name

when plain, no label; at least |prefix=_blank_ = show blank prefix.

ref: preview refname

"change param from name into refname

in Wikidata

Currency

(P489) (P9059) (P5061) (P1552) (P17) (P562) (P176)

• (Q61200261) (Q858338)

cryptocurrency

• {{Infobox currency/overview/crypto}} ([edit]). 167 QIDs (8 Oct 2022).

{{Infobox cryptocurrency}} (edit talk history links # /subpages /doc /doc edit /sbox /sbox diff /test) TPU

(Q13479982) (P5810), (Q48893562) (=blockchain fork)

Articles switched from IB currency to IB cryptocurrency: Primecoin, Coinye, Nxt. 17:44, 8 October 2022

ISO 4217

• (Q37431) (P498)

References

These references will appear in the article, but this list appears only on this page.

See also

• IBAN using currency code:

"List of Currency Codes by Country (ISO 4217)". www.iban.com.

Template:ISO 4217 invokes Module:Navbox using Lua.

Usage

This template can be used to make a standard navigation box. It is intended for use within another template that standardises the title and contents of the box (see Template:ShipNavbox). This template SHOULD NOT be used directly within articles, as it creates a maintenance burden to do so whenever the contents of the box have to be updated.

The purpose of this template is to standardise the attributes of all navigation boxes, for example, their colours and other CSS attributes. The template is fairly simple, and could be extended to add other features in the future. Using this template allows changes to be implemented much quicker and easier than editing each template separately.

Syntax

{{navbox
|state      = uncollapsed, collapsed, plain, autocollapse (default)
|name       = mandatory - name of the template
|style      = optional - style for the whole table
|title      = mandatory - navbox header
|gtitleN    = optional - title of N-th group of items
|styleN     = optional - style for groupN; i.e. text-align
|groupN     = mandatory - list of groups of items
|fstyle     = optional - style for footer ; i.e. text-align
|footer     = optional - navbox footer
}}

• Groups: Currently there is no technical limit to the maximum number of groups.
  • Groups of items can be added as parameters: group1, group2, group3, ... up to groupN.
• Group title: Each group has its own title parameter: gtitle1, gtitle2, gtitle3, ... up to gtitleN. Note that the default width for the first column is 15%.
• Group style: Style may also be customised to each group in: style1, style2, style3, ... up to styleN.
  • Note that neither the title nor the items have any wiki-links built into the template. As a result, users of the template are free to use wiki-links as they wish.
• Line breaks: Line-breaks (<br />) are unnecessary, as text wrapping is done automatically by the template. This also includes links and text in gtitleN and groupN.
• Bullets: Create unordered lists with lines beginning with *.
• Pipe links: Because of the nature of template syntax, it may be necessary to use Template:! ({{!}}).

States

• Autocollapse: By default, the state of a navbox is "autocollapsed". This means that if the number of navboxes in a page exceeds the maximum allocation of the collapsible navboxes, then the remaining navboxes are collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
  • Currently, the autocollapse allocation is 2 (see MediaWiki:Common.js). This means that if there are 3 navboxes in a page, the third and subsequent navboxes will be collapsed automatically.
• Uncollapsed: Forces the navbox to be displayed.
  • All of the navboxes in this documentation are in the uncollapsed state.
• Collapsed: The reverse of uncollapsed. Forces the navbox to be hidden instead.
  • Navboxes with a height of more than 300 pixels will also be collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
• Plain: Removes the "show/hide" link.

Sub-groups

• For larger navboxes, it may be necessary to include sub-groups within a particular group of items. It is also possible to collapsible navboxes within the parent navbox, see Collapsible sub-groups.
• To create sub-groups within {{navbox}}, certain parameters are to be included:
  • The parent navbox group (i.e. group2 in the example below) requires the type parameter (gtype2 = Subgroup).
  • The nested navbox (sub-group) requires the inclusion of the sub-group parameter (subgroup = yes). This enables the template to differentiate between the sub-group and the parent navbox.

{{navbox
|name    =
|title   =
|gtitle1 =
|group1  =
|gtitle2 =  
|gtype2  = Subgroup (mandatory)
|group2  = 
  {{navbox
  |subgroup = yes (mandatory)
  |gtitle1  = 
  |group1   =
  |gtitle2  = 
  |group2   = 
  }}
}}

Collapsible sub-groups

• For extremely long navboxes, it is recommended to use collapsible navboxes within the parent navbox. Further sub-groups can then be added to these collapsible navboxes.
• To create collapsible sub-groups within {{navbox}}, these parameters need to be included:
  • The parent navbox is almost always uncollapsed (state=uncollapsed).
  • The parent navbox group (i.e. group1 in the example below) requires the type parameter (gtype1 = Subgroup).
  • The nested collapsible navbox requires the inclusion of the collapsible parameter (collapsible = yes). This enables the template to differentiate between the collapsible navbox and the parent navbox.
  • The nested collapsible navbox is forcefully collapsed (state=collapsed).

{{navbox
|state  = uncollapsed
|name   = 
|gtype1 = Subgroup
|group1 = 
  {{navbox
  |collapsible = yes
  |state   = collapsed
  |title   = 
  |gtitle1 = 
  |group1  = 
  |gtitle2 = 
  |group2  = 
  }}
}}

Use of images

• The use of images in navboxes is permitted, but please resize the images to keep them small. Inventory-sized images (25-30 pixels) are recommended.
• Please use {{t|plink}} to create links with images. Use {{t|plink}} for any case where text is not desired after the link. It functions the same as {{t|plink}}, but it does not produce a wikilink in text. Use {{t|chatl}} to link chatheads. These templates create links for both the image and text (except for {{t|plink}}) using far less wikicode than the standard syntax.

Link and file share the same name

{{plink|Item}}

File name differs from the link

{{plink|Item|File}}

Link and file share the same name, but different text is desired to display

{{plink|Item|alt=Text}}

File name differs from the link and different text is desired to display

{{plink|Item|File|alt=Text}}

Categorising

Navboxes are very useful for transcluding categories onto a large number of pages that share both a trait and the navigation box. For example: Template:ShipNavbox transcludes Category:Ships onto every page that uses it.

There are 2 methods of categorising pages with navboxes:

The first way is with {{t|Ctg}}. This is the preferred method, and can be used in most cases. The rules and operations for the Category handler template are very simple; however, they are enough to produce the desired results on most pages.

Categorisation should only be used on a template for large-scale addition. It is unhelpful, for example, to use a rule that only applies to 1 page.

Examples

To see the following navboxes in action, see Template:Navbox.

Single line navbox with centered list

{{navbox
|name    = 
|title   = 
|style1  = text-align:center
|group1  =
}}

Navbox with standard footer

{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|footer  = Centered footer
}}

Navbox with styled footer

{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|fstyle  = text-align:right
|footer  = Right-aligned footer
}}

Multiple line navbox

{{navbox
|name    = 
|title   = 
|gtitle1 = Group title 1
|group1  = 
|gtitle2 = Group title 2
|group2  = 
|gtitle3 = Group title 3
|group3  = 
}}

Collapsed navbox

{{navbox
|state   = collapsed
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox with Tnavbar

{{navbox
|state   = plain
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox without Tnavbar

{{navbox
|state   = plain
|title   = 
|style1  = text-align:center
|group1  = 
}}

Complicated navbox

{{navbox
|state   = uncollapsed
|name    = 
|title   = 
|gtitle1 = Level 1 Title 1
|group1  = 
|gtitle2 = Level 1 Title 2
|group2  = 
|gtitle3 = Level 1 Title 3
|group3  = 
|gtitle4 = Level 1 Title 4
|group4  = 
|gtitle5 = Level 1 Title 5
|gtype5  = Subgroup
|group5  = 
  {{navbox
  |subgroup = Yes
  |gtitle1  = Level 2 Title 1
  |group1   =
  |gtitle2  = Level 2 Title 2
  |group2   =
  |gtitle3  = Level 2 Title 3
  |gtype3   = Subgroup
  |group3   = 
    {{navbox
    |subgroup = Yes
    |gtitle1  = Level 3 Title 1
    |group1   =
    |gtitle2  = Level 3 Title 2
    |group2   =
    }}
  |gtitle4  = Level 2 Title 4
  |group4   = 
  }}
|gtitle6 = Level 1 Title 6
|group6  = 
|gtitle7 = Level 1 Title 7
|group7  = 
|fstyle  = 
|footer  = 
}}

Preventing unwanted documentation

The Navbox template's documentation is automatically transcluded under the navbox on any Template namespace page. It is not transcluded when used as a sub-group or collapsible sub-group template (subgroup= yes or collapsible=yes).

Should the documentation appear when it is unwanted, it can be hidden by setting the doc parameter doc=no on the template. In most cases, the doc parameter is NOT used and the parameter is removed completely.