Difference between revisions of "App/otu"

From mx Help Wiki
Jump to: navigation, search
m
m
 
(3 intermediate revisions by one user not shown)
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:
 
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:
  
Line 10: Line 9:
  
 
# 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 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>''
+
# 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. Your name might then 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
 
# 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
 +
# While anything is permitted names should ''not'' typically formed like '''''Aus'' <span style="color:blue;">bus</span>''' bur rather like this: '''''Aus'' <span style="color:blue;">Aus bus</span>''', i.e. include the redundancy in the OTU name. Remember you are not reading the name across from left to right, you're reading up to 4 different names concatenated for display purposes.  Components of that concatenation are shown individually in their respective places.
 +
# In collaborative labs it's useful to fill in the Sensu/concept field so as to keep OTUs distinguishable by something other than IDs
 +
# Consider making ample use of OTU groups as you create OTUs
 +
  
 
== OTU Application help ==
 
== OTU Application help ==
  
 
{{Special:Prefixindex/App/otu/}}
 
{{Special:Prefixindex/App/otu/}}

Latest revision as of 16:46, 26 April 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:

  1. 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
  2. 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. Your name might then look like this: Aus Aus sp23.
  3. 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
  4. While anything is permitted names should not typically formed like Aus bus bur rather like this: Aus Aus bus, i.e. include the redundancy in the OTU name. Remember you are not reading the name across from left to right, you're reading up to 4 different names concatenated for display purposes. Components of that concatenation are shown individually in their respective places.
  5. In collaborative labs it's useful to fill in the Sensu/concept field so as to keep OTUs distinguishable by something other than IDs
  6. Consider making ample use of OTU groups as you create OTUs


[edit] 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