gsarti commited on
Commit
a12425c
1 Parent(s): 9212672

Added questionnaires data

Browse files
questionnaires/README.md ADDED
@@ -0,0 +1,17 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # QE4PE Questionnaires
2
+
3
+ This folder contains the configurations and results of pre- and post-task questionnaires used in the QE4PE project. Questionnaires were created using the Qualtrics platform. For every questionnaire, the following files are available:
4
+
5
+ - `{{QUESTIONNAIRE_ID}}_config.json`: the configuration file mapping output columns to questions and available options.
6
+
7
+ - `{{QUESTIONNAIRE_ID}}_results.csv`: contains the answers collected from the participants. The file contains preprocessed entries to facilitate further analyses on the results. Answer values are mapped to the original questions and options using the configuration file.
8
+
9
+ ## Pre-task Questionnaire
10
+
11
+ The `pretask` questionnaire was administered to translators **before** the `pretask` to ensure their proficiency with post-editing MT and other computer-assisted translation tools, and collect their opinions regarding post-editing before the task.
12
+
13
+ ## Post-task Questionnaires
14
+
15
+ After the `main` task, translators were asked to complete the `posttask` questionnaire. This questionnaire aimed to collect feedback on the post-editing task, the MT system, the interface and the highlighting.
16
+
17
+ Two versions of the `posttask` questionnaire were used: one named `posttask_highlight` for translator editing highlighted segments in the main task (for `oracle`, `supervised` and `unsupervised` modalities), and one named `posttask_no_highlight` for the `no_highlight` modality. The **only differences** between the two versions are the presence of several questions related to the highlighting feature (`highlight_statement` 1 to 8 in `posttask_highlight_config.json`), which were replaced by a smaller subset of speculative questions (`highlight_statement` 1 to 3 in `posttask_no_highlight_config.json`) for the no-highlight setting, and the formulation of open-ended highlight questions (`highlight_like` and `highlight_dislike` in both configurations).
questionnaires/posttask_highlight_config.json ADDED
@@ -0,0 +1,322 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "time": {
3
+ "title": "Duration (in seconds)"
4
+ },
5
+ "translation_direction": {
6
+ "title": "Translation direction",
7
+ "options": {
8
+ "eng-ita": "English to Italian",
9
+ "eng-nld": "English to Dutch"
10
+ }
11
+ },
12
+ "main_task_modality": {
13
+ "title": "Main task modality",
14
+ "options": {
15
+ "no_highlight": "No Highlight",
16
+ "oracle": "Oracle",
17
+ "supervised": "Supervised",
18
+ "unsupervised": "Unsupervised"
19
+ }
20
+ },
21
+ "pretask_translator_id": {
22
+ "title": "Pretask translator ID",
23
+ "options": {
24
+ "t1": "Translator 1",
25
+ "t2": "Translator 2",
26
+ "t3": "Translator 3",
27
+ "t4": "Translator 4",
28
+ "t5": "Translator 5",
29
+ "t6": "Translator 6",
30
+ "t7": "Translator 7",
31
+ "t8": "Translator 8",
32
+ "t9": "Translator 9",
33
+ "t10": "Translator 10",
34
+ "t11": "Translator 11",
35
+ "t12": "Translator 12"
36
+ }
37
+ },
38
+ "main_task_translator_id": {
39
+ "title": "Main task translator ID",
40
+ "options": {
41
+ "no_highlight_t1": "Translator 1 - No Highlight Modality",
42
+ "no_highlight_t2": "Translator 2 - No Highlight Modality",
43
+ "no_highlight_t3": "Translator 3 - No Highlight Modality",
44
+ "oracle_t1": "Translator 1 - Oracle Modality",
45
+ "oracle_t2": "Translator 2 - Oracle Modality",
46
+ "oracle_t3": "Translator 3 - Oracle Modality",
47
+ "supervised_t1": "Translator 1 - Supervised Modality",
48
+ "supervised_t2": "Translator 2 - Supervised Modality",
49
+ "supervised_t3": "Translator 3 - Supervised Modality",
50
+ "unsupervised_t1": "Translator 1 - Unsupervised Modality",
51
+ "unsupervised_t2": "Translator 2 - Unsupervised Modality",
52
+ "unsupervised_t3": "Translator 3 - Unsupervised Modality"
53
+ }
54
+ },
55
+ "mt_quality": {
56
+ "title": "MT quality",
57
+ "prompt": "Rate the quality of machine translation for the texts you post-edited.",
58
+ "options": {
59
+ "1": "Very bad",
60
+ "2": "Worse than average",
61
+ "3": "Average",
62
+ "4": "Better than average",
63
+ "5": "Very good"
64
+ }
65
+ },
66
+ "frequent_issues": {
67
+ "title": "Frequent MT issues",
68
+ "prompt": "What issues were the most serious and frequent problems in the provided translations? Check all those that apply.",
69
+ "multiple_choice": true,
70
+ "options": {
71
+ "syntax": "The structure of sentences was unnatural",
72
+ "inflection": "Words were inflected incorrectly (gender, number, conjugations)",
73
+ "terminology": "Specific terms were translated incorrectly",
74
+ "additions": "Irrelevant information was added in the translation",
75
+ "omissions": "Relevant information was omitted in the translation",
76
+ "no_context": "Context was not taken into account in the translation",
77
+ "other": "Other (specify)"
78
+ }
79
+ },
80
+ "frequent_issues_other": {
81
+ "title": "Other frequent MT issues",
82
+ "other_text_for": "frequent_issues"
83
+ },
84
+ "mt_fluency": {
85
+ "title": "MT fluency",
86
+ "prompt": "What proportion of the machine translated outputs could be considered fluent prior to your editing? ( i.e. well formed grammatically, employing correct spelling and adhering to common use of terms, intuitively interpreted by a native speaker)",
87
+ "options": {
88
+ "0.2": "0 to 20%",
89
+ "0.4": "21 to 40%",
90
+ "0.6": "41 to 60%",
91
+ "0.8": "61 to 80%",
92
+ "1": "81 to 100%"
93
+ }
94
+ },
95
+ "mt_accuracy": {
96
+ "title": "MT accuracy",
97
+ "prompt": "What proportion of the machine translated machine translated outputs could be considered accurate prior to your editing? (i.e. the meaning of the original sentence was conveyed effectively, without adding or omitting information)",
98
+ "options": {
99
+ "0.2": "0 to 20%",
100
+ "0.4": "21 to 40%",
101
+ "0.6": "41 to 60%",
102
+ "0.8": "61 to 80%",
103
+ "1": "81 to 100%"
104
+ }
105
+ },
106
+ "highlight_accuracy": {
107
+ "title": "Highlight accuracy",
108
+ "prompt": "How accurate were the highlights in detecting potential issues in the machine translated outputs?",
109
+ "options": {
110
+ "1": "Very inaccurate",
111
+ "2": "Moderately inaccurate",
112
+ "3": "Neither accurate nor inaccurate",
113
+ "4": "Moderately accurate",
114
+ "5": "Very accurate"
115
+ }
116
+ },
117
+ "highlight_usefulness": {
118
+ "title": "Highlight usefulness",
119
+ "prompt": "How useful was the presence of highlights during the editing process?",
120
+ "options": {
121
+ "1": "Not useful at all",
122
+ "2": "Rarely useful",
123
+ "3": "Sometimes useful",
124
+ "4": "Often useful",
125
+ "5": "Always useful"
126
+ }
127
+ },
128
+ "highlight_comment": {
129
+ "title": "Highlight comment",
130
+ "prompt": "Motivate your choice for the usefulness of highlighting during the editing process."
131
+ },
132
+ "interface_quality": {
133
+ "title": "Interface quality",
134
+ "prompt": "Rate the overall quality of the interface you used for the task:",
135
+ "options": {
136
+ "1": "Much worse than average",
137
+ "2": "Mildly worse average",
138
+ "3": "Average",
139
+ "4": "Mildly better than average",
140
+ "5": "Much better than average"
141
+ }
142
+ },
143
+ "interface_quality_motivation": {
144
+ "title": "Interface quality motivation",
145
+ "prompt": "Motivate your rating for interface quality."
146
+ },
147
+ "interface_statement_1": {
148
+ "title": "Statement - Interface Accessibility",
149
+ "prompt": "Rate the following statement about the interface and data used for the task: The interface was easy to setup and access.",
150
+ "options": {
151
+ "1": "Strongly disagree",
152
+ "2": "Somewhat disagree",
153
+ "3": "Neither agree nor disagree",
154
+ "4": "Somewhat agree",
155
+ "5": "Strongly agree"
156
+ }
157
+ },
158
+ "interface_statement_2": {
159
+ "title": "Statement - Interface Clarity",
160
+ "prompt": "Rate the following statement about the interface and data used for the task: The interface was intuitive to use.",
161
+ "options": {
162
+ "1": "Strongly disagree",
163
+ "2": "Somewhat disagree",
164
+ "3": "Neither agree nor disagree",
165
+ "4": "Somewhat agree",
166
+ "5": "Strongly agree"
167
+ }
168
+ },
169
+ "interface_statement_3": {
170
+ "title": "Statement - Tech Issues",
171
+ "prompt": "Rate the following statement about the interface and data used for the task: I could complete the assignments without facing technical issues.",
172
+ "options": {
173
+ "1": "Strongly disagree",
174
+ "2": "Somewhat disagree",
175
+ "3": "Neither agree nor disagree",
176
+ "4": "Somewhat agree",
177
+ "5": "Strongly agree"
178
+ }
179
+ },
180
+ "interface_statement_4": {
181
+ "title": "Statement - Task Difficulty",
182
+ "prompt": "Rate the following statement about the interface and data used for the task: The provided texts were challenging to translate.",
183
+ "options": {
184
+ "1": "Strongly disagree",
185
+ "2": "Somewhat disagree",
186
+ "3": "Neither agree nor disagree",
187
+ "4": "Somewhat agree",
188
+ "5": "Strongly agree"
189
+ }
190
+ },
191
+ "interface_statement_5": {
192
+ "title": "Statement - Context Sufficiency",
193
+ "prompt": "Rate the following statement about the interface and data used for the task: The provided context in every document was sufficient to produce correct translations.",
194
+ "options": {
195
+ "1": "Strongly disagree",
196
+ "2": "Somewhat disagree",
197
+ "3": "Neither agree nor disagree",
198
+ "4": "Somewhat agree",
199
+ "5": "Strongly agree"
200
+ }
201
+ },
202
+ "interface_statement_6": {
203
+ "title": "Statement - Missing Features",
204
+ "prompt": "Rate the following statement about the interface and data used for the task: The interface was lacking useful features for improving my post-editing experience.",
205
+ "options": {
206
+ "1": "Strongly disagree",
207
+ "2": "Somewhat disagree",
208
+ "3": "Neither agree nor disagree",
209
+ "4": "Somewhat agree",
210
+ "5": "Strongly agree"
211
+ }
212
+ },
213
+ "highlight_statement_1": {
214
+ "title": "Statement - Highlights Productivity Impact",
215
+ "prompt": "Rate the following statement about the highlights: The presence of highlights improved my editing productivity.",
216
+ "options": {
217
+ "1": "Strongly disagree",
218
+ "2": "Somewhat disagree",
219
+ "3": "Neither agree nor disagree",
220
+ "4": "Somewhat agree",
221
+ "5": "Strongly agree"
222
+ }
223
+ },
224
+ "highlight_statement_2": {
225
+ "title": "Statement - Highlights Quality Impact",
226
+ "prompt": "Rate the following statement about the highlights: The presence of highlights improved the quality of my translations.",
227
+ "options": {
228
+ "1": "Strongly disagree",
229
+ "2": "Somewhat disagree",
230
+ "3": "Neither agree nor disagree",
231
+ "4": "Somewhat agree",
232
+ "5": "Strongly agree"
233
+ }
234
+ },
235
+ "highlight_statement_3": {
236
+ "title": "Statement - Highlights Creativity Impact",
237
+ "prompt": "Rate the following statement about the highlights: The presence of highlights made my translations more creative.",
238
+ "options": {
239
+ "1": "Strongly disagree",
240
+ "2": "Somewhat disagree",
241
+ "3": "Neither agree nor disagree",
242
+ "4": "Somewhat agree",
243
+ "5": "Strongly agree"
244
+ }
245
+ },
246
+ "highlight_statement_4": {
247
+ "title": "Statement - Highlights Editing Effort Impact",
248
+ "prompt": "Rate the following statement about the highlights: Post-editing texts with highlights required additional editing effort from my part.",
249
+ "options": {
250
+ "1": "Strongly disagree",
251
+ "2": "Somewhat disagree",
252
+ "3": "Neither agree nor disagree",
253
+ "4": "Somewhat agree",
254
+ "5": "Strongly agree"
255
+ }
256
+ },
257
+ "highlight_statement_5": {
258
+ "title": "Statement - Highlights Editing Choices Impact",
259
+ "prompt": "Rate the following statement about the highlights: The presence of highlights influenced my editing choices.",
260
+ "options": {
261
+ "1": "Strongly disagree",
262
+ "2": "Somewhat disagree",
263
+ "3": "Neither agree nor disagree",
264
+ "4": "Somewhat agree",
265
+ "5": "Strongly agree"
266
+ }
267
+ },
268
+ "highlight_statement_6": {
269
+ "title": "Statement - Highlights Error Identification Impact",
270
+ "prompt": "Rate the following statement about the highlights: Highlights helped me identify errors that I would have otherwise missed.",
271
+ "options": {
272
+ "1": "Strongly disagree",
273
+ "2": "Somewhat disagree",
274
+ "3": "Neither agree nor disagree",
275
+ "4": "Somewhat agree",
276
+ "5": "Strongly agree"
277
+ }
278
+ },
279
+ "highlight_statement_7": {
280
+ "title": "Statement - Highlights Enjoyability Impact",
281
+ "prompt": "Rate the following statement about the highlights: I enjoyed post-editing with highlights more than regular post-editing.",
282
+ "options": {
283
+ "1": "Strongly disagree",
284
+ "2": "Somewhat disagree",
285
+ "3": "Neither agree nor disagree",
286
+ "4": "Somewhat agree",
287
+ "5": "Strongly agree"
288
+ }
289
+ },
290
+ "highlight_statement_8": {
291
+ "title": "Statement - Highlights Future Interest",
292
+ "prompt": "Rate the following statement about the highlights: I wish highlights could be added to my CAT tool of choice for future editing tasks.",
293
+ "options": {
294
+ "1": "Strongly disagree",
295
+ "2": "Somewhat disagree",
296
+ "3": "Neither agree nor disagree",
297
+ "4": "Somewhat agree",
298
+ "5": "Strongly agree"
299
+ }
300
+ },
301
+ "highlight_like": {
302
+ "title": "Highlight like",
303
+ "prompt": "In the experiment, what did you like about post-editing with highlights compared to regular post-editing?"
304
+ },
305
+ "highlight_dislike": {
306
+ "title": "Highlight dislike",
307
+ "prompt": "In the experiment, what did you dislike about post-editing with highlights compared to regular post-editing?"
308
+ },
309
+ "interface_improvement": {
310
+ "title": "Interface improvement",
311
+ "prompt": "Which one of these features, if any, were notable exclusions that you would like to see included in the post-editing interface you used for this task? Select all that apply.",
312
+ "multiple_choice": true,
313
+ "options": {
314
+ "spellcheck": "The interface does not provide spellchecking for translations",
315
+ "multidoc_streamline": "The process of editing several files is cumbersome",
316
+ "mid_edit_save": "The editing process cannot be saved mid-document",
317
+ "tm_lexicon": "No direct access to translation memories and lexicons",
318
+ "other_mt": "No direct access to other machine translation systems"
319
+ }
320
+ }
321
+
322
+ }
questionnaires/posttask_highlight_results.csv ADDED
@@ -0,0 +1,19 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ time,translation_direction,main_task_modality,pretask_translator_id,main_task_translator_id,mt_quality,frequent_issues,frequent_issues_other,mt_fluency,mt_accuracy,highlight_accuracy,highlight_usefulness,highlight_comment,interface_quality,interface_quality_motivation,interface_statement_1,interface_statement_2,interface_statement_3,interface_statement_4,interface_statement_5,interface_statement_6,highlight_statement_1,highlight_statement_2,highlight_statement_3,highlight_statement_4,highlight_statement_5,highlight_statement_6,highlight_statement_7,highlight_statement_8,highlight_like,highlight_dislike,interface_improvement
2
+ 77,eng-ita,oracle,t1,oracle_t2,3,"syntax,terminology,omissions,no_context",,0.4,0.6,2,1,"I barely looked at the highlighted terms, since the sentences were in need of restoration as a whole.",2,"So many aspects to improve: impossibility to save segments after translation, editing was clumsy due to the highlights, no context available whatsoever, saving system negligible, annoying system crashes.",3,3,1,4,1,5,1,1,1,4,1,1,1,1,"NOTHING! :D","EVERYTHING! :D","spellcheck,multidoc_streamline,mid_edit_save,tm_lexicon,other_mt"
3
+ 175,eng-ita,unsupervised,t2,unsupervised_t3,3,"syntax,inflection,terminology,omissions",,0.4,0.6,2,2,"Most of the times the highlighted terms or expressions were actually correct. It was useful to find real errors just in a few cases.",3,"The interface is user-friendly but it omitted entire sentences.",4,4,3,4,2,3,2,2,3,3,3,4,4,2,"I did not find any relevant advantages in post-editing with highlights. It was useful to spot real errors in a very few cases.","I waisted time trying to spot an error that actually did not exist.","spellcheck,mid_edit_save,tm_lexicon,other_mt"
4
+ 69,eng-ita,oracle,t3,oracle_t3,3,"syntax,no_context",,0.6,0.6,2,2,"Highlights were useful only to spot typos/extra spaces, but they were hardly useful to spot other error types.",2,"There was no TM/glossary available, also it was not possible to leave comments.",5,5,5,4,1,5,1,1,1,1,1,4,1,1,"I liked the fact that highlights were useful to spot typos and extra spaces that otherwise I might not have noticed.","Highlights did not help me to spot the vast majority of mistakes (accuracy, omissions, style etc.). Also, the different categories of highlights (minor and major mistakes) were not correctly reflected in the texts to be post-edited.","mid_edit_save,tm_lexicon"
5
+ 448,eng-ita,supervised,t4,supervised_t3,3,"syntax,terminology,omissions,no_context",,0.6,0.6,2,2,"The highlights provided within the copy were more of an eye distraction as they often weren’t actual mistakes.",1,"major issue: impossible to save work if page needs refreshing, nor to edit segments once saved - no glossaries",2,2,1,4,2,5,2,1,1,1,4,4,1,1,"nothing. I found them quite unuseful and distracting","See previous answer","spellcheck,mid_edit_save,tm_lexicon"
6
+ 115,eng-ita,unsupervised,t5,unsupervised_t2,3,"syntax,terminology,no_context",,0.6,0.6,3,3,"Highlights were not much accurate in indicating mistakes",3,"There was no spell checker. We had to log in each time we had to upload a new text",5,4,5,4,4,3,2,3,2,2,1,1,3,2,"Highlights did not make a significant difference","Same as above","spellcheck,multidoc_streamline,mid_edit_save,tm_lexicon"
7
+ 201,eng-ita,supervised,t6,supervised_t2,3,"syntax,terminology,no_context",,0.4,0.4,2,2,"Highlights were often unnecessary because the term/sentence wasn't wrong or because they didn't focus on the real issues",3,"The interface was basic, it provided just the target translation and highlights, but no other useful features, such as glossary, matches, a.s.o.",5,5,3,4,2,5,3,2,2,4,3,3,4,4,"They helped me identify possible errors","Highlights were often unnecessary","spellcheck,tm_lexicon"
8
+ 192,eng-ita,unsupervised,t7,unsupervised_t1,3,"omissions",,0.8,0.6,3,2,"Very often I found the presence of the highlighted words to be of little use because either it was not necessary to change them or because it did not change much in the individuation of the error.",4,"simple and intuitive.",5,5,5,3,2,3,3,3,3,3,2,2,2,2,"As already mentioned, having the words highlighted did not change or affect much in my translation experience.","The experience of highlighting the words was of no benefit because sometimes it happened that you had to edit not just the highlighted word but the entire sentence.","spellcheck"
9
+ 87,eng-ita,supervised,t8,supervised_t1,3,"syntax,terminology,no_context",,0.4,0.4,2,1,"Often the highlights concerned correct terms and, at the same time, incorrect words were unmarked. In my editing process I therefore ended up disregarding the highlights in order to focus on the check of each sentence.",2,"The interface was very basic and did not allow the user to act on the text in a fluid manner or to make use of translation memories for text editing.",2,2,2,5,2,5,1,1,3,3,1,2,2,2,"The presence of highlights did not enhance the post-editing experience for the reasons explained above.","Highlights simply proved to be of little use in the post-editing process. ","spellcheck,multidoc_streamline,mid_edit_save,tm_lexicon,other_mt"
10
+ 80,eng-ita,oracle,t11,oracle_t1,5,"inflection,terminology",,0.4,0.8,4,4,"It helped me a lot, making the editing process faster and somehow easier. ",4,"Compared to the other interfaces I used (and I still use) for translating or editing texts, this one was better because the outputs were of better quality than average and the editing process was faster.",5,5,5,3,3,3,5,2,1,1,1,1,4,4,"I liked it because it made the editing process faster and somehow easier. ","Nothing, overall I liked post-editing with highlights :) ","mid_edit_save,tm_lexicon"
11
+ 890,eng-nld,unsupervised,t2,unsupervised_t2,3,"syntax,inflection,terminology,additions,omissions,no_context",,0.6,0.6,4,3,"Sometimes it was useful and other times important mistakes were not highlighted, so I'd say it's not quite accurate enough to rely on them as a suggestion.",2,"most translation software I've used is more user friendly, especially because you have to upload each section of the assignment manually and re-type your name/password every time. Also it's hard to get back into it and if you refresh the page by mistake, it won't have saved your project mid-way through.",4,2,1,4,1,4,3,3,2,4,3,2,3,3,"The highlights would in theory speed up the process of translation, but when you get tempted to rely on them too much, this pro becomes a con, because it just isn't good enough yet.","The fact that the highlights are not that reliable yet and miss some crucial mistakes. E.g. some words/sentences were missing from the target language, which you wouldn't notice if you rely too much on highlights (given the fact that you won't see highlighted empty space).","spellcheck,multidoc_streamline,mid_edit_save,other_mt"
12
+ 81,eng-nld,unsupervised,t3,unsupervised_t3,1,"syntax,terminology,omissions",,0.4,0.4,2,4,"The highlights often showed that a change was needed, but they by far didn't cover everything",1,"I missed a lot of options usually available in translation tools, such as for in-between saving, glossaries, reverting to previous translations, concordance search options, etc.",4,3,5,5,1,1,4,4,4,3,2,2,3,4,"The highlights showed where edits were (mostly) needed, but they were insufficient as an indication of all required edits.","I didn't dislike the highlights as such","spellcheck,multidoc_streamline,mid_edit_save,tm_lexicon"
13
+ 127,eng-nld,oracle,t4,oracle_t1,3,"syntax,inflection,terminology",,0.6,0.6,2,1,"I didn't look at the highlighting. Too confusing.",3,"Not translator friendly",2,2,3,3,3,4,2,2,2,2,1,1,1,1,"I didn't like it","They were confusing and annoying","spellcheck,multidoc_streamline"
14
+ 76,eng-nld,supervised,t6,supervised_t3,5,"syntax,terminology,additions,omissions,no_context",,0.8,1,4,3,"They were accurate about 50% of the time. so they are 50% useful :)",2,"No integrated tools such as glossary, translation memory, spelling and grammar checks.",5,5,4,5,4,5,3,3,3,2,2,2,4,3,"It's new to me, which added interest. If they become a bit more accurate, it could be a nice feature.","They draw attention, but are not always accurate.","spellcheck,multidoc_streamline,mid_edit_save,tm_lexicon,other_mt"
15
+ 97,eng-nld,unsupervised,t7,unsupervised_t1,3,"terminology,additions,omissions,other",Sometimes an entire sentence or part was missing.,0.6,0.8,3,2,"The highlighting did not always indicate an actual flaw. I think maybe in 10% of the cases it was an actual mistake, in other cases just something MT thought was wrong but was not.",4,"There were some hiccups with logging in, until I found the browser that worked. It was a bit unconvenient that the login code/user name could not be saved (and that this had to be re-entered for every individual task.",4,5,3,4,3,3,1,3,1,1,1,2,1,1,"I felt neutral about them. Mostly they were distracting, but I did look at them and sometimes they were useful.","They were not accurate most of the time.","spellcheck,multidoc_streamline,tm_lexicon,other_mt"
16
+ 89,eng-nld,supervised,t8,supervised_t2,3,"syntax,additions,no_context",,0.4,0.6,2,2,"It seemed that the highlights were mostly false positives, yet other issues were not highlighted, but did need attention, such as structural errors.",2,"The biggest issues: a) it was not possible to save your work in between editing, or even edit anything after saving. b) lack of glossary, which could be very useful, especially for specific areas of expertise, such as medical translations. c) the process of loading a new document seemed time consuming, because you have to go back to the main page, log in again and upload a new document. It would be better to load all the documents in one go and then have button to go back and forth to the next or previous document. Also the warning message seemed unnecessary that all progress would be lost if going back to the main page, because you cannot edit anything after saving anyway.",4,2,3,3,2,5,1,1,1,1,1,2,3,2,"Highlights can be very useful if they are indeed indicating an error. ","The highlights were usually false positives and didn't seem useful in indicating actual mistakes","spellcheck,multidoc_streamline,mid_edit_save,tm_lexicon,other_mt"
17
+ 71,eng-nld,oracle,t10,oracle_t3,3,"syntax,terminology",,0.6,0.4,3,1,"Emphasizing the errors proved to be of limited utility, as modifications were necessary in nearly every section.",3,"The interface was average at best; it didn’t have any remarkable features, but it wasn’t lacking either.",4,4,5,3,2,4,1,1,1,1,1,1,3,1,"My feelings towards post-editing with highlights were neutral; I neither favored it nor disfavored it in comparison to traditional post-editing methods","Highlighting the mistakes turned out to be somewhat ineffective.","spellcheck,multidoc_streamline"
18
+ 175,eng-nld,oracle,t11,oracle_t2,3,"syntax",,0.8,0.6,4,3,"3 because they were not always positioned correctly",3,"the interface provided an acceptable modus operandi, I disliked the fact that for every single file I had to check in again.",4,5,2,5,2,3,3,3,2,3,3,2,3,3,"I have to admit that to me the presence of the highlights did not change my way of working, maybe they prompted me to check the completeness of my revision","did not dislike their presence, just they did not prove themselves to be very useful to me","spellcheck,multidoc_streamline,mid_edit_save,tm_lexicon"
19
+ 290,eng-nld,supervised,t12,supervised_t1,3,"terminology,omissions,no_context",,0.6,0.4,2,2,"Bad context, sentence structure and translations.",3,"Interface is good but limited.",5,5,5,1,2,5,1,1,1,5,3,1,1,1,"It does draw your attention to potential problems.","The highlights are usually false positive.","multidoc_streamline,mid_edit_save,tm_lexicon,other_mt"
questionnaires/posttask_no_highlight_config.json ADDED
@@ -0,0 +1,241 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "time": {
3
+ "title": "Duration (in seconds)"
4
+ },
5
+ "translation_direction": {
6
+ "title": "Translation direction",
7
+ "options": {
8
+ "eng-ita": "English to Italian",
9
+ "eng-nld": "English to Dutch"
10
+ }
11
+ },
12
+ "main_task_modality": {
13
+ "title": "Main task modality",
14
+ "options": {
15
+ "no_highlight": "No Highlight",
16
+ "oracle": "Oracle",
17
+ "supervised": "Supervised",
18
+ "unsupervised": "Unsupervised"
19
+ }
20
+ },
21
+ "pretask_translator_id": {
22
+ "title": "Pretask translator ID",
23
+ "options": {
24
+ "t1": "Translator 1",
25
+ "t2": "Translator 2",
26
+ "t3": "Translator 3",
27
+ "t4": "Translator 4",
28
+ "t5": "Translator 5",
29
+ "t6": "Translator 6",
30
+ "t7": "Translator 7",
31
+ "t8": "Translator 8",
32
+ "t9": "Translator 9",
33
+ "t10": "Translator 10",
34
+ "t11": "Translator 11",
35
+ "t12": "Translator 12"
36
+ }
37
+ },
38
+ "main_task_translator_id": {
39
+ "title": "Main task translator ID",
40
+ "options": {
41
+ "no_highlight_t1": "Translator 1 - No Highlight Modality",
42
+ "no_highlight_t2": "Translator 2 - No Highlight Modality",
43
+ "no_highlight_t3": "Translator 3 - No Highlight Modality",
44
+ "oracle_t1": "Translator 1 - Oracle Modality",
45
+ "oracle_t2": "Translator 2 - Oracle Modality",
46
+ "oracle_t3": "Translator 3 - Oracle Modality",
47
+ "supervised_t1": "Translator 1 - Supervised Modality",
48
+ "supervised_t2": "Translator 2 - Supervised Modality",
49
+ "supervised_t3": "Translator 3 - Supervised Modality",
50
+ "unsupervised_t1": "Translator 1 - Unsupervised Modality",
51
+ "unsupervised_t2": "Translator 2 - Unsupervised Modality",
52
+ "unsupervised_t3": "Translator 3 - Unsupervised Modality"
53
+ }
54
+ },
55
+ "mt_quality": {
56
+ "title": "MT quality",
57
+ "prompt": "Rate the quality of machine translation for the texts you post-edited.",
58
+ "options": {
59
+ "1": "Very bad",
60
+ "2": "Worse than average",
61
+ "3": "Average",
62
+ "4": "Better than average",
63
+ "5": "Very good"
64
+ }
65
+ },
66
+ "frequent_issues": {
67
+ "title": "Frequent MT issues",
68
+ "prompt": "What issues were the most serious and frequent problems in the provided translations? Check all those that apply.",
69
+ "multiple_choice": true,
70
+ "options": {
71
+ "syntax": "The structure of sentences was unnatural",
72
+ "inflection": "Words were inflected incorrectly (gender, number, conjugations)",
73
+ "terminology": "Specific terms were translated incorrectly",
74
+ "additions": "Irrelevant information was added in the translation",
75
+ "omissions": "Relevant information was omitted in the translation",
76
+ "no_context": "Context was not taken into account in the translation",
77
+ "other": "Other (specify)"
78
+ }
79
+ },
80
+ "frequent_issues_other": {
81
+ "title": "Other frequent MT issues",
82
+ "other_text_for": "frequent_issues"
83
+ },
84
+ "mt_fluency": {
85
+ "title": "MT fluency",
86
+ "prompt": "What proportion of the machine translated outputs could be considered fluent prior to your editing? ( i.e. well formed grammatically, employing correct spelling and adhering to common use of terms, intuitively interpreted by a native speaker)",
87
+ "options": {
88
+ "0.2": "0 to 20%",
89
+ "0.4": "21 to 40%",
90
+ "0.6": "41 to 60%",
91
+ "0.8": "61 to 80%",
92
+ "1": "81 to 100%"
93
+ }
94
+ },
95
+ "mt_accuracy": {
96
+ "title": "MT accuracy",
97
+ "prompt": "What proportion of the machine translated machine translated outputs could be considered accurate prior to your editing? (i.e. the meaning of the original sentence was conveyed effectively, without adding or omitting information)",
98
+ "options": {
99
+ "0.2": "0 to 20%",
100
+ "0.4": "21 to 40%",
101
+ "0.6": "41 to 60%",
102
+ "0.8": "61 to 80%",
103
+ "1": "81 to 100%"
104
+ }
105
+ },
106
+ "interface_quality": {
107
+ "title": "Interface quality",
108
+ "prompt": "Rate the overall quality of the interface you used for the task:",
109
+ "options": {
110
+ "1": "Much worse than average",
111
+ "2": "Mildly worse average",
112
+ "3": "Average",
113
+ "4": "Mildly better than average",
114
+ "5": "Much better than average"
115
+ }
116
+ },
117
+ "interface_quality_motivation": {
118
+ "title": "Interface quality motivation",
119
+ "prompt": "Motivate your rating for interface quality."
120
+ },
121
+ "interface_statement_1": {
122
+ "title": "Statement - Interface Accessibility",
123
+ "prompt": "Rate the following statement about the interface and data used for the task: The interface was easy to setup and access.",
124
+ "options": {
125
+ "1": "Strongly disagree",
126
+ "2": "Somewhat disagree",
127
+ "3": "Neither agree nor disagree",
128
+ "4": "Somewhat agree",
129
+ "5": "Strongly agree"
130
+ }
131
+ },
132
+ "interface_statement_2": {
133
+ "title": "Statement - Interface Clarity",
134
+ "prompt": "Rate the following statement about the interface and data used for the task: The interface was intuitive to use.",
135
+ "options": {
136
+ "1": "Strongly disagree",
137
+ "2": "Somewhat disagree",
138
+ "3": "Neither agree nor disagree",
139
+ "4": "Somewhat agree",
140
+ "5": "Strongly agree"
141
+ }
142
+ },
143
+ "interface_statement_3": {
144
+ "title": "Statement - Tech Issues",
145
+ "prompt": "Rate the following statement about the interface and data used for the task: I could complete the assignments without facing technical issues.",
146
+ "options": {
147
+ "1": "Strongly disagree",
148
+ "2": "Somewhat disagree",
149
+ "3": "Neither agree nor disagree",
150
+ "4": "Somewhat agree",
151
+ "5": "Strongly agree"
152
+ }
153
+ },
154
+ "interface_statement_4": {
155
+ "title": "Statement - Task Difficulty",
156
+ "prompt": "Rate the following statement about the interface and data used for the task: The provided texts were challenging to translate.",
157
+ "options": {
158
+ "1": "Strongly disagree",
159
+ "2": "Somewhat disagree",
160
+ "3": "Neither agree nor disagree",
161
+ "4": "Somewhat agree",
162
+ "5": "Strongly agree"
163
+ }
164
+ },
165
+ "interface_statement_5": {
166
+ "title": "Statement - Context Sufficiency",
167
+ "prompt": "Rate the following statement about the interface and data used for the task: The provided context in every document was sufficient to produce correct translations.",
168
+ "options": {
169
+ "1": "Strongly disagree",
170
+ "2": "Somewhat disagree",
171
+ "3": "Neither agree nor disagree",
172
+ "4": "Somewhat agree",
173
+ "5": "Strongly agree"
174
+ }
175
+ },
176
+ "interface_statement_6": {
177
+ "title": "Statement - Missing Features",
178
+ "prompt": "Rate the following statement about the interface and data used for the task: The interface was lacking useful features for improving my post-editing experience.",
179
+ "options": {
180
+ "1": "Strongly disagree",
181
+ "2": "Somewhat disagree",
182
+ "3": "Neither agree nor disagree",
183
+ "4": "Somewhat agree",
184
+ "5": "Strongly agree"
185
+ }
186
+ },
187
+ "highlight_statement_1": {
188
+ "title": "Statement - Pretask Usefulness",
189
+ "prompt": "In this task, you post-edited texts without highlights, as opposed to the pre-task were they were present. In light of this, rate the following statement: - The pre-task was too short to assess the usefulness of highlights.",
190
+ "options": {
191
+ "1": "Strongly disagree",
192
+ "2": "Somewhat disagree",
193
+ "3": "Neither agree nor disagree",
194
+ "4": "Somewhat agree",
195
+ "5": "Strongly agree"
196
+ }
197
+ },
198
+ "highlight_statement_2": {
199
+ "title": "Statement - Highlights Usefulness Speculation",
200
+ "prompt": "In this task, you post-edited texts without highlights, as opposed to the pre-task were they were present. In light of this, rate the following statement: - I think highlights would have improved my editing workflow in the main-task.",
201
+ "options": {
202
+ "1": "Strongly disagree",
203
+ "2": "Somewhat disagree",
204
+ "3": "Neither agree nor disagree",
205
+ "4": "Somewhat agree",
206
+ "5": "Strongly agree"
207
+ }
208
+ },
209
+ "highlight_statement_3": {
210
+ "title": "Statement - Highlights Future Interest",
211
+ "prompt": "In this task, you post-edited texts without highlights, as opposed to the pre-task were they were present. In light of this, rate the following statement: - I wish higlights could be added to my CAT tool of choice for future editing tasks",
212
+ "options": {
213
+ "1": "Strongly disagree",
214
+ "2": "Somewhat disagree",
215
+ "3": "Neither agree nor disagree",
216
+ "4": "Somewhat agree",
217
+ "5": "Strongly agree"
218
+ }
219
+ },
220
+ "highlight_like": {
221
+ "title": "Highlight like",
222
+ "prompt": "Having tried editing with and without highlights, what did you like about post-editing with highlights compared to regular post-editing?"
223
+ },
224
+ "highlight_dislike": {
225
+ "title": "Highlight dislike",
226
+ "prompt": "Having tried editing with and without highlights, what did you dislike about post-editing with highlights compared to regular post-editing?"
227
+ },
228
+ "interface_improvement": {
229
+ "title": "Interface improvement",
230
+ "prompt": "Which one of these features, if any, were notable exclusions that you would like to see included in the post-editing interface you used for this task? Select all that apply.",
231
+ "multiple_choice": true,
232
+ "options": {
233
+ "spellcheck": "The interface does not provide spellchecking for translations",
234
+ "multidoc_streamline": "The process of editing several files is cumbersome",
235
+ "mid_edit_save": "The editing process cannot be saved mid-document",
236
+ "tm_lexicon": "No direct access to translation memories and lexicons",
237
+ "other_mt": "No direct access to other machine translation systems"
238
+ }
239
+ }
240
+
241
+ }
questionnaires/posttask_no_highlight_results.csv ADDED
@@ -0,0 +1,7 @@
 
 
 
 
 
 
 
 
1
+ time,translation_direction,main_task_modality,pretask_translator_id,main_task_translator_id,mt_quality,frequent_issues,frequent_issues_other,mt_fluency,mt_accuracy,interface_quality,interface_quality_motivation,interface_statement_1,interface_statement_2,interface_statement_3,interface_statement_4,interface_statement_5,interface_statement_6,highlight_statement_1,highlight_statement_2,highlight_statement_3,highlight_like,highlight_dislike,interface_improvement
2
+ 181,eng-ita,no_highlight,t9,no_highlight_t3,3,"terminology,omissions",,0.8,0.8,2,Because no work could be saved during revision,4,1,3,5,4,5,3,3,3,Not sure what highlight means in this context,Not sure what highlight means in this context,"spellcheck,multidoc_streamline,mid_edit_save,tm_lexicon,other_mt"
3
+ 75,eng-ita,no_highlight,t10,no_highlight_t1,4,"inflection,additions,omissions",,0.8,0.8,4,Intuitive and clear,4,5,5,1,4,1,1,1,3,"I think that post-editing with highlights can be useful to first identify the most important elements to be post-edited but on the other hand can overshadow other elements that might still need post-editing. It's like a double-edged sword but if you are careful, highlights can be useful.","The possibility of being visually distracted by the highlighted elements, while still wanting to check the whole sentence, i.e. also the non-highlighted elements.","spellcheck,multidoc_streamline,mid_edit_save"
4
+ 94,eng-ita,no_highlight,t12,no_highlight_t2,3,"syntax,inflection,terminology,omissions,no_context",,0.6,0.4,2,Cumbersome to upload and download files. No spellcheck included. I liked that it was simple and so it's easy to concentrate on the actual translation job.,2,2,5,4,5,5,5,1,1,Highlights were not helpful at all. I just deleted them at the beginning of the post-editing process. ,"As I said above, just a way to lose time :) as they were not highlighting anything that required any particular attention.","spellcheck,multidoc_streamline,tm_lexicon"
5
+ 460,eng-nld,no_highlight,t1,no_highlight_t1,3,"syntax,terminology,omissions,no_context",,0.2,0.4,2,"Not being able to save your work, no spell check. Zero context provided about texts.",5,4,5,4,1,3,4,3,3,I didn't really notice much of a difference.,I didn't really notice much of a difference.,"spellcheck,mid_edit_save"
6
+ 98,eng-nld,no_highlight,t5,no_highlight_t2,2,"syntax,terminology,omissions,no_context",,0.4,0.6,1,"I couldn't see the name of the file that I was editing. It often took ages for the Download button to be available. When I pasted copy from elsewhere, the formatting was preserved and there was no way (that I could see) to paste without formatting.",5,4,1,5,1,4,3,1,1,Nothing,The highlights only distracted from my work. I didn't think they had any added value.,spellcheck
7
+ 472,eng-nld,no_highlight,t9,no_highlight_t3,2,"terminology,omissions,no_context",,0.2,0.4,1,It had none of the functions that the average CAT-tool has.,5,3,1,5,1,5,5,4,3,"Highlights can help, but everything has to be checked anyway.",Nothing much except (see previous answer) they could provide a false sense of security.,"multidoc_streamline,mid_edit_save,tm_lexicon,other_mt"
questionnaires/pretask_config.json ADDED
@@ -0,0 +1,262 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "time": {
3
+ "title": "Duration (in seconds)"
4
+ },
5
+ "translation_direction": {
6
+ "title": "Translation direction",
7
+ "options": {
8
+ "eng-ita": "English to Italian",
9
+ "eng-nld": "English to Dutch"
10
+ }
11
+ },
12
+ "main_task_modality": {
13
+ "title": "Main task modality",
14
+ "options": {
15
+ "no_highlight": "No Highlight",
16
+ "oracle": "Oracle",
17
+ "supervised": "Supervised",
18
+ "unsupervised": "Unsupervised"
19
+ }
20
+ },
21
+ "pretask_translator_id": {
22
+ "title": "Pretask translator ID",
23
+ "options": {
24
+ "t1": "Translator 1",
25
+ "t2": "Translator 2",
26
+ "t3": "Translator 3",
27
+ "t4": "Translator 4",
28
+ "t5": "Translator 5",
29
+ "t6": "Translator 6",
30
+ "t7": "Translator 7",
31
+ "t8": "Translator 8",
32
+ "t9": "Translator 9",
33
+ "t10": "Translator 10",
34
+ "t11": "Translator 11",
35
+ "t12": "Translator 12"
36
+ }
37
+ },
38
+ "main_task_translator_id": {
39
+ "title": "Main task translator ID",
40
+ "options": {
41
+ "no_highlight_t1": "Translator 1 - No Highlight Modality",
42
+ "no_highlight_t2": "Translator 2 - No Highlight Modality",
43
+ "no_highlight_t3": "Translator 3 - No Highlight Modality",
44
+ "oracle_t1": "Translator 1 - Oracle Modality",
45
+ "oracle_t2": "Translator 2 - Oracle Modality",
46
+ "oracle_t3": "Translator 3 - Oracle Modality",
47
+ "supervised_t1": "Translator 1 - Supervised Modality",
48
+ "supervised_t2": "Translator 2 - Supervised Modality",
49
+ "supervised_t3": "Translator 3 - Supervised Modality",
50
+ "unsupervised_t1": "Translator 1 - Unsupervised Modality",
51
+ "unsupervised_t2": "Translator 2 - Unsupervised Modality",
52
+ "unsupervised_t3": "Translator 3 - Unsupervised Modality"
53
+ }
54
+ },
55
+ "mother_tongue": {
56
+ "title": "Mother tongue",
57
+ "prompt": "Specify your mother tongue. If needed, you can specify more than one language.",
58
+ "options": {
59
+ "ita": "Italian",
60
+ "nld": "Dutch",
61
+ "other": "Other (specify)"
62
+ }
63
+ },
64
+ "mother_tongue_other": {
65
+ "title": "Mother tongue (other)",
66
+ "other_text_for": "mother_tongue"
67
+ },
68
+ "language_combination": {
69
+ "title": "Language combination",
70
+ "prompt": "Please, specify which language combination you work with more frequently.",
71
+ "options": {
72
+ "eng-ita": "English to Italian",
73
+ "ita-eng": "Italian to English",
74
+ "eng-nld": "English to Dutch",
75
+ "nld-eng": "Dutch to English",
76
+ "other": "Other (specify)"
77
+ }
78
+ },
79
+ "language_combination_other": {
80
+ "title": "Language combination (other)",
81
+ "other_text_for": "language_combination"
82
+ },
83
+ "current_position": {
84
+ "title": "Current position",
85
+ "prompt": "Please, specify your current position/job/activity.",
86
+ "options": {
87
+ "fulltime_freelancer": "Full-time freelance translator",
88
+ "parttime_freelancer": "Part-time freelance translator",
89
+ "fulltime_employed": "Employed full-time in a translation agency",
90
+ "parttime_employed": "Employed part-time in a translation agency",
91
+ "other": "Other (specify)"
92
+ }
93
+ },
94
+ "current_position_other": {
95
+ "title": "Current position (other)",
96
+ "other_text_for": "current_position"
97
+ },
98
+ "english_level": {
99
+ "title": "English proficiency",
100
+ "prompt": "Specify your estimated English proficiency. A1 is equivalent to a beginners level and C2 to a native or near native speaker level according to the Common European Framework of Reference for Languages (CEFR).",
101
+ "options": {
102
+ "a1": "A1",
103
+ "a2": "A2",
104
+ "b1": "B1",
105
+ "b2": "B2",
106
+ "c1": "C1",
107
+ "c2": "C2"
108
+ }
109
+ },
110
+ "translation_experience": {
111
+ "title": "Translation experience",
112
+ "prompt": "Specify your professional experience as a translator overall in number of years.",
113
+ "options": {
114
+ "2": "Less than 2 years",
115
+ "3.5": "Between 2 and 5 years",
116
+ "7.5": "Between 5 and 10 years",
117
+ "10": "More than 10 years"
118
+ }
119
+ },
120
+ "pe_proficiency": {
121
+ "title": "Post editing proficiency",
122
+ "prompt": "As a professional translator, have you post-edited machine translated texts?",
123
+ "options": {
124
+ "1": "Yes",
125
+ "0": "No"
126
+ }
127
+ },
128
+ "pe_experience": {
129
+ "title": "Post editing experience",
130
+ "prompt": "Specify the number of years of experience in post-editing machine translated texts.",
131
+ "options": {
132
+ "2": "Less than 2 years",
133
+ "3.5": "Between 2 and 5 years",
134
+ "7.5": "Between 5 and 10 years",
135
+ "10": "More than 10 years"
136
+ }
137
+ },
138
+ "pe_percentage": {
139
+ "title": "Post editing percentage",
140
+ "prompt": "In the last 12 months, which percentage of your translation tasks involved post-editing machine translated texts?",
141
+ "options": {
142
+ "0.2": "0 to 20%",
143
+ "0.4": "21 to 40%",
144
+ "0.6": "41 to 60%",
145
+ "0.8": "61 to 80%",
146
+ "1": "81 to 100%"
147
+ }
148
+ },
149
+ "catt_experience": {
150
+ "title": "Computer-assisted translation technologies experience",
151
+ "prompt": "How often do you employ computer-assisted translation technologies, such as translation memories or quality estimation, in your translation work?",
152
+ "options": {
153
+ "1": "Never",
154
+ "2": "Rarely",
155
+ "3": "From time to time",
156
+ "4": "Often",
157
+ "5": "Always"
158
+ }
159
+ },
160
+ "mt_statements": {
161
+ "title": "Machine translation statements",
162
+ "prompt": "Please, select the answer(s) that best represents your views on Machine Translation (MT). Check all the options that apply.",
163
+ "multiple_choice": true,
164
+ "options": {
165
+ "like_A": "I like using MT for repetitive work that requires consistency.",
166
+ "like_B": "I like using MT to check certain words or expressions.",
167
+ "like_C": "I like using MT to trigger my creativity.",
168
+ "like_D": "I like using MT because it makes me more productive.",
169
+ "like_E": "I like using MT because it improves the quality of my translations.",
170
+ "dislike_A": "I don't like using MT because it makes me less creative.",
171
+ "dislike_B": "I don't like using MT because it makes me less productive.",
172
+ "dislike_C": "I don't like using MT because the proposals are poor in quality.",
173
+ "dislike_D": "I don't like using MT because it makes my translations worse.",
174
+ "other": "Other (specify)"
175
+ }
176
+ },
177
+ "mt_statements_other": {
178
+ "title": "Machine translation statements (other)",
179
+ "other_text_for": "mt_statements"
180
+ },
181
+ "statement_1": {
182
+ "title": "Statement - Confidence in Editing Human Translations",
183
+ "prompt": "Rate the following statement: I feel confident in reviewing translations produced by other professional translators.",
184
+ "options": {
185
+ "1": "Strongly disagree",
186
+ "2": "Somewhat disagree",
187
+ "3": "Neither agree nor disagree",
188
+ "4": "Somewhat agree",
189
+ "5": "Strongly agree"
190
+ }
191
+ },
192
+ "statement_2": {
193
+ "title": "Statement - Confidence in Editing Machine Translations",
194
+ "prompt": "Rate the following statement: I feel confident in post-editing translations produced by MT systems.",
195
+ "options": {
196
+ "1": "Strongly disagree",
197
+ "2": "Somewhat disagree",
198
+ "3": "Neither agree nor disagree",
199
+ "4": "Somewhat agree",
200
+ "5": "Strongly agree"
201
+ }
202
+ },
203
+ "statement_3": {
204
+ "title": "Statement - Post-editing or Translating from Scratch",
205
+ "prompt": "Rate the following statement: Without access to a translation memory, I would generally choose to post-edit MT over translating from scratch.",
206
+ "options": {
207
+ "1": "Strongly disagree",
208
+ "2": "Somewhat disagree",
209
+ "3": "Neither agree nor disagree",
210
+ "4": "Somewhat agree",
211
+ "5": "Strongly agree"
212
+ }
213
+ },
214
+ "statement_4": {
215
+ "title": "Statement - Post-editing or Imperfect TM",
216
+ "prompt": "Rate the following statement: I would generally choose to post-edit MT over processing good but imperfect (85-94%) translation memory matches.",
217
+ "options": {
218
+ "1": "Strongly disagree",
219
+ "2": "Somewhat disagree",
220
+ "3": "Neither agree nor disagree",
221
+ "4": "Somewhat agree",
222
+ "5": "Strongly agree"
223
+ }
224
+ },
225
+ "statement_5": {
226
+ "title": "Statement - Post-editing MT or Human Translation",
227
+ "prompt": "Rate the following statements: - I would generally choose to post-edit machine translations over human translations",
228
+ "options": {
229
+ "1": "Strongly disagree",
230
+ "2": "Somewhat disagree",
231
+ "3": "Neither agree nor disagree",
232
+ "4": "Somewhat agree",
233
+ "5": "Strongly agree"
234
+ }
235
+ },
236
+ "statement_6": {
237
+ "title": "Statement - MT for Known Languages",
238
+ "prompt": "Rate the following statements: - I often use MT for languages I know outside of work.",
239
+ "options": {
240
+ "1": "Strongly disagree",
241
+ "2": "Somewhat disagree",
242
+ "3": "Neither agree nor disagree",
243
+ "4": "Somewhat agree",
244
+ "5": "Strongly agree"
245
+ }
246
+ },
247
+ "statement_7": {
248
+ "title": "Statement - MT for Unknown Languages",
249
+ "prompt": "Rate the following statements: - I often use MT for languages I don't know outside of work.",
250
+ "options": {
251
+ "1": "Strongly disagree",
252
+ "2": "Somewhat disagree",
253
+ "3": "Neither agree nor disagree",
254
+ "4": "Somewhat agree",
255
+ "5": "Strongly agree"
256
+ }
257
+ },
258
+ "pe_opinion": {
259
+ "title": "Post-editing opinion",
260
+ "prompt": "What is your opinion overall of post-editing machine translation as part of your translation work? Please, feel free to comment about technical aspects as well as opinions and feelings."
261
+ }
262
+ }
questionnaires/pretask_results.csv ADDED
@@ -0,0 +1,26 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ time,translation_direction,main_task_modality,pretask_translator_id,main_task_translator_id,mother_tongue,mother_tongue_other,language_combination,language_combination_other,current_position,current_position_other,english_level,translation_experience,pe_proficiency,pe_experience,pe_percentage,catt_experience,mt_statements,mt_statements_other,statement_1,statement_2,statement_3,statement_4,statement_5,statement_6,statement_7,pe_opinion
2
+ 133,eng-ita,oracle,t1,oracle_t2,ita,,eng-ita,,fulltime_freelancer,,C2,7.5,1,7.5,0.2,5,"like_A,like_B",,4,5,3,4,3,3,4,"Post-editing translation can be a useful instrument when it comes to fine-tuning a technical document. On the other hand, if the content is very articulated and its syntax and context are tricky, machine translation can become a real nuisance, since it is not able to infer from certain contexts yet. At the very end, it all depends on the machine translation output quality."
3
+ 158,eng-ita,unsupervised,t2,unsupervised_t3,ita,,eng-ita,,fulltime_freelancer,,C1,7.5,1,3.5,0.8,5,"like_A,like_D,dislike_A",,5,5,4,2,2,2,5,"From my point of view, MTPE is a helpful tool for linguists, allowing them to focus on the more context related part of their translation projects. it is useful especially when translating short sentences, even if MT does not recognize a correlation between related sentences in different segments. It indeed forms grammatically correct sentences but does not see the potential meaning hidden behind words, that’s why sometimes the result cannot sound as natural as a human translation. It transfers texts into target languages but can’t be creative. It does not localize texts to adapt it to the culture of the target audience. It transfers words but cannot rewrite the text to imply a meaning instead of simply saying it. Overall, on the one hand, MT helps translators improving speed, consistency and effectiveness but, on the other hand, it does not grasp context, idiomatic expressions, and cultural nuances. Personally, I find it an essential foundation to build my translations on. It saves me time, but I believe that a careful review process is fundamental to deliver a high-quality target-centred result. "
4
+ 76,eng-ita,oracle,t3,oracle_t3,ita,,eng-ita,,fulltime_freelancer,,C2,3.5,1,3.5,0.8,5,"like_A,like_D",,5,5,5,4,3,1,4,"I find post-editing machine translation to be extremely useful, as it enables me to manage larger volumes of work efficiently while dedicating more attention to complex linguistic nuances. This allows me to work in a faster and more productive way in many translation tasks. However, there are instances in which the creativity of human translation is irreplaceable, especially in marketing texts, in which style and tone are paramount. In such cases, I prefer to translate from scratch, as it gives me the freedom to be more creative and ensure the message resonates perfectly with the target audience."
5
+ 169,eng-ita,supervised,t4,supervised_t3,ita,,eng-ita,,fulltime_freelancer,,C1,10,1,3.5,1,5,"like_A,like_D,dislike_A",,5,5,2,4,1,3,3,"What comes to mind is that, even though I never stopped reading in my free time, I feel that, over the years, the constant use of MT has somehow reduced my problem solving skills, creative thinking and ability to produce translation alternatives in terms of syntax and terminology. I believe the drastic decline of output quality in any given translated advertisement and marketing materials I happen to see on TV or over the Internet may be due to translators fear (or maybe not enough paid time) to detach from the original, once a MT translation has been unanimously approved within a translation team. This was true when I first started working with MT and got worse over time, especially when working with big translation agencies and teams. On one hand, this standardization has undoubtedly improved consistency for certain copy types, while on the other hand it has produced a consistent decline in quality, making us translators less and less creative and independent from it. "
6
+ 252,eng-ita,unsupervised,t5,unsupervised_t2,ita,,eng-ita,,fulltime_freelancer,,C1,10,1,7.5,0.6,4,"like_A,like_D,dislike_A",,5,5,3,3,4,1,5,"I view it as an opportunity for translators to work with this technology. Of course, much depends on the subject matter of the translation project, language pair and quality of the MT output. Adaptive MT is much improved."
7
+ 167,eng-ita,supervised,t6,supervised_t2,ita,,eng-ita,,fulltime_freelancer,,C1,10,1,7.5,0.2,5,"like_A,like_C,like_D,like_E",,5,5,4,4,2,3,4,"Generally speaking, I think that MT is a helpful tool because it speeds up the translation process, especially when the content is repetitive and technical, as it often includes glossaries and translation matches. So, I don't need to translate the content from scratch and I can just post-edit the translations proposed. However, MT is less helpful when content is creative and contains wordplay, idioms, jargons, aso because most of the time, it translates them literally or wrongly. In such cases, I prefer to use dictionaries or other tools to double check the meaning. In general, I work on Matecat, but I often use Deepl to post-edit translations because I can rework them by checking synonyms, changing the structure of the sentence, checking the dictionary, choosing the ToV, also. In this way, I can quickly and easily improve my translations. "
8
+ 88,eng-ita,unsupervised,t7,unsupervised_t1,ita,,eng-ita,,fulltime_freelancer,,C1,2,1,2,0.6,4,"like_A,like_B,dislike_A",,5,5,3,3,3,1,4,"I don't believe those who say ""the machine will replace humans"" or ""the profession of translator will disappear."" 1, in part the last statement is true but I believe that, as in any technological evolution in history, a technology leads to the evolution of a profession and I think we should not fear the progress that the machine is making. We should not perceive the machine as a threat but an ""opportunity"" to focus in other aspects of translation."
9
+ 89,eng-ita,supervised,t8,supervised_t1,ita,,eng-ita,,parttime_freelancer,,C1,10,1,3.5,0.4,4,"like_A,like_B,like_D,like_E",,5,5,4,4,3,4,3,"Machine translation provides an excellent basis for translation work. The functionalities offered by these technologies make it possible to increase the quality of translated texts, especially in terms of uniformity and consistency, and particularly when adherence to a specific glossary is required. The human mind can freely interact with the machine's results, improving readability and fluency, based on the specific context of each text, the required tone of voice and the most appropriate style. It is therefore not a matter of replacing human work with machine translations, but of finding the right balance between the automatic results and the individual translator's ability to understand the source language and localise it for the target audience."
10
+ 487,eng-ita,no_highlight,t9,no_highlight_t3,ita,,other,Both English to Italian and Italian to English,parttime_freelancer,,C2,10,1,3.5,0.4,3,like_C,,5,5,4,3,3,3,4,In reality I don't have a strong opinion on this. I feel confident post-editing both MT work or human one. Often MT work can provide a different creative input but that not necessarily (at least in my experience) constitutes a time saving solution.
11
+ 220,eng-ita,no_highlight,t10,no_highlight_t1,ita,,eng-ita,,fulltime_freelancer,,C1,3.5,1,3.5,1,4,"like_A,like_D,like_E,other",,4,5,5,3,4,3,3,"I think post-editing surpasses translation from scratch for documents that require a lot of consistency and on large volumes of work as long as it is done with great care and precision. Translation memory or not, I always note those terms that require consistency, for me quality always comes first."
12
+ 241,eng-ita,oracle,t11,oracle_t1,ita,,eng-ita,,fulltime_freelancer,,C2,7.5,1,7.5,0.6,3,"like_A,like_D,dislike_A",,5,4,2,4,2,3,1,"I think that post-editing machine translation can be very useful to be more productive and to work faster, especially for repetitive work that requires consistency and in case of tight deadlines. However, also with the help of MT, the work of a professional translator is (and always will be :) ) necessary in order to deliver top-quality translations."
13
+ 257,eng-ita,no_highlight,t12,no_highlight_t2,ita,,eng-ita,,parttime_freelancer,,C1,10,1,2,0.2,4,"like_A,like_D,dislike_A",,3,4,2,2,2,1,4,"""It could be very challenging, as sometimes terminology is not correct or consistent. Also, I noticed that sentences are not that natural, and after a while I tend to loose the ability to produce a """"normal"""" or good quality text. That's why I need to break big MTPE jobs into smaller bits: this helps me to write in a natural and fluent way. Personally, I sometimes use MT to get an overall overview of a text prior to accept it."""
14
+ 50,eng-nld,,t0,,Dutch,,eng-nld,,fulltime_freelancer,,C2,10,1,3.5,0.4,4,"dislike_C",,5,5,4,2,1,3,3,"The biggest problem with post editing machine translation for me, apart from the translations being poor and not adapted to the target market, is that they're inconsistent: tone, formal/informal (je/jij and u), terminology etc."
15
+ 219,eng-nld,no_highlight,t1,no_highlight_t1,nld,,eng-nld,,other,"Full-time freelance translator, copywriter and journalist",C1,10,1,10,0.4,4,"like_A,like_B,dislike_A",,5,5,2,2,2,2,2,"It's an integral part of the job, and one I don't mind at all. Sometimes an MT gets you further than a human translation, as it tends to be a more exact translation. However it can be quite a bit too literal and leaves no room for transcreation, which is also quite important in the work."
16
+ 199,eng-nld,unsupervised,t2,unsupervised_t2,other,"Dutch, Italian, English",nld-eng,,fulltime_freelancer,,C2,7.5,1,3.5,0.6,3,"like_A,like_B,like_D,like_E,dislike_C",,4,4,4,4,2,2,3,"I love its potential to speed up the work that needs to be done. However, in many programs like MateCat it's trickier to make the sentences or parts of the sentence match in a coherent way. When dealing with long sentences it's often easier to rely on one's own (human) translation capabilities because once the sentences are broken up, their syntax and word order often no longer makes sense in the target language."
17
+ 219,eng-nld,unsupervised,t3,unsupervised_t3,nld,,eng-nld,,fulltime_freelancer,,C2,10,1,3.5,0.4,5,"like_A,like_B,like_D",,5,5,3,3,2,4,4,"I believe that MTs can speed up large-scale translation projects and provide consistency when approved translations are used for this purpose. At the same time, context and/or reference documents must be provided as well to ensure that the MTs are used and post-edited properly within the required context. As for technical aspects, propagation of approved/edited segments to 100% matches should be part of the program or platform that is used."
18
+ 71,eng-nld,oracle,t4,oracle_t1,nld,,eng-nld,,fulltime_freelancer,,C1,7.5,1,7.5,0.8,5,"like_A,like_B,like_D,like_E",,5,5,4,4,3,3,1,"I really enjoy doing this for more product descriptions and more technical translations. I do a lot of legal work and MT can be a big help. I loose less time with translating the repetitive, easier parts, I can concentrate more on the correct terminology,..."
19
+ 90,eng-nld,no_highlight,t5,no_highlight_t2,nld,,eng-nld,,fulltime_freelancer,,C2,10,1,3.5,0.4,5,"like_D,dislike_A,dislike_C,dislike_D",,5,4,2,1,1,1,4,"MT advocates mostly promote the increased productivity of using MT. While MT does increase productivity, other, more negative aspects are often overlooked. First, translating while using MT requires a different skill set from regular translation, i.e. you are a translator & reviewer at the same time. Not all translators are good reviewers. Second, translating while using MT tends to be a lot more tedious than regular translation. Third, MT is often applied without taking the type of source text into account. Not all content is suitable for MT. Fourth, MT rates are usually lower than the rates for regular translation. Combined with the third aspect mentioned above, translators may have to comprise on quality just to stay within budget. Fifth, MT tends to play havoc with tags, punctuation, placeholders, etc. Correcting this type of errors is time-consuming & error-prone."
20
+ 416,eng-nld,supervised,t6,supervised_t3,nld,,eng-nld,,fulltime_freelancer,,C1,7.5,1,7.5,0.8,5,"like_A,like_D",,5,5,1,2,3,2,4,"When the output of the MT is good, it increases my productivity. Especially self-learning MT improves consistency across files, which is a plus. It does sometimes cripple my creativity, because seeing a more or less ready translation tends to focus my brain in that direction, making it harder to divert from it completely."
21
+ 152,eng-nld,unsupervised,t7,unsupervised_t1,other,"Dutch, but also fluent in English.",eng-nld,,other,I would say full-time freelance translator but my availability can differ per week/month.,C2,7.5,1,3.5,0.4,3,"like_A,like_B,like_C,like_D,like_E,dislike_C,dislike_D,other","It really depends on the quality of the output, but I cannot deny that there are advantages to using MT. However, a human touch is very often still required so it's best to always be vigilant I think.",5,5,5,3,2,3,3,"""It definitely has benefits, just for the mere fact that you have a translation (of whatever quality) to begin with. I like working with it, but the truth is that you should always remain extra alert of errors because there are often strange errors that are 'logical' to a machine but make no sense to humans. The benefit of doing a translation 'from scratch' is the fact that you are much more in touch with the entire text, whereas with PE there is the risk that you gloss over things, because it is so 'easy' to oversee something because it was pre translated; in particular with repetitive segments an extra sharp focus is needed when it comes to MT (PE) content. In general the rate for PE is often quite low and sometimes the workload is quite high if the quality is poor. Human output is overall better (of course), but I am a fan of the technology and the possibilities it provides. """
22
+ 119,eng-nld,supervised,t8,supervised_t2,nld,,eng-nld,,fulltime_freelancer,,C2,10,1,10,0.6,3,"like_B,dislike_C",,4,5,3,1,4,1,4,"I'm generally not fond of using MT for work-related tasks, but sometimes it can help speed up the post-editing process when there is much text to review. I would occasionally use it to see if I can get a better translation for a certain phrase or expression, and adapt the grammar accordingly if I find a somewhat suitable translation. "
23
+ 233,eng-nld,no_highlight,t9,no_highlight_t3,nld,,eng-nld,,fulltime_freelancer,,C2,10,1,7.5,1,4,"like_B,like_C,like_D,like_E",,5,5,5,1,1,5,4,"I almost always make use of machine translation, but I wouldn't necessarily call what I do 'post-editing'. With DeepL, for example, you can have the MT rephrase any sentence in multiple ways, allowing you to search for the right word and the best construction. This, combined with online dictionaries (Van Dale), in-context translation websites (Linguee, Reverso), and general web searches, ensures the translator remains fully in control — far from being a 'slave to the machine'. These are just tools to aid the process."
24
+ 250,eng-nld,oracle,t10,oracle_t3,nld,,eng-nld,,fulltime_freelancer,,C2,10,1,3.5,0.6,4,"like_A,like_D,other","I don't like using MT because of its lack of cultural understanding. Unlike human translators, machines struggle to grasp cultural nuances, idioms, and expressions. ",5,5,5,4,3,5,5,"""One of the primary advantages of MTPE is its ability to enhance efficiency, facilitating swift translation production while significantly reducing my workload. By participating in the post-editing phase, I can focus on enhancing the quality of the text rather than initiating the translation process from the beginning. This approach streamlines the translation workflow, leading to greater productivity. On the other hand, achieving accuracy is one of the foremost challenges in machine translation, with errors frequently occurring in idiomatic expressions and cultural nuances. Additionally, the lack of cultural insight poses a significant hurdle, as language is deeply intertwined with culture, making it difficult for machines to fully understand idiomatic phrases and cultural contexts. Lastly, machine translation is often inadequate for handling specific text types, particularly those that contain specialized jargon or technical terminology. A major strength of AI translation lies in its relentless ability to learn and grow. Through ongoing analysis of training data, these systems refine their accuracy and remain attuned to the constantly shifting world of language."""
25
+ 275,eng-nld,oracle,t11,oracle_t2,nld,,other,Italian to Dutch,fulltime_freelancer,,C2,10,1,3.5,0.4,5,"dislike_A,dislike_B,dislike_C",,4,5,2,2,1,3,3,"Currently my work consists for the most part (75%) of Italian-Dutch translations in the technical sector/automotive industry. The MT projects for now always severely lack in quality, resulting me having to work more for lower rates. So for the moment I cannot be considered a big fan of post-editing machine translations, on the contrary, but I'm well aware that the evolution is inevitable and that it only can be improved through human contribution."
26
+ 438,eng-nld,supervised,t12,supervised_t1,nld,,eng-nld,,fulltime_freelancer,,C2,10,1,7.5,0.6,4,"like_A,like_C,like_D",,5,3,1,1,1,3,5,"It makes the job easier, but I also worry that it may eventually replace me."