Difference between revisions of "Data dictionary"
From mx Help Wiki
m |
|||
| (2 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
== Tables == | == Tables == | ||
| + | * '''associations''' - user definable linkages between OTUs, e.g. host/parasite, can be linearly chained and tied to supporting data | ||
* '''chr''' - characters (phylogentic) | * '''chr''' - characters (phylogentic) | ||
* '''ces''' - collecting events | * '''ces''' - collecting events | ||
* '''claves''' - dichotomous keys | * '''claves''' - dichotomous keys | ||
* '''codings''' - the content of matrix cells (many codings can be present in one cell) | * '''codings''' - the content of matrix cells (many codings can be present in one cell) | ||
| − | |||
* '''contents''' - text blocks of a given content type | * '''contents''' - text blocks of a given content type | ||
* '''content_types''' - user defined "headings" for text content | * '''content_types''' - user defined "headings" for text content | ||
* '''confidences''' - definable confidence "levels", used for various data types, e.g. codings | * '''confidences''' - definable confidence "levels", used for various data types, e.g. codings | ||
* '''content_templates''' - Containers for content_types, used to customize ordering and groups of content_types. These are the layout of OTU pages. | * '''content_templates''' - Containers for content_types, used to customize ordering and groups of content_types. These are the layout of OTU pages. | ||
| − | |||
* '''datasets''' - files of any type, for specific filetypes functions may be available (e.g. Nexus files can be translated to the database) | * '''datasets''' - files of any type, for specific filetypes functions may be available (e.g. Nexus files can be translated to the database) | ||
* '''figures''' - ties an image and an optional caption to any data in mx | * '''figures''' - ties an image and an optional caption to any data in mx | ||
| Line 22: | Line 19: | ||
* '''mxes_plus_otus''' - individual otus that will be included in a given matrix | * '''mxes_plus_otus''' - individual otus that will be included in a given matrix | ||
* '''namespaces''' - a domain (string) for which all identifiers (strings) must be unique | * '''namespaces''' - a domain (string) for which all identifiers (strings) must be unique | ||
| + | * '''OTU''' - "operational taxonomic unity", most data in mx are tied to OTUs, then through this to taxon names | ||
* '''projs''' - projects | * '''projs''' - projects | ||
| − | |||
* '''tags''' - ties a keyword and some optional caption to any data in mx | * '''tags''' - ties a keyword and some optional caption to any data in mx | ||
| + | * '''taxon_hists''' - taxonomic histories, records usage of a taxon name in some combination | ||
| + | * '''taxon_names''' - ''available'' taxon names, as governed- things like "Aus spp." or "Aus nr. bus" belong in OTUs. | ||
Latest revision as of 10:29, 25 January 2011
[edit] Tables
- associations - user definable linkages between OTUs, e.g. host/parasite, can be linearly chained and tied to supporting data
- chr - characters (phylogentic)
- ces - collecting events
- claves - dichotomous keys
- codings - the content of matrix cells (many codings can be present in one cell)
- contents - text blocks of a given content type
- content_types - user defined "headings" for text content
- confidences - definable confidence "levels", used for various data types, e.g. codings
- content_templates - Containers for content_types, used to customize ordering and groups of content_types. These are the layout of OTU pages.
- datasets - files of any type, for specific filetypes functions may be available (e.g. Nexus files can be translated to the database)
- figures - ties an image and an optional caption to any data in mx
- keywords - a customizable controlled vocabulary applied to data via tags
- lots - records referencing more than one specimen
- mxes - matrices
- mxes_minus_chrs - individual characters that will be excluded from a given matrix
- mxes_minus_otus - individual otus that will be excluded from a given matrix
- mxes_plus_otus - individual otus that will be included in a given matrix
- namespaces - a domain (string) for which all identifiers (strings) must be unique
- OTU - "operational taxonomic unity", most data in mx are tied to OTUs, then through this to taxon names
- projs - projects
- tags - ties a keyword and some optional caption to any data in mx
- taxon_hists - taxonomic histories, records usage of a taxon name in some combination
- taxon_names - available taxon names, as governed- things like "Aus spp." or "Aus nr. bus" belong in OTUs.
