Differences

This shows you the differences between two versions of the page.

--- 02_browsing:04_queries:01_support [2020/04/22 11:11] – simone
+++ 02_browsing:04_queries:01_support [2022/06/27 09:21] (current) – external edit 127.0.0.1
@@ Line 10: / Line 10: @@
 Figure 1: Starting the query builder
-It comes in two flavors, as you can see. You can use the "General (TigerSearch like) function, which is a bit more demanding or you can use the "Word sequences and meta information" function. To switch between these two functions, just press the arrow down.
+It comes in two flavors, as you can see. You can use the "General (TigerSearch like)" function, which is a bit more demanding or you can use the "Word sequences and meta information" function. To switch between these two functions, just press the arrow down.
 Let us first look at the "Word sequences and meta information" function. This function helps you build queries per (sub-)corpus, so when you first open it, all sections have a button "initialize". When you press this button, the tool looks for available fields and options for the (sub-)corpus that you have selected at that moment. When you switch corpora, you have to re-initialize the tool by closing its tab and starting it anew.
 The tool is set up into different sections, which we will discuss in more detail in the following.
-tok="ora" & tt_pos="NOM" & tok="siamo"
-& age_range = "18-24"
-& #1_=_#2
-& #2 . #3
-& #4_i_#1
-& #4_i_#3
 ==== Linguistic sequence ====
@@ Line 30: / Line 25: @@
   - The second token has to follow the first one directly, i.e. with no other tokens in between.
-As you can see in figure 2, properties that apply to the same token are listed below each other (01 and 02 in figure 2), while sequences of tokens are listed in a horizontal line (01 and 03 in figure 2). In order to add more attributes to a specific token, you press the ''+'' below the token (04 in figure 2). If you want to add another token to the query, press the button ''Add'' to the right of the last token  (05 in figure 2).
+As you can see in Figure 2, properties that apply to the same token are listed below each other (01 and 02 in Figure 2), while sequences of tokens are listed in a horizontal line (01 and 03 in Figure 2). In order to add more attributes to a specific token, you press the ''+'' below the token (04 in Figure 2). If you want to add another token to the query, press the button ''Add'' to the right of the last token  (05 in Figure 2).
 {{ :02_browsing:04_queries:queryexample1.png?600 |}}
-Figure 2: The query "was (part of speech: PRELS) me" built with word sequence builder.
+Figure 2: The query "//ora// (part of speech: //NOM//) followed by //siamo//" built up with the Word sequence Builder.
-To have the option of defining the sequence of words in more detail. This option is represented by the rectangle 06 in figure 2 and explained in more detail in figure 3, where ''.2'' stands for a token that is preceding another one with one token in between, ''.1,2'' represents a token that is directly preceding or with one token in between, ''.*'' represents a token that is indirectly preceding, this with any number of tokens in between and ''.'' represents a token that is directly preceding.
+The option of defining the sequence of words in more detail is represented by the rectangle 06 in Figure 2 and explained in more detail in Figure 3, where ''.2'' stands for a token that is preceding another one with one token in between, ''.1,2'' represents a token that is directly preceding or with one token in between, ''.*'' represents a token that is indirectly preceding, this with any number of tokens in between, and ''.'' represents a token that is directly preceding.
 {{ :02_browsing:04_queries:queryexample2.png?600 |}}
@@ Line 41: / Line 36: @@
 ==== Scope and Meta information ====
-In the section below the //Linguistic sequence// (part 07 in figure 2) you can add additional options to your query that pertain to the whole message or the whole chat as listed in section [[02_browsing:04_queries:05_fields|2.4.5 Fields available]].
+In the section below the //Linguistic sequence// (part 07 in Figure 2) you can add additional options to your query that pertain to the whole message or the whole chat as listed in section [[02_browsing:04_queries:05_fields|2.4.5 Fields available]].
 ==== Toolbar ====
-When clicking ''Create AQL Query'' in the section //Toolbar//, your query is created (number 08 in figure 2). Additional functions in this section are ''Clear the Query Builder'', which is used if you want to start anew with your query and ''Refresh Query Builder'', which you have to click if you decide to select another sub-corpus for your query.
+When clicking ''Create AQL Query'' in the section //Toolbar//, your query is created (number 08 in Figure 2). Additional functions in this section are ''Clear the Query Builder'', which is used if you want to start anew with your query and ''Refresh Query Builder'', which you have to click if you decide to select another sub-corpus for your query.
 ===== Query Builder. General (TigerSearch like) =====
-This type of query builder focuses on relationships between entities. It basically works as follows: you select an entity (ie. the value of the token) and then select another entity (eg. the part of speech that this tokens is to have) and then link the two via a relationship. Figure 5 shows how this example is constructed.
+This type of query builder focuses on relationships between entities. It basically works as follows: you select an entity (ie. the value of the token) and then select another entity (eg. the part of speech that this tokens is to have) and then link the two via a relationship. Figure 4 shows how this example works.
 {{ :02_browsing:04_queries:queryexample4.png?600 |}}
-Figure 5: Building a query by selecting a relationship between entities
+Figure 4: Building a query by selecting a relationship between entities
-To work with this query builder, you first select all the nodes ("Add node") required for your query (i.e. the value of the token and the PoS in the example). You then add an edge, i.e. a relationship between these two entities (e.g. different types of precedence, inclusion, overlap etc.) and dock the selected entity to the other one.
-**NB: you cannot have isolated identities, they all have to be linked via edges**.
+To work with this query builder, you first select all the nodes (''Add node'' in Figure 4) required for your query (i.e. the value of the token and the PoS in the example). You then add an edge, i.e. a relationship between these two entities by clicking on the button ''Edge'' on one of your tokens. All other tokens that you have added now show a button ''Dock'', which you can click to create an relationship between these two tokens. As can be seen inFigure 4, ten different relationships can be created.