User:Aardvark/TranscriptWorkflow: Difference between revisions

	The Portal Transcripts (Transcript Completion Project)
Information
Topic	The Portal Podcast
Leader	pyrope#5830; BeefSandwich27#0143; Aardvark#5610
Start Date	31 January 2020
Methodology	Transcript Workflow
Style Guide	Wiki Page
Portal Media Spreadsheet	Sheet
Google Drive	Drive
Links
Website	The Portal Blog
Discord	Link
The Portal Group Discord	Link
	All Projects

Revision as of 13:33, 26 April 2021

This is the workflow for generating and editing transcripts for The Portal Podcast and other Content by Eric Weinstein. It introduces the tools we use, our style guide, and our process.

Before you start

There are a couple things you should know before starting. Also check that there isn't already a transcript for what you would like to contribute to, using our sheet, the wiki categories, or the blog.

Make accounts

In order to give you access to our transcripts, you'll need accounts with the services we use.

Have a Discord account. Discord is an online chat service where we coordinate our work.
Have an Otter.ai account. We generate our transcripts in Otter, where they can be edited to match speakers to text.
Have a Google account. We use Google Drive and Google Docs to store and coordinate our work.

Contact us on Discord

Contact Aardvark or Brooke on our transcript-focused Discord server or our main Discord server. Say what you'd like to work on and we'll give you access to our Drive folder and the AI-generated transcript in Otter.

Basic Editing Rules

We have developed a style guide to keep our transcripts consistent. Here are the basics.

We use a clean verbatim style. This means filler words (ums/uhs) and repeated words, when they do not add extra meaning (and, and , and ...), are removed.
Add notes in brackets for things that happen in video but don't translate to audio.
No indent on paragraphs
In your text editor, leave an empty paragraph between existing ones
Timestamp on top, italicized, shift+enter for line break (not paragraph break from regular enter)
For speaker tags: full speaker name (first + last), bolded with a colon.
For multiple paragraphs by the same speaker, only the first should have a speaker tag
Add section headings

Be sure to review our style guide for everything in detail with examples.

Editing Process

Some people prefer doing the majority of their editing in Otter, while others prefer Google Docs. Both are necessary, but you are free to use them as best suits your preferences.

Edit in Otter
Edit in GDocs while listening
Edit in GDocs again

Using Otter

Using Google Docs

When finished

Tell us! We'll look it over and put it on the blog.

Paste it onto the wiki. Note that

Timestamps must be followed by a <br> tag to insert the linebreak.
Perform a find/replace operation with each speaker name, replacing the speaker name with the name surrounded by three tick marks. So Eric Weinstein: is replaced '''Eric Weinstein:'''.
Add the necessary markup around section headings. Keep in mind heading levels may differ between the Google doc and the wiki, all that needs to be preserved is.

Also add the transcript blurb template.

For more help on using the wiki, see Wikipedia's guide on Wiki markup and our Wiki Usage FAQ.

If I don't want to continue working on a transcript

Tell us!

@@ Line 18: / Line 18: @@
 We have developed a style guide to keep our transcripts consistent. Here are the basics.
-* We use a clean verbatim style. This means filler words (ums/uhs) and repeated words when they do not add extra meaning (and, and , and ...) are removed.
+* We use a clean verbatim style. This means filler words (ums/uhs) and repeated words, when they do not add extra meaning (and, and , and ...), are removed.
 * Add notes in brackets for things that happen in video but don't translate to audio.
 * No indent on paragraphs