Skip to content

Archive for

Weekly Friendly Tips

Monday Friendly Tips to Keep in Mind!

Welcome to the Weekly Friendly Tips post!

Written by fellow CrowdSurfers, these posts are published every Monday and will list the previous weeks most common errors and help with how to avoid making those errors in future tasks!


Monday, September 26, 2016

 

Hello, CrowdSurfers!

1st:

This week’s leader in the FTR Error Board was the issue of words being incorrectly transcribed. Here are just a few examples of what I encountered:

      • Transcribed as: Thank you for having me as a contribution of the team work.
      • Correct Transcription: Thank you for having me as a contributing author to your book.
      • Transcribed as: They could be coming from revet, could be coming from another nervous works model.
      • Correct Transcription: They could be coming from Revit, could be coming from another Navisworks model.

 

One of the nice things about doing FTRs as opposed to just transcription is that most FTRs are long enough to give us some context about what is being discussed. By focusing on what’s being said throughout the entire piece, we can use what we’ve already heard to help us determine whether what’s been transcribed makes sense with regard to what’s being discussed.

2nd:

The second most frequent error I encountered this week was random capital letters sprinkled throughout the transcriptions. Remember, an FTR is a stitching together of several individual transcription tasks. As per CrowdSurf guidelines, each of those transcriptions begins with a capital letter, even if it is not the start of a sentence. For this reason, one of our primary jobs in FTR is to spot those capitalized words that end up being mid-sentence in the final, stitched together product and correct them to lowercase.

3rd:

Hot on the heels of the capitalization issue was timing errors. Remember, if the audio does not match the beginning of the transcription in the yellow (current) box, then the timing is off and needs to be flagged.

Please see this excellent YouTube video for a more in-depth explanation: https://www.youtube.com/watch?v=AaVo_QDUF8A&feature=youtu.be

4th:

And finally, speaker changes. A finished FTR should have speaker change indicators wherever, and only wherever, there is a new human speaker. When reviewing an FTR, it is important to watch for and remove incorrect speaker changes, and also to make sure that there are indicators whenever there is a new speaker.

A very nice explanation of proper speaker changes is included in this YouTube video: https://www.youtube.com/watch?v=pb94R0rjihI

 

Focusing on these issues should help us all to produce the kind of high-quality work that will keep our CrowdSurf clients coming back to re-fill the queues.

 

Peace, Love, Transcription!


For more help with Full Text Review tasks, check out the links below:

Media Minute Bonus

Queues are OVERFLOWING!

This week, make your $Bonus$ earnings the largest earnings yet!

But first, make you sure you carefully review the General Guidelines.

Don’t forget to email us at support@crowdsurfwork.com with any questions you may have and  subscribe to the CrowdSurfWork Newsletter to get alerts on any changes, updates, and other important information!

Check your inboxes regularly! We’re promoting!

Join us on Work Market for the best work experience!

Here’s what you need to know this week:

  • NEW Level 5, 6 & 7 Requirements!!: Read below to learn more about updated requirements
  • Weekly Bonuses will go out by Tuesday 10/4/16 11:59pm PT.

Read more

Transcription Bonus

The Queues Will Make it Hard Not to Smile!

Read more

Weekly Friendly Tips

Super Tips to Keep in Mind!

Welcome to the Weekly Friendly Tips post!

Written by fellow CrowdSurfers, these posts are published every Monday and will list the previous weeks most common errors and help with how to avoid making those errors in future tasks!


Monday, September 19, 2016

Hi CrowdSurfers,

Here are some of the most frequent errors I found while doing FTR, QC and QCR tasks this week and tips on how to fix them:

1st

The biggest problem I encountered this week was that spoken words were not accurately transcribed. It is often easy to put all your focus in reviewing the accuracy of each individual line and ignoring context. However, it’s important to always remember: Context is vital in FTR.

  • While there is a button on the interface that says “Play Until End of Sentence”, I recommend that you pay close attention when using it while working Full Text Tasks.
    For example when you use the “Play Until End of Sentence option” the audio will stop at the end of each line, it may create situations like the examples below. Each of these examples should have been a single sentence:

    • Incorrect: “We cannot just hire them and leave them there. And hope they will learn everything by themselves.”
    • Correct: “We cannot just hire them and leave them there, and hope they will learn everything by themselves.”
    • Incorrect: “And employees should be rewarded for their high performance. So later on, they will be more motivated.”
    • Correct: “And employees should be rewarded for their high performance, so later on, they will be more motivated.”

I also noticed many instances where the speaker would use the word “gonna”, then switch to using the phrase “going to”. Maintaining consistency within a task doesn’t apply to changing all instances to either one or the other. Please leave words as they were spoken.

 2nd

Now brace yourselves, we’re talking commas.

Probably the most frequent error I’m running into is the comma after a conjunction at the start of a sentence. Commas after “And” or “But” are not necessary, especially at the
beginning of a sentence.

3rd

I also ran into multiple instances where commas were placed before the word “is”.

  • “For today’s call, the real important thing that you need to know
    about Section 508, is that for videos and multimedia products.”
  • “Clearly one of the things we have to do, is to make sure we’re giving great feedback to people.”

The comma and when to use it can be confusing, no doubt. Keeping in mind some of these tips can go a long way toward reducing a lot of work for fellow CrowdSurfers down the line.

CrowdSurf has recommended this resource on commas:
https://owl.english.purdue.edu/owl/resource/607/01/

 


For more help with Full Text Review tasks, check out the links below:

Transcription Bonus

Don’t Miss Out on Your Opportunity to Make More $$$!

Read more

Media Minute Bonus

Let’s Keep on Pushing Minutes Through!

Jobs keep flowing in! Helps us keep the queues empty and bring home more $$$ for your wallets! Make sure you familiarize yourself with the

Make sure you familiarize yourself with the General Guidelines before diving into the queues.

Don’t forget to email us at support@crowdsurfwork.com with any questions you may have and  subscribe to the CrowdSurfWork Newsletter to get alerts on any changes, updates, and other important information!

Check your inboxes regularly! We’re promoting!

Join us on Work Market for the best work experience!

Here’s what you need to know this week:

  • NEW Level 5 Requirements: Read below for Level 5 requirements
  • Weekly Bonuses will go out by Tuesday 9/27/16 11:59pm PT.

Read more

Weekly Friendly Tips

Supercharge Your Transcription & Editing Skills

Welcome to the Weekly Friendly Tips post!

Written by fellow CrowdSurfers, these posts are published every Monday and will list the previous weeks most common errors and help with how to avoid making those errors in future tasks!


Monday, September 12, 2016

Hello CrowdSurfers,

Here are the most frequent errors I found while doing QC and Timing tasks this past week.

1st and 2nd:

Tied for the top spot, oddly enough, were two very opposite problems – one word sentences and unbroken run-on sentences.

Please remember:

  • We are transcribing for captioning for hearing impaired individuals so one or two word sentences are not ideal because they would flash by so quickly on the screen.
  • We should always endeavor to combine words or phrases like “okay” or “all right” with the longer sentence that is immediately before or after them. And conversely, a huge, long, run-on sentence is just too much to take in at once.
  • Captions are easier to digest if they’re kept to just a few lines.
  • It is perfectly acceptable in CrowdSurf transcription to start a new sentence with “And”, “Because”, “But”, “So”, “Which”, etc.

Review Guidelines Section Three- Punctuation, Sentence Style & Breakpoints

1. Break up run-on sentences.

2. Join sentence fragments. Hint: Generally 40-60 characters is the optimal sentence length.

Obviously, counting characters is tedious and time-consuming so personally, I normally look for an acceptable break point whenever I have a sentence running two or more lines. There will always be some instances where a logical break simply isn’t possible, but I find those to be the exception.

3rd:

The third most frequent sort of error I encountered this week was an issue of just plain wrong words.

Please remember:

  • It’s very important to have a quiet working environment, free of distractions, as well as a set of headphones or earbuds to do this work well.
    • While some folks use sound enhancement software and fancy gamers’ headphones, I’ve always done quite well with just a fairly inexpensive set of Sony headphones.
  • Pay attention to the subject of the piece so that we can apply some logical, contextual reasoning to figure out words which may not be spoken clearly.
  • Ask yourself, ‘does what I just transcribed make sense?’ If not, perhaps we should give it another listen. It may even be a word or term that was used previously in the piece.

And if we’re dealing with very poor audio, sometimes we really do need to use an [INAUDIBLE] tag. This can be preferable to just blindly plugging in any old words to fill up the space.

4th:

I encountered a number of math tasks where variables were capitalized. Math tasks can be daunting, I know, but there are some very helpful tips in the guidelines for doing them correctly!

Please remember:

  • The only time a math variable would be capitalized is if it is shown that way onscreen or if the speaker specifically indicates that it is “capital” or “big” or “uppercase”.
  • Use lowercase letters for variables in formulas

Review the Abbreviated General Guidelines, Math, Science and Computers

5th:

Speaker changes

Please remember:

  • Each new speaker needs to be indicated by a double right-facing chevron (>>).
  • (>>) are only used to indicate a change human speaker (or human-made sounds like: audience laughter or applause or cough) and should not be used before a sound tag.
  • Sometimes in FTR, there will be speaker change indicators where they don’t belong. We need to remove any incorrect ones that we encounter.

 

I hope these tips have been helpful and will result in you being a happier, more productive CrowdSurfer!

Peace, love and transcription!


For more help with Full Text Review tasks, check out the links below:

Media Minute Bonus

Happy Monday, Let’s Get This Week Started!

Last week was a great week for quality transcripts! Let’s keep up the good work. Check out the General Guidelines or email us at support@crowdsurfwork.com with any questions you may have!

If you haven’t already, please subscribe to the CrowdSurfWork Newsletter to get alerts on any changes, updates, and other important information!

Check your inboxes regularly! We’re promoting!

Join us on Work Market for the best work experience!

Here’s what you need to know this week:

  • NEW Level 5 Requirements: Read below for Level 5 requirements
  • Weekly Bonuses will go out by Tuesday 9/20/16 11:59pm PT.

Read more

Transcription Bonus

Excited for A New Week With YOU!

Read more

Transcription Bonus

 Stay Awesome This Month!

Read more