Difference between revisions of "App/taxon name"
(added common diacritic marks) |
(→Diacritic marks) |
||
Line 19: | Line 19: | ||
Common diacritic marks that one may copy and paste in Content include: | Common diacritic marks that one may copy and paste in Content include: | ||
− | Á á à Â â ã å ä Ç ç É é è ê ë í î ï ñ Ó ô õ Ö ö Š š Ú ú û Ü ü ý | + | Á á à Â â ã å ä Ç ç Č č É é è ê ë ę ë ğ í î ï ĭ ñ ň Ó ô õ Ö ö ŕ Ş ş Š š ţ Ú ú û Ü ü ū ý ž ż |
Revision as of 15:14, 10 March 2011
Contents |
Taxonomic names in mx
The taxonomic hierarchy is maintained independently of the OTU list. You need not use the hierarchy at all. OTUs may be tied to taxonomic names. Multiple OTUs can have the same taxonomic name, within, and between projects.
Visibility
The taxonomic tree is shared through projects. The names you see in a current project can be set (and changed) at any time by following the visibility link from more options. Including the highest level you wish to see names from. When you return to the main tab the list will be populated with the current taxa in that node. You can add multiple names, and will see children from all of them. Internally nested names within the visibility (e.g. selecting Ichneumonoidea when Hymenoptera is already chosen) have no effect, they are ignored.
Permissions
Permissions to edit the tree are granted by an administrator. They can be set for any node (level), and all the children of that node. To gain permissions to edit or update contact an administrator.
Type information
Type related information should be provided in the form of specimen records. This permits many (e.g. syntype series or paratypes + holotype) records for one taxonomic name. You will need to create a specimen record, and tie it to a collecting event, then make that specimen a type of a given name.
Diacritic marks
Common diacritic marks that one may copy and paste in Content include:
Á á à Â â ã å ä Ç ç Č č É é è ê ë ę ë ğ í î ï ĭ ñ ň Ó ô õ Ö ö ŕ Ş ş Š š ţ Ú ú û Ü ü ū ý ž ż