02_browsing:05_additional:02_export
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
02_browsing:06_export [2019/12/04 09:46] – simone | 02_browsing:05_additional:02_export [2020/04/22 12:32] – simone | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Export ====== | + | ====== |
- | After performing a query, you can click on "More" | + | After performing a query, you can click on '' |
{{ : | {{ : | ||
- | Figure 1: Export | + | Figure 1: Different exporters and additional |
- | Next to the type of export, you have the option "Left and right context", | ||
- | The other options, " | ||
- | Once you click " | + | ===== WekaExporter ===== |
+ | This exporter is very specific for the data mining application [[https:// | ||
- | Exports are very hungry in resources, thus, it might take a while to create an export or the server might even hang. The simpler your query, the less problems | + | ===== CSVExporter ===== |
+ | This exporter creates one line per result. In this line, you see the text you queried for as well as all the annotations available on the token level. Depending on the sub-corpus, these are the token itself as well as [[01_corpus:02_preprocessing:06_pos|PoS]] annotations. | ||
+ | ===== TokenExporter ===== | ||
+ | This exporter is intended for smaller corpora than ours. Using our (sub-)corpora it often hangs even at very small queries. We recommend not to use it. | ||
- | ===== WekaExporter | + | ===== GridExporter |
- | This exporter is very specific for the data mining application [[https:// | + | This exporter is the most versatile one, since you can choose the annotations that you want to export. Figure 2 shows an example in which one token to the left and one to the right are exported as well as the whole message, the message ID, the token queried |
- | ===== CSVExporter ===== | + | {{ :02_browsing:gridexporter.png? |
- | This exporter creates one line per result. In this line, you see the text you queried for as well as all the annotations available on the token level. Depending on the sub-corpus, these are the token itself as well as [[01_corpus:04_annotations:02_pos|PoS]] annotations. | + | Figure 2: Example of a GridExport |
- | The field " | + | The resulting output starts as follows: |
- | Under " | + | {{ :02_browsing: |
+ | Figure 3: Results | ||
- | ===== TokenExporter | + | As you can see in Figure 3, each result is preceded by a number starting with 0. You then see all the annotation keys selected in Figure 2 in the selected order: whole message, message ID, token (your query is in the center, in this case //demain// plus the left and right token that you selected with the left and right context), age_range and then the chat ID selected with '' |
- | This exporter is intended | + | |
+ | If you leave the field " | ||
+ | |||
+ | ===== Simple text exporter | ||
+ | This exporter | ||
+ | |||
+ | ===== Additional options ===== | ||
+ | Next to the type of export, you have the option “Left and right context”, which is the same for all export formats. Here, you can define the number of entities to be exported to the left or right of your search query. The entity is in the same unit as your query, i.e. if you query for tokens, you can select the number of tokens | ||
+ | |||
+ | The other options, " | ||
+ | |||
+ | Under “Parameters”, | ||
+ | |||
+ | Once you click '' | ||
+ | |||
+ | |||
+ | |||
+ | Exports are very hungry in resources, thus, it might take a while to create an export or the server might even hang. The simpler your query, the less problems you have. **Hint**: instead of formulating a complex [[02_browsing: | ||
+ | |||
+ | |||
- | ===== GridExporter ===== | ||
- | This exporter offers the most options. | ||
02_browsing/05_additional/02_export.txt · Last modified: 2022/06/27 09:21 by 127.0.0.1