User Tools

Site Tools


01_corpus:02_preprocessing:05_technical_messages

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
01_corpus:03_preprocessing:05_technical_messages [2020/04/16 12:50] simone01_corpus:02_preprocessing:05_technical_messages [2022/06/27 09:21] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== 1.3.5 Technical messages ====== +====== 1.2.5 Technical messages ====== 
-WhatsApp sometimes generates messages when something happens in a chat. If, for example, a user leaves a group, the message can be //Peter left// or //Peter hat die Gruppe verlassen// In order to get one wording for these messages, we encoded them, e.g. //actionQuserOUT//.+WhatsApp sometimes generates messages when something happens in a chat. If, for example, a user leaves a group, the message can be //Peter left// or //Peter hat die Gruppe verlassen// In order to get one wording for these messages, we encoded them, e.g. ''actionQuserOUT''.
  
 This results in the following values for the field //msg_type//: This results in the following values for the field //msg_type//:
-  * actionQiconDELthe avatar was deleted +  * ''actionQiconDEL'' the avatar was deleted 
-  * actionQiconUPDthe avatar was changed +  * ''actionQiconUPD'' the avatar was changed 
-  * actionQsubjUPDthe name of a group was updated +  * ''actionQsubjUPD'' the name of a group was updated 
-  * actionQuerINa speaker was added to a group +  * ''actionQuerIN'' a speaker was added to a group 
-  * actionQuserOUTa speaker was removed or removed themselves +  * ''actionQuserOUT'' a speaker was removed or removed themselves 
-  * actionQuserREMMeta text about a speaker in a group chat+  * ''actionQuserREM'' Meta text about a speaker in a group chat
  
 Other options in the field //msg_type// are: Other options in the field //msg_type// are:
  
-  * contentA message with text written by a communication partner +  * '' content'' A message with text written by a communication partner 
-  * encryptedA message that was encrypted  +  * '' encrypted'' A message that was encrypted  
-  * mediaA message that contained a media file such as a sound file, an image or a video +  * '' media'' A message that contained a media file such as a sound file, an image or a video 
-  * no consentA message written by a communication partner who did not give [[01_corpus:03_preprocessing:02_without_permission|permission]] for his texts to be used.+  * '' no consent'' A message written by a communication partner who did not give [[01_corpus:02_preprocessing:02_without_permission|permission]] for his texts to be used.
  
-Some of these cases also re+Since most of these technical messages do not contain any text, they are also marked in the field //tok// as follows:
  
-The following codes exist in the corpus in the field "tok": 
  
-  * mediaQremovedfor media that we removed +  * '' mediaQremoved'' for media that we removed 
-  * emptyQmsgan empty message +  * '' emptyQmsg'' an empty message 
-  * encryptedQmsgsome informants encrypted their messages +  * '' encryptedQmsg'' some informants encrypted their messages 
-  * systemQspk53says very generallythat speaker 53 did something, e.g. changed the title, joined the group etc.+  * '' systemQspk53'' says very generally that speaker 53 did something from the first bullet list above, e.g. leave a group. 
  
-If you want more information about what speaker 53 did in the above example, you have to query the field , which knows the following options: 
  
  
01_corpus/02_preprocessing/05_technical_messages.1587034245.txt.gz · Last modified: 2022/06/27 09:21 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki