17,519
edits
Main Page: Difference between revisions
→Q & A
(→Q & A) |
|||
| Line 37: | Line 37: | ||
: For example, the [[Item:Q22|brown ciliate]] is reported as a Parduczia sp. based on sequence analysis, but the sequences from that study are published under an environmental "ciliate metagenome" identifier on NCBI. | : For example, the [[Item:Q22|brown ciliate]] is reported as a Parduczia sp. based on sequence analysis, but the sequences from that study are published under an environmental "ciliate metagenome" identifier on NCBI. | ||
: Therefore, the item "brown ciliate" is modeled here as a provisional taxon, because it does not have an exact equivalent in the NCBI Taxonomy. | : Therefore, the item "brown ciliate" is modeled here as a provisional taxon, because it does not have an exact equivalent in the NCBI Taxonomy. | ||
: For [[Item:Q301| | : For [[Item:Q301|Bacteroidales sp. Cc3-010 ectosymbiont of Caduceia versatilis]], an SSU rRNA sequence has been published. The property [[Property:P28|P28]] is used to link to a representative sequence for disambiguation. | ||
; Why do some interacts with statements link to "unknown value"? | |||
: If a symbiont is reported only on the basis of microscopy, without any information on its phylogenetic affiliation, "unknown value" is used for the object of the statement. | |||
: If some information is known about its likely taxonomy, e.g. through use of group-specific FISH probes, then a placeholder taxon is created with a temporary name. | |||
: The entry [[Item:Q441|''Metopus contortus'']] has both an "unknown value" statement and a placeholder symbiont taxon [[Item:Q442|Q442]]. | |||
; Why host this on Wikibase? | ; Why host this on Wikibase? | ||
: This database has seen a number of iterations: starting as a table in a word processor file, to spreadsheets, a custom SQLite database, and an attempt to homebrew a structured data base with XML files and Python scripts. After getting some experience on Wikidata, I found that Wikibase offers the key features that I wanted: flexible and extensible schemata, graphical frontend for manual data entry, options for programmatic data import from tables, integration with external databases, and a sophisticated query interface. | : This database has seen a number of iterations: starting as a table in a word processor file, to spreadsheets, a custom SQLite database, and an attempt to homebrew a structured data base with XML files and Python scripts. After getting some experience on Wikidata, I found that Wikibase offers the key features that I wanted: flexible and extensible schemata, graphical frontend for manual data entry, options for programmatic data import from tables, integration with external databases, and a sophisticated query interface. | ||