File naming procedure (Talk-A-Thon Data)
Participant IDs
In all data documentation, participants in the recordings will be referred to by a code number, to be specified by your supervisor.
General Rules for naming files
-
No spaces - Use underscores instead
-
No dollar signs
-
No percent signs
-
No exclamation marks
Any data derived from a study should include the participant ID in the file name. In addition, depending on the study, the file name should contain additional information that helps the team to know what is contained in the file.
Specific File-naming formats
Type 1: Pilot in-lab-audio recording
ParticipantStudyID_Languages_Age in Months_Recording Format_ Date (YYYYMMDD)_Extra-notes-critical-to-understanding
For example:
PR0001_ECxxx_18_LL_YYYYMMDD_File-corrupted-after-18-minutes
Note that the date in question is the date of recording. Ask the home recording team if you are unsure.
The Language Code:
| Code | Meaning |
|---|---|
| E | English |
| C | Chinese |
| T | Tamil |
| M | Malay |
| O | Others |
Use this format for naming both ELAN and audio files.
PR0001_ECxxx_18_LL_YYYYMMDD_File-corrupted-after-18-minutes.eaf
PR0001_ECxxx_18_LL_YYYYMMDD_File-corrupted-after-18-minutes.wav
Guide to different recording formats
The first position refer to the mic, the second position refers to the recording device:
Mics:
| Code | Meaning |
|---|---|
| A | Aputure A.lav (Lapel Mic) |
| B | Brittany (Lapel Mic) |
| L | Lena integrated Mic |
| S | Shotgun |
| Z | Zoom Integrated Mic |
Recording Units:
| Code | Meaning |
|---|---|
| L | Lena (make sure to give unit number) |
| Z | Zoom (make sure to give the rec unit number) |
| P | PC (make sure to keep notes about which computer and which software were used) |
Other Files
For other notes on the files, you should include them in a separate ReadMe file. For example:
00_ReadMe_FileHandlingNotes.markdown