02_browsing:02_layers
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revisionNext revision | |||
— | 02_browsing:02_layers [2020/01/06 16:59] – simone | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== 2.2 Layers of information ====== | ||
+ | WhatsApp messages are built up in a hierarchy: a chat contains messages that contain tokens that contain characters. A corpus of WhatsApp chats should allow for all these layers to be queried. Additionally, | ||
+ | These layers can nicely be seen when browsing results from a query: | ||
+ | {{ : | ||
+ | |||
+ | ===== Chats ===== | ||
+ | |||
+ | In this example, you find the chat back as an ID (chat138) at the top in pink. If you want to see the whole chat, you see two options at the very bottom: chat in context (faster) or the whole chat (can be slow). When you click on the little <i> in the top bar, you can also see meta data about the chat, such as the number of speakers, languages, total messages etc. | ||
+ | |||
+ | ===== Messages ===== | ||
+ | |||
+ | In this pink chat, you see three selected messages in blue: | ||
+ | * Message 165379: Anke adesso se vuoi | ||
+ | * Message 165380: Aeh ho solo 10 percento di batteria xo | ||
+ | * Message 165381: Ah ecco | ||
+ | |||
+ | As you can see, these messages have meta data assigned to them, as well, e.g. the message ID and the speaker (these pieces of information are always available) as well as information provided by the informant such as age, mothertongue etc. | ||
+ | |||
+ | ===== Tokens ===== | ||
+ | The individual tokens are annoted in green in the above example and they are aligned to the message, to which they belong. | ||
+ | |||
+ | Tokens, too, (can) have annotations that are assigned to them. In the example shown above, you have the following meta data that was created by our team or by our computational linguists: | ||
+ | * Gloss: a normalization, | ||
+ | * tt_pos: A part-of-speech annotation generated with the parser [[https:// | ||
+ | * tt_lem: The lemma for each token as it was created by TreeTagger. | ||
+ | |||
+ | The red token //di//, by the way, is the one that we queried for to create this screen shot. | ||
+ | |||
+ | ===== Labels ===== | ||
+ | On all three layers, i.e. for chats, messages and tokens, as well as for all the meta data, you see the labels, e.g. msg_id, gloss, home_postcode etc. These labels are used for queries. | ||
+ | |||
+ | Examples: | ||
+ | * If you want to see the whole message 165380, your query would be // | ||
+ | * If you want to find verbs in the present tense, your query is // | ||
+ | |||
+ | To see the query-labels for the chat as well as all the labels available in a specific sub-corpus, check the information for the [[02_browsing: |
02_browsing/02_layers.txt · Last modified: 2022/06/27 09:21 by 127.0.0.1