Vorlage:Switch

A key-like branching, a decision between a single level of alternatives, here especially to choose among alternative available identification tools. The term "Key Switch" was avoided, because identification tools may be simple image field guides, tabular overviews, or even free-form text.

Planned name in German: "Weiche".

Technical Note: The requirements for this template are that both jKey and mobileKey can follow it as if it were a key. For this purpose, both parameter names and the output hmtl layout follow the Key Start and Decision templates.

Parameters

For the entire Switch:

• id (optional, defaults to "switch" if not given)
• title
• remarks
• common names
• parent taxon
• parent key
• parent key text
• (no creator, category, geoscope, audience, edited by etc.!)

For the alternatives of the decision:

• result 1…15
• result text 1…15
• statement 1…15
• remarks 1…15
• image 1…15a, 1…15b

• caption 1…15a, 1…15b
• image 1…15a width, 1…15b width
• image 1…15a height, 1…15b height

• subheading 1…15
• subheading style 1…15

Current architecture

 ├ Switch/Lead
 └ Switch/doc
 + StripFormatting
 + Lead/GalleryItemNoCaption
 + Multilingual

Open questions

1. parent key text → automatically transmit to a category or property?

   Do you mean whether the Parent key should be added as property? Property perhaps yes, but only parent key (i.e. the page referenced), not for parent key text. I am not sure I understand the problem… --Gregor Hagedorn 21:55, 28. Sep. 2010 (CEST)

   I think I suggested this, because this might give a systematic hierarchy that can be displayed later by template: Taxinfo and parent key text is usually the real systematic group. BTW it seems to me that determination keys should be categorised more precisely because with semantic media wiki one should be able to query (sub)keys that are for instance in category Flora. So category Flora is not really necessary in any of the keys but a category for the systematic level. --Andreas Plank 08:47, 29. Sep. 2010 (CEST)

   We could add new fields for systematic categories - but which? Family = Order = Class = ? About parent key: the "parent key" link itself is fairly reliable, but the parent key text can, and especially for entomologist, will be very complicated, e.g. a hierarchical listing of taxon groups like: "Insecta: Coleoptera: Chrysomelidae: Cryptocephalinae". I therefore think that this is not a good method. --Gregor Hagedorn 10:29, 29. Sep. 2010 (CEST)

---