Ezdi MT Training (Updated)
Ezdi MT Training (Updated)
Ezdi MT Training (Updated)
Transcription Training
Manual Transcription Training
with pre segmented audio and tagging
Timestamps Segment
Type Label
No speaker label
required for Music or
Noise segments
You may click on the Topic Names
Checking the dropdown menu to check that you agree
Topic(s) of 8kHz with the chosen topics against the subject
of the audio
files
Correcting Speaker
Names (IDs) in 8kHz files
• Speaker names are generated automatically in
8kHz files.
• Please ensure that the pre-selected Left and Right
speakers in 8kHz files refer to the correct speakers
by listening to the audio, and not by looking at
the audio bar.
• You will need left and right speakers on your PC,
or a headset, or earphones, in order to hear
which is Left and which is Right.
• You can correct this by using the ‘Link Speaker’
icon or segment by segment as you go.
‘Link Speaker’ in 8kHz
This ‘Link Speaker’ icon opens this box where you can link a Speaker to a channel. After listening through left
and right speakers, a headset, or earphones, you will be able to tell which channel on the audio bar is left, and
which is right. Once confirmed, you can link Channel 1 to Left/ Right, and Channel 2 will default to the other
speaker. This will change the channel names from Ch1 and Ch2 to Left and Right, and enable speaker accuracy
and consistency throughout the file.
✓ Label a segment Speech for any speech from one to two intelligible
foreground speakers, even if it is only for 1 filler word, regardless of
how short it is and up to 15 seconds.
✓ Label a segment Music for audio that consists of music, songs,
singing, or musical instruments.
✓ Label a segment Noise for any noise (breathing, coughing, and non-
human noises like ringing, beeping sounds) that lasts over 1 second.
✓ Label a segment Babble for audio that consists of speech or isolated
vocal noise (coughing or laughing) from one or more background
Types of speakers (people standing nearby, or in the same room), even if the
speech is partially intelligible.
Segments in × Do not label segments Overlap in 8kHz files. If you have an overlap in
speech, duplicate the segment, ensuring the segment label and
8kHz speakers are correct.
× Ignore noises that are less than 1 second in length (including human
vocal noises such as breathing, coughing, and non-human noises like
ringing, beeping sounds, etc.).
× Ignore continuous stretches of silence or white noise that lasts 2 or
more seconds at the beginning, in the middle, or at the end of the
audio files.
NB: No use of X Overlap segments and overlap tags are NOT allowed in 8kHz files.
Overlap ✓ In 8Khz files all overlaps are dealt with transcribing the other
segments or speaker into the duplicate segment provided. Should there be no
duplicate segment for this, you may create one.
overlap tags in
8kHz
How to duplicate and
create a new segment
• If you need to create a missing segment,
please duplicate the segment before where it
should be.
• If, as in this example, you want to create a new
segment between Segment A and Segment B.
• First, click on Segment A, then press Ctrl+Alt+F
to duplicate it.
• As in the opposite image you will see 2
resulting identical segments.
• Ensure you choose the correct label type for
each segment.
SixteenkHz Files
Click on the Resume button on your file in
the Worklist to open the file. Allow the file
to open completely before starting the
following actions.
Inside a 16kHz Transcription File Speakers
Comments
Shortcuts
Query
User Guide 2 Guidelines Box
1 Audio Channel
Segment
Timestamps Type Label
• Label a segment Speech for any speech from 1 to 2 intelligible foreground speakers,
even if it is only for 1 filler word, regardless of how short it is and up to 15 seconds.
• Label a segment Music for audio that consists of music, songs, singing, or musical
instruments.
• Label a segment Noise for any noise (breathing, coughing, and non-human noises
like ringing, beeping sounds) that lasts over 1 second.
• Label a segment Babble for audio that consists of speech or isolated vocal noise
Types of (coughing or laughing) from one or more background speakers (people standing
nearby, or in the same room), even if the speech is partially intelligible.
• Label a segment Overlap for audio that consists of overlapping speech between 2+
16kHz Files • Ignore noises that are less than 1 second in length (including human vocal noises
such as breathing, coughing, and non-human noises like ringing, beeping sounds,
etc.).
• Ignore continuous stretches of silence or white noise that lasts 2 or more seconds
at the beginning, in the middle, or at the end of the audio files.
Summary of overlapping speech in 16kHz
• Overlaps between 2 foreground speakers:
Speech segment label, transcribe 2nd speaker <overlap>inside</overlap> of
Overlap tags, no space directly after or before the tags.
19
Overlap Tags in 16kHz Files
• Overlap tags should be used in 16kHz files Example:
only, within a Speech segment, regardless of
the length of the overlap.
[music] It's, it's unbelievably scary, #uh, because, you
• Words should not be broken up with the know, <overlap>you've got ((all these)) fights going
<overlap></overlap> tags (initialisms are
on.</overlap>
treated as words).
• If the overlap begins in the middle of a word,
place the <overlap> tag before the word. If
the overlap ends in the middle of a word,
place the </overlap> tag after the word.
• When a segment contains an opening
<overlap> tag, it must also contain a closing
</overlap> tag.
Overlap labelled segments do not save ANY text, so please pay
attention to when they should be used:
X Do not use the overlap segment label for overlapping speech when
you can hear what the 2 target speakers are saying.
✓ In this case, transcribe each speaker using overlap
(<overlap>2nd speaker’s speech</overlap>) tags around the
Use of second speaker’s speech.
Mispronounced Words
Mispronunciations should be transcribed using
the correct standard spelling.
• Transcribe speech as it sounds, Examples:
even in cases when a word, or
phrase, does not conform to the "He been done work." =
standard grammar of the language. "He been done work."
Examples:
Individually
Spoken Examples:
• Use tildes to indicate truncated words, whether at the beginning or the end.
• "Ale… alexa … stop the mu… the music." = "Ale~ Alexa, stop the mu~ the music."
• "...lexa play Janet Jackson… no wait…" = "~lexa, play Janet Jackson. No, wait."
• "N… n… no. It's Ch… Chom… Chomsky who said that." = "N~ n~ no. It’s Ch~ Chom~ Chomsky who said that."
Tagging
1 Non Speech/ Noise Tags
Please use the following non speech tags where these sounds occur, Examples:
but never inside of a word. Tag shortcut ‘1’ inside of a segment will • If a non-speech sound occurs in the middle of a word, add the tag
show a dropdown list with the following tags, in this order: exactly before the word in which it occurred.
• [no-speech] No speech
• [bg-speech] Background speech "I will abso-(ring)-lutely open it" = "I will [ring] absolutely open it."
• [beep] Replaces profanity or classified info • If a non-speech sound occurs repeatedly, represent it only once.
• (()) Unintelligible
"Wait … click click click click there" = "Wait [click] there."
• [lipsmack] Lipsmacks, tongue clicks
• [breath] Breathing in and out, yawning
• [cough] Coughing, throat clearing, sneezing
• [laugh] Laughing, chuckling
• [click] Machine or phone click
• [ring] Telephone
• [dtmf] Dialing on a telephone keypad
• [sta] Static, at start of continuous bg noise
• [cry] Crying, sobbing
• [music] Fore or background music
• [noise] Other noise not covered in this list
• [applause] Clapping
If a sound is continuous throughout the file (like music, or an echo)
please ignore this, no tag is required.
2 Filler Words
Filler words are "words" that speakers use to indicate hesitation, Tag shortcut ‘2’ will show a dropdown list with the
or to fill a pause in order to maintain control of a conversation
while thinking of what to say next. pre-determined filler words for your language.
• Each language has a limited set of filler words specific to This example shows the list of 5 English filler words:
that language. Only this pre-determined list of filler words,
preceded by the hashtag, should be used.
The # tag is only to be used for the pre-determined filler words. If you are not
Please do not add # in front of other words that may sound like transcribing
filler words but are not in this list. English, please
• Do not alter the spelling of filler words to reflect how the check your own
speaker pronounces the word. If the speaker says a filler language
word that does not match any of the listed filler words, use guidelines for your
the filler word that is the closest match.
specific list of filler
• Filler words are not to be confused with interjections. words.
• In particular, the filler word "#hm" is not to be confused with
the interjection "hmm". Use context to disambiguate the two
different uses.
3 Markup Tags
Non-speech and other markup tags must remain in English as
shown below:
Tag shortcut ‘3’ will show a dropdown list that includes the
following main tags:
• <initial></initial>
• <lang:Foreign></lang:Foreign>
• <lang:X></lang:X> where X can be replaced by a language
name starting with a capital first letter (e.g. Arabic)
• <lang:English><initial> </initial></lang:English> the English
Initial Tag: English initials must be tagged within an Initial
tag within a Foreign language tag.
• They should be transcribed as words in upper case with no spaces or periods between the letters.
• "I work for NASA." = "I work for NASA."
• "AIDS has a great impact on society." = "AIDS has a great impact on society."
• Initialisms refer to terms spoken as a series of letters (e.g., IBM, IMDB, HTTP). They should be written as
• upper case letters, but enclosed within the <initial> and </initial> tags.
• "I work for IBM." = "I work for <initial>IBM</initial> ."
and • Use periods only for initials standing for given names (e.g. E. B. White, George W. Bush).
• "George W Bush paints now" = "George <initial>W.</initial> Bush paints now."
Initialisms
• Do not include plural markers (e.g., -s) or possessive marker ('s) within <initial></initial> tags.
• "Welcome to the Ordinary Wizarding Level Examinations. O. W. L.s. More commonly known as Owls." =
• "Welcome to the Ordinary Wizarding Level Examinations. <initial>OWL</initial>s. More commonly known
as Owls."
• "George W's dog was a Scottish Terrier." = "George <initial>W.</initial>'s dog was a Scottish Terrier."
• Initialisms are treated as words. Do not break an initialism up with tags and don't include any other tags
• within the <initial></initial> tags.
• "I'll be taking my S (cough) AT next month." = "I'll be taking my [cough] <initial>SAT</initial> next month."
• The word "OK"/ "okay " is always transcribed as "okay."
• Spoken individual letters (e.g., proper names that are spelled out) are not initialisms and do not need the
<initial></initial> tags.
Non-Target Languages
• Any foreign language should be placed in a foreign language <lang:Foreign> tag at the location where the switch between the languages begins and </lang:Foreign> where the
switch ends.
• When a segment contains the opening <lang:Foreign> tag, it must also contain the closing </lang:Foreign> tag.
• If you can identify the non-target language, replace "Foreign" with the Language name in the tags. Capitalize the first letter of the language name.
• If you understand the non-target language, please transcribe between the tags with no spaces. Otherwise, transcribe the non-target language as (()) with no spaces.
• "You have to finish <lang:Spanish>todo esto, porque</lang:Spanish>. I have other things to do."
• "I'd like to tell her <lang:Foreign>(())</lang:Foreign>."
• Words of non-target language origin adopted into common use in the target language (loanwords) should be transcribed as target language.
• Words should not be broken up with foreign language tags. This is rare, but in cases where a speaker mixes languages within a single word, such as the first part of the word in the
non-target language and the last part in the target language:
• The word should be transcribed as it is pronounced, using the correct spelling in each language.
• Enclose both the first and last part within the <lang:Foreign></lang:Foreign> tags.
• Non-target language tags can be used in conjunction with other markup tags (e.g. <initial></initial> and <overlap></overlap>)
• "The story is set in Belarus after the collapse of the <lang:Russian><initial>СССР</initial></lang:Russian>. Well, that's <initial>USSR</initial> in Russian."
• "I'll sometimes start a sentence in Arabic <lang:Spanish>y termino <overlap>en español</overlap></lang:Spanish>."
Special Characters
Troubleshooting •
•
Internet speed check: www.speedtest.net
Guidelines: if you need to remind yourself of a particular rule in the
Guidelines, open them and press Ctrl+F, enter a keyword and search for
what you need.
• Spell Check, for English, please install the Chrome extension ‘Language
Tool’: https://chrome.google.com/webstore/detail/grammar-and-spell-
checker/oldceeleldhonbafppcapldpdifcinji?hl=en
• Or you can search here:
https://chrome.google.com/webstore/category/extensions for
spell check extensions for your own language. Please remember
that spelling and grammar remain your responsibility regardless
of whether or not you use one of these tools.
Comments Box
• The comments box is found on the top right
of your transcription screen.
• Please add a comment to a file that you wish
people to see in order to reject the file, to not Comments
reassign it to you, or to just put a general
comment about quality or anything else that
you experienced in the file.
• Our project managers can view these
comments, where as only the tech team can
view your queries.
How to send a Query
to the Tech Team
• It is possible that some of your files may be returned for rework from QA
• In this case the file will be reassigned to you and you should receive a notification, either an
email or a WhatsApp message, confirming that the file has been reassigned to you and that it
requires rework.
• If the notification is not clear about what errors require fixing, and it is not obvious from looking
at the file, please do check with a project manager so that you receive the correct instructions.
• Never re-send a file to QA without doing any rework.
• Once you are done with your rework file, please ensure that you know where your project
manager would like you to send the file (if anywhere - they may want to collect the file).
Thank you and we hope you enjoy
working on this project