Lesson 11: Editing relations with the network-editor

The network editor

It is possible to establish a relationship between objects in the evolving semantic network through the "link" function. However you would loose the surveillance over the entire structure of the network. To solve this problem, ATLAS/ti provides a graphical network-editor (NWE) that helps you to graphically shape the entire semantic network. You open the NWE by simply clicking the network icon in the button bar of the particular special list-window. This will open a new window in which the currently active object (for example the code "job-sharing") is presented as a graphical object. In case that the object was already linked to other objects they are displayed as well in the NWE. Because numerous quotations are in many cases linked to particular codes, the quotation-objects are not being displayed (but they may optionally be included ) when opening a focusing network.

A line that behaves like a rubber band characterizes the relationship between the various objects represented within the NWE: as soon as you move an object on the surface, the line expands respectively. This will allow you to align the objects according to your preference and visual logic without endangering your comprehension of the relationship that objects have to each other.

You may usually want to use the NWE to establish or to outline relationships of the presented objects to additional objects. The first step to accomplish this is to import additional objects by way of a simple drag&drop operation: the object, say the code "Cooperation" is selected in the respective list and dragged and then dropped (by releasing the mouse button) into the network-editor while initially keeping the left mouse button pressed. You can alternatively select the "import neighbors" option from the menu or context-menu. As a result all linked objects are being imported provided that they have not already existed in the NWE. Codes containing a large number of objects may also cause the inconvenience of quickly having hundreds of quotation-objects displayed inside the window. Therefore the application provides two safety-features: firstly the Node-menu (but not the context-menu of the objects) contains an "undo import neighbors" function that allows you to undo the last import-process. Secondly you can take immediate precautions against importing the wrong objects. To do so, you hold down the key when choosing the function. As a result importing of quotations is suppressed in the case of code-objects and ONLY quotations are imported (useful for hyperlink-networks) in the case of quotation-objects.

Each object in the NWE has its own context-menu corresponding to its object-type and may be opened by right-clicking the object. You may then carry out actions such as importing of additional neighbor-objects, removing the object from the network-sight, deleting the object from the HU, opening an additional focused network-sight around the desired object. With code-objects you can also have a list with linked quotations displayed from which you may select a quotation that is immediately being displayed in the context of the PD-window.

Creating a relationship

You can also establish the relationship between one object and another by way of drag&drop. For this purpose the first object is activated with a right mouse click followed by holding down the key and the left mouse button while the mouse is dragged over the second object. A "rubber band" now spans between the two of the objects. An option-menu is opened with code-to-code or quotation-to-quotation relationships from which you may select the type of relationship to be established between both of the objects (you can define relationships with a nomenclature and different properties for these both types of relationships. Only unnamed relationships may be established with other objects.). A number of such relationships are already pre-defined however you may also define your own (see below for more information on the relationship-editor).

The major point of interest with asymmetric and transitive relationships is to know which one of the two objects to be linked is the origination and what object is the target of the unidirectional relationship. All these processes are completely intuitive within the NWE: To create a relationship "a is element of b" you initially select a and then b meaning to initially select the element and then the whole. However the process of establishing relationships via the context-menu of the code-list is inverse which one the one hand may require accustoming but on the other side was intended. This is because it does make sense to initially activate the whole and then to select the elements to be assigned from the code-list (for example in a "is a" or an "is part of" relationship) when working with the context-menu. This process is inverted within the NWE: You may for example mark a large number of objects and link them to another object in one stroke (don't work with multiple objects at the same time). Thus you always choose the elements first and then the whole.

ATTENTION: All operations that are carried out within the NWE have in fact an impact on the HU. Whenever new codes are created or objects are deleted it is therefore not an entirely graphical operation but a differently visualized logical operation within the HU. Only the "Remove from view" function solely has a meaning at the graphical level. If you intend to close the NWE you are prompted whether to save the network-view. Please note that this action does not intend to save changes resulting of the graphical editing of the network of the relationship-structure that objects have to each other. Saving the HU as a whole exclusively facilitates this. You are rather given the opportunity to save the particularly displayed section of the semantic network existing within the HU including the laboriously created layouts. Therefore if you intend to work with the particular network-view without starting to import various objects from scratch and without restoring the effective visual alignment you should answer the prompt to save with "yes". However you can do without saving if your sole purpose is to edit the logical references of objects to each other with a graphical user-interface.

The NWE offers a multitude of features that cannot be explained in further detail. However a floating toolbar providing the most essential edit-functions and that may be aligned over- and next to the NEW, is to be emphasized.

The relationship-editor

Although a number of common code-to-code relationships are pre-defined within ATLAS/ti you have the possibility, as previously mentioned, to define your own additional relationships during your analytical work. This is facilitated in two ways:

  1. As above mentioned, you may select the "user defined relation" option instead of the pre-defined relationship-patterns offered while at the process of linking two code-objects. In that case you are prompted to specify the internal name (only used to administer the relation within the HU), a symbol for visual outlining within the NWE, menu-text, thickness of the connection-line as well as the logical state of the relationship (either transitive, asymmetric or symmetric).
  2. A second more comfortable approach is to select the "relation-editor" option from the "Links" menu. This will pop up a window with a comprehensive set of configuration-options for code-to-code relationships where you may set the parameters that are being named as with the first option. Moreover you may define even more settings such as the color and the type of connection-line as well as the how to display the default-direction of relationships within the NWE (for example to sort "element of" relationships from the bottom to the top). You may furthermore enter a comment-text here. It is important to know whether changes are generally valid for all HU's on the same computer or only locally for the HU being edited when changing or creating new relationships. You need to know that ATLAS/ti follows an object-oriented logic and so properties of a particular HU are initially inherited from the default-settings of the application. As a result, any changes made to the HU only have an impact on the HU. This works similar with relations: (also when defining search swarms in the text-search): changes to code-to-code relations or hyperlink-relations are initially stored within the HU only and are tightly linked to them. If the HU is re-located to another computer also the properties of the relations are transferred. Other HU's may inherit those changed properties provided that two conditions are given: 1.) If the HU with those new or altered relationships is currently opened when founding an additional HU, the new HU inherits the modifications as well as the ATLAS/ti default-standards from the other HU. 2.) if you save the modified relations explicitly to the standard-relationships file "default.rel" for code-to-code relationships or to "hyph.rel" for hyperlinks (or to "srchbib.skt" for ???) and thus changing the ATLAS/ti standard on the particular computer. To continue working on another computer with equally modified standards you must either copy the appropriate standard-files (from the ATLAS/ti application-directory) or overwrite the standard-files on the other machine with the modified relations from the HU.