Difference between revisions of "App/otu"
From mx Help Wiki
m |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | + | Data in mx are primarily tied to OTUs, which in turn are linked into a taxonomic names hierarchy. The names are individually used in different contexts (e.g. in public a manuscript name won't be shown, in matrices the matrix name will be used if provided, etc.). In mx these names are often displayed together and can be identified by their colour: | |
| − | + | black name (comes from the link to a taxon name) | |
| + | <span style="color:blue;">blue name </span> (comes from the OTU 'name' field) | ||
| + | <span style="color:green;">green name </span> (comes from the OTU 'matrix name' field) | ||
| + | <span style="color:red;">red name </span> (comes from the OTU 'manuscript name' field) | ||
| − | + | This system allows you to create OTUs in the absence of a taxonomic name hierarchy if needed, and it allows any naming convention to be used (e.g. lab codes, etc.). Some general guidelines/considerations are useful in practice: | |
| + | |||
| + | # If you a) have a taxonomic name hierarchy and b) want to represent a 1:1 match of concept to name then simply select the appropriate taxonomic name and do not provide a OTU name | ||
| + | # If you don't have a 1:1 match, or want to include multiple concepts for a given name identify your OTUs to the finest level within the taxonomic hierarchy by choosing a the closest taxon name, then repeat the working name as an OTU name (e.g. your name might look like this ''Aus <span style="color:blue;">Aus sp23</span>'' | ||
| + | # While it is not necessary to tie an OTU to the taxonomic hierarchy you can benefit from doing so as some data (e.g. content) are organized by this hierarchy | ||
== OTU Application help == | == OTU Application help == | ||
{{Special:Prefixindex/App/otu/}} | {{Special:Prefixindex/App/otu/}} | ||
Revision as of 13:51, 22 February 2011
Data in mx are primarily tied to OTUs, which in turn are linked into a taxonomic names hierarchy. The names are individually used in different contexts (e.g. in public a manuscript name won't be shown, in matrices the matrix name will be used if provided, etc.). In mx these names are often displayed together and can be identified by their colour:
black name (comes from the link to a taxon name) blue name (comes from the OTU 'name' field) green name (comes from the OTU 'matrix name' field) red name (comes from the OTU 'manuscript name' field)
This system allows you to create OTUs in the absence of a taxonomic name hierarchy if needed, and it allows any naming convention to be used (e.g. lab codes, etc.). Some general guidelines/considerations are useful in practice:
- If you a) have a taxonomic name hierarchy and b) want to represent a 1:1 match of concept to name then simply select the appropriate taxonomic name and do not provide a OTU name
- If you don't have a 1:1 match, or want to include multiple concepts for a given name identify your OTUs to the finest level within the taxonomic hierarchy by choosing a the closest taxon name, then repeat the working name as an OTU name (e.g. your name might look like this Aus Aus sp23
- While it is not necessary to tie an OTU to the taxonomic hierarchy you can benefit from doing so as some data (e.g. content) are organized by this hierarchy
OTU Application help
| App/otu/edit | App/otu/edit page | App/otu/index |
| App/otu/new | App/otu/show | App/otu/show codings |
| App/otu/show compare content | App/otu/show content | App/otu/show material |
| App/otu/show matrix sync |
