File Naming¶
Each file you prepare for the TPR-DB should represent one session. The TPR-DB backend expects the following naming convention for all log files (Translog-II or Trados Qualitivity) as well as any accompanying files (InputLog files and eye-tracking files).
Naming Convention¶
Session Files Naming Convention
P<participant-number>_<modality-abbreviation><source-text-number>.<extension>
Ex.
P01_T1.xml
Ex.
P09_P22.xml
Ex.
P03_MT35.xml
Ex.
P12_I4.xml
Participant Numbers vs. Source Text Numbers
Note that single-digit participant numbers are expected to start with 0
(e.g., participant 1 = 01).
On the other hand, single-digit source text numbers do not start with 0
(e.g., source text 1 = 1)
Standard Modality Abbreviations¶
The following are standardized modality abbreviations that the TPR-DB will automatically recognize:
T-
from-scratch Translation
P-
Post-Editing of Machine Translation
E-
Monolingual Editing
C-
Text Copying
R-
Translation Revision
D-
Dictation
S-
Sight Translation
MT-
Machine Translation output
I-
Simultaneous Interpreting
ST-
Simultaneous Interpreting with Source Text
A-
Authoring
L-
Reading
LV-
Reading Aloud
U-
Monolingual Summarization
H-
Monolingual Paraphrasing
Custom Modalities¶
If your experiment involves sessions that the standardized modality abbreviations do not adequately describe, then you can use, label, and describe custom modalities when you upload your session files.
Custom Modality Abbreviations
Custom modality abbreviations must be roman alphabetical characters (A–Z) and can be no longer than two characters
Custom modalities can be very useful for organizing different experimental conditions.
Use Case
Let's say that, in some of your experiment's sessions, the participants are post-editing with the help of quality estimation. You could name those sessions using a modality abbreviation PQ.
When you upload to the TPR-DB, you will be prompted to add a label and a description for this custom modality.