Difference between revisions of "Guide/Ontology"

From mx Help Wiki
Jump to: navigation, search
m
m
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
One of the strengths of databasing is the possibility to cross-reference. In our project we have the potential to take advantage of this by accessing the Hymenoptera Ontology Project. Whenever you are viewing a character description ('''Fig. 11''') you can click <span class="hll">markup description</span> in the menu to the left and MX will highlight all words in the description with a corresponding entry in the ontology. The highlights are links, each of which will take you to a definition on a public webpage also powered by MX ('''Fig. 13'''). Furthermore, there is a private part which is
+
[[Guide | Guide home]]
available to all users of the chalcid project ('''Fig. 14'''). Just click <span class="hll">Change projects</span> at the top right of a page and choose <span class="hll">Hymenoptera Ontology</span>. There is no need to log out first, and you can even access both projects and have multiple windows open simultaneously. <br/><br/>
+
  
The first view presents you with a choice of what to do. Typically you will want to either <span class="hll">list all the terms</span> ('''Fig. 14'''), <span class="hll">search for term</span> through the blue box, <span class="hll">add a new term</span> ('''Fig. 15 & 16''') or <span class="hll">edit</span> an existing definition. All these procedures are pretty straightforward and all you really need to know is that when creating a new term you are not required to enter <span class="hll">highest taxon name to which this term applies</span> ('''Fig. 16''') although we would recommend it. A term can also have a number of relationships such as the terminal button being part_of the antenna. If we would later decide on another name for terminal button this can be indicated by it being a synonym_of, ''e.g.'', reduced apical flagellomere.
+
One of the strengths of databasing is the possibility to cross-reference. In our project we have the potential to take advantage of this by accessing the Hymenoptera Ontology Project. Whenever you are viewing a character description ('''Fig. 11''') you can click <span class="hll">markup description</span> in the menu to the left and MX will highlight all words in the description with a corresponding entry in the ontology. The highlights are links, each of which will take you to a definition on a public webpage also powered by MX ('''Fig. 13'''). Furthermore, there is a private part which is available to all users of the chalcid project ('''Fig. 14'''). Just click <span class="hll">Change projects</span> at the top right of a page and choose <span class="hll">Hymenoptera Ontology</span>. There is no need to log out first, and you can even access both projects and have multiple windows open simultaneously. <br/><br/>
 +
 
 +
The first view presents you with a choice of what to do. Typically you will want to either <span class="hll">list all the terms</span> ('''Fig. 14'''), <span class="hll">search for term</span> through the blue box, <span class="hll">add a new term</span> ('''Fig. 15 & 16''') or <span class="hll">edit</span> an existing definition. All these procedures are pretty straightforward and all you really need to know is that when creating a new term you are not required to enter <span class="hll">highest taxon name to which this term applies</span> ('''Fig. 16''') although we would recommend it. A term can also have a number of relationships such as the terminal button being part_of the antenna. If we would later decide on another name for terminal button this can be indicated by it being a synonym_of, ''e.g.'', reduced apical flagellomere. Or the entry could simply be destroyed.<br/>
 +
 
 +
There is actually an ontology part of the chalcid project too, but everything is set up so that the chalcid
 +
project is accessing the collaborative general ontology rather than the local version which is accessible for our
 +
project only. This way we can make use of the many already entered terms.<br/>
 +
 
 +
[[Image:Guide_fig_11.jpg|frame|none| '''Fig. 11.''' Single character show.]]
 +
 
 +
[[Image:Guide_fig_13.png|frame|none| '''Fig. 13.''' Public ontology.]]
 +
 
 +
[[Image:Guide_fig_14.png|frame|none| '''Fig. 14.''' Listing terms.]]
 +
 
 +
[[Image:Guide_fig_15.jpg|frame|none| '''Fig. 15.''' New term.]]
 +
 
 +
[[Image:Guide_fig_16.png|frame|none| '''Fig. 16.''' Show term.]]

Latest revision as of 02:04, 29 December 2006

Guide home

One of the strengths of databasing is the possibility to cross-reference. In our project we have the potential to take advantage of this by accessing the Hymenoptera Ontology Project. Whenever you are viewing a character description (Fig. 11) you can click markup description in the menu to the left and MX will highlight all words in the description with a corresponding entry in the ontology. The highlights are links, each of which will take you to a definition on a public webpage also powered by MX (Fig. 13). Furthermore, there is a private part which is available to all users of the chalcid project (Fig. 14). Just click Change projects at the top right of a page and choose Hymenoptera Ontology. There is no need to log out first, and you can even access both projects and have multiple windows open simultaneously.

The first view presents you with a choice of what to do. Typically you will want to either list all the terms (Fig. 14), search for term through the blue box, add a new term (Fig. 15 & 16) or edit an existing definition. All these procedures are pretty straightforward and all you really need to know is that when creating a new term you are not required to enter highest taxon name to which this term applies (Fig. 16) although we would recommend it. A term can also have a number of relationships such as the terminal button being part_of the antenna. If we would later decide on another name for terminal button this can be indicated by it being a synonym_of, e.g., reduced apical flagellomere. Or the entry could simply be destroyed.

There is actually an ontology part of the chalcid project too, but everything is set up so that the chalcid project is accessing the collaborative general ontology rather than the local version which is accessible for our project only. This way we can make use of the many already entered terms.

Error creating thumbnail: Unable to save thumbnail to destination
Fig. 11. Single character show.
Error creating thumbnail: Unable to save thumbnail to destination
Fig. 13. Public ontology.
Error creating thumbnail: Unable to save thumbnail to destination
Fig. 14. Listing terms.
Error creating thumbnail: Unable to save thumbnail to destination
Fig. 15. New term.
Error creating thumbnail: Unable to save thumbnail to destination
Fig. 16. Show term.
Personal tools