Difference between revisions of "App/otu"

From mx Help Wiki
Jump to: navigation, search
Line 1: Line 1:
 
OTUs are the core objects in the database. They represent taxonomic concepts of any level or rank. Most other objects are attached or referenced through an OTU.
 
OTUs are the core objects in the database. They represent taxonomic concepts of any level or rank. Most other objects are attached or referenced through an OTU.
 
== Edit ==
 
 
=== Published names vs. Containing taxon ===
 
 
You can tie your OTU to a published taxonomic name by selecting a taxon name via the blue picker at the top when you edit that OTU. If your OTU represents that taxon name that’s all you need to do. If your OTU is a child of that taxon name you can click the “Is child of published name?” check box. Note that we recently merged the functionality of is/is child to a single dropdown.
 
 
=== Manuscript Names ===
 
 
Do not place manuscript names in the name field. If you are describing a new species in an currently available genus you should enter the genus name and “new species” in name, field and the full species epithet in the manuscript name field. OTU names are/will be routinely displayed for public use in some cases, and thus it is very important to not include manuscript names in that field.
 
 
== List ==
 
  
 
By default all the OTUs for the current project are listed. In most cases you will not want to see this list, but rather a grouped-list. You can create as many OTU groups as you want in the Groups + Templates tab. When there select a group as a default and when you return to the OTU tab you’ll only see those group members. At present the OTU default group is reset every time you enter a project.
 
By default all the OTUs for the current project are listed. In most cases you will not want to see this list, but rather a grouped-list. You can create as many OTU groups as you want in the Groups + Templates tab. When there select a group as a default and when you return to the OTU tab you’ll only see those group members. At present the OTU default group is reset every time you enter a project.
Line 18: Line 6:
  
 
<b>Taxon Name <span style="color: blue;">Otu Name</span> <span style="color: red;">Manuscript Name</span>  <span style="color: green;">Matrix Name </span> <span style="color: silver;">(Containing Taxon name)</span></b>
 
<b>Taxon Name <span style="color: blue;">Otu Name</span> <span style="color: red;">Manuscript Name</span>  <span style="color: green;">Matrix Name </span> <span style="color: silver;">(Containing Taxon name)</span></b>
 
== Show options ==
 
 
When you Show an OTU numerous options are available on the left.
 
 
=== content ===
 
See [[App/content]].
 
  
 
== OTU Application help ==
 
== OTU Application help ==
  
 
{{Special:Prefixindex/App/otu/}}
 
{{Special:Prefixindex/App/otu/}}

Revision as of 11:27, 15 October 2009

OTUs are the core objects in the database. They represent taxonomic concepts of any level or rank. Most other objects are attached or referenced through an OTU.

By default all the OTUs for the current project are listed. In most cases you will not want to see this list, but rather a grouped-list. You can create as many OTU groups as you want in the Groups + Templates tab. When there select a group as a default and when you return to the OTU tab you’ll only see those group members. At present the OTU default group is reset every time you enter a project.

There are various possible names for OTUs. These are color-coded in the list as follows:

Taxon Name Otu Name Manuscript Name Matrix Name (Containing Taxon name)

OTU Application help

App/otu/editApp/otu/edit pageApp/otu/index
App/otu/newApp/otu/showApp/otu/show codings
App/otu/show compare contentApp/otu/show contentApp/otu/show material
App/otu/show matrix sync
Personal tools