The "Add Attribute" panel is used to add attributes and their values to queries.
(1) Entity to which an attribute is being added. (In the example above, it is the top level of the query. However, it may be any node in the query network.)
(2) The class to which the entity in focus belongs, and to which an additional attribute is about to be added.
(3) These checkboxes tell LegendBurster which attributes to show in drop-down lists. Although LegendBurster can make extensive use of inherited attributes during matching, they are not incorporated into this version of the system, as they require sophisticated understanding of ontology design to be used correctly. Please contact Georeference Online Ltd if you believe you have an application that needs this level of sophistication. During normal operation, only the "Primary Only" checkbox should be checked.
(4) In this drop-down list, selection is made of which attribute is to be added to the query. (Only attributes valid for the selected entity are shown.)
(5) In these drop-down lists the attribute values of interest are selected. Note that if the value extends beyond the width of the display column, the full text of the highlighted value is shown in the form's status bar (just below the Comment field (Item 8 above)). In the diagram above, the word "Ready" appears in this position because the value has already been chosen.
(6) Drop-down lists of "Expected Frequency in the Sought-For Object", for selection opposite the attribute value they qualify. See the legend on the right of the screen (Always = green; Usually = light green; Sometimes = white; Rarely = pink; Never = red). When processing the query, LegendBurster will accord high rewards for MapObjects which match an attribute value with an "always" frequency, a slightly lower score for a "usually" frequency, and no score for a "sometimes" frequency. A negative score will be accorded for attribute values matching a "rarely" expected frequency, and an even higher negative score for a "never" frequency. Scores are calculated for each MapObject, with the highest scorers being the closest matches to the query.
In the default situation, only very small penalties (negative scores) are recorded for attributes that do not match (ie: there is neither conflict nor agreement). By using the "wildcard" value "OTHERS", and giving it a "never" frequency, the presence of unwanted "extra" attribute values can effectively be penalised.
(7) If they were input in the Ontology Editor, descriptions are provided of the entities and attributes in focus, to ensure consistent understanding of terms. Special considerations regarding the "links" between entities and their attributes are also noted when appropriate. (If the description extends beyond the form margin, resting the mouse pointer on the description will cause the complete text to be displayed.)
(8) Space for the entry of comments relevant to the attribute value entered.
(9) Click on the "View Hierarchy" button to see the hierarchical arrangement of all possible attribute values (example shown below), which can be searched by entry of a term of interest in the search field. Double clicking on any value in the hierarchy will transfer that value to the input box. Click on the "Hide Hierarchy" button to remove the hierarchy.
(10) Click on the "Add item" button to complete the insertion of the new attribute value or values.
Proceed to the Net Editor Drop-Down Menu (where the important net-drawing function is described)
Proceed to the Query Net Editor Toolbar or
Proceed to Mapping Results