Captioning and Transcript Workflow
•Download as PPTX, PDF•
0 likes•877 views
Sage Publishing's workflow for captioning content. An in-depth walkthrough of how they use 3Play Media.
Recommended
More Related Content
Similar to Captioning and Transcript Workflow
Similar to Captioning and Transcript Workflow (20)
More from 3Play Media
More from 3Play Media (20)
Recently uploaded
Recently uploaded (20)
Captioning and Transcript Workflow
- 1. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne Captioning and Transcript Workflow Jerry Orvedahl Manager, Online Content Analysis Publishing Technologies October 2, 2018
- 2. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne Agenda • About SAGE • SAGE Accessibility • The Deliverables • Infrastructure and Partners • Workflows • Questions
- 3. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne About SAGE Publishing • Founded in 1965 • The largest social science publisher • The fastest growing STM publisher • Building Bridges to Knowledge • Teaching, Learning, Research, & Practice
- 4. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne Committed to Accessibility • Accessibility Working Group • Revamping our workflows to accommodate ATLD • Finalist, Digital Book World’s “Innovation in Accessibility Award”
- 5. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne Committed to Accessibility • Accessibility Working Group • Revamping our workflows to accommodate ATLD • Finalist, Digital Book World’s “Innovation in Accessibility Award” - Amazon Alexa - DAISY Consortium - Google Assistant - Novel Effect
- 6. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne The Deliverables
- 7. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne The Deliverables
- 8. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne The Deliverables
- 9. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne The Deliverables
- 10. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne The Deliverables
- 11. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 12. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne Infrastructure and Partners “Microscope” (2015) “SOCR” CMS Orbis Technologies RSuite Brightcove (2010) 3PlayMedia (2013) “Retriever” DAM (2014) Northplains Telescope
- 13. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 14. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 15. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 16. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 17. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 18. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 19. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 20. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne
- 21. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne The Bare Minimum
- 22. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne The Bare Minimum https://players.brightcove.net/ 268012963001/default_default/ index.html? videoId=2586988066001
- 23. Los Angeles | London | New Delhi | Singapore | Washington DC | Melbourne Jerry Orvedahl jerry.orvedahl@sagepub.com (202) 729-1842 Questions?
Editor's Notes
- When I attend a workshop or symposium, I hope to hear presentations directly relevant to my experience, and to come away with a few practical nuggets ... Something actionable to justify the day out of the office and the registration fee. The challenge in talking about workflows … is that publishing houses are highly idiosyncratic. The organizational structures, the cultures, the tools and skillsets at their disposal, the roles and responsibilities are highly variable. I have no expectation that the SAGE environment would translate perfectly to yours. But it’s useful – I hope -- to demonstrate one way of doing things. To share what works well, and where we struggled. Two quick questions …. …. By show of hands, who is already working with 3PlayMedia? Last question, by show of hands, who is using the 3PlayMedia API in their workflows? …. Before getting into workflow I’d like to briefly introduce SAGE and accessibility at SAGE. The deliverables from our workflow. Can’t really talk about the tools, workflows, and processes without first understanding what it is we need to deliver. Once we know what we’re trying to produce, then we can talk about the infrastructure and partnerships available to us. And only then can we talk about the workflow that an asset transits from the time it’s created or licensed, to it’s delivery to the online platform. … Will address one of our workflows. The most complex, the most highly automated, to demonstrate what can be done. …. We’ll talk a bit about the puppy later. Our in-house DAM is known internally as Retreiver. Hence the image.
- One fun fact … SAGE’s DC office is located in the Watergate Office Building. My office on on the 6th floor, site of the DNC office in 1972, at the time of the Watergate break-in. Building Bridges to Knowledge …. Transferring ideas from the mind of a scholar into the mind of a consumer. The consumer of the idea might be a student in a classroom or a library, a researcher, or an education professional. We do that the traditional way: putting print textbooks into the hands of students, and print journals onto Library shelves. We also do that ….
- The DBW conference is under way right now in Nashville TN. Winners will be announced today.
- Plus abstract, segmentation, keywords, scholars ….
- Winners of the Digital Book World awards are being announced today in Nashville, TN.
- SOCR = SAGE Online Content Repository. It is our customized implementation of Rsuite, which is a product of Orbis Technologies. Built on a MarkLogic database. It is designed to secure and distribute digital assets. Brightcove. SAGE has been a Brightcove customer since 2010. Created as a pilot and caught on internally. It supports two very different operating paradigms: 1. Large Reference products highly automated. Rely on APIs. Custom players invoking video via API. 2. Embed code manually created and the iframes embedded in html of web pages, in XML files, in Learning Management System coursepacks. Two years into our experiment -- June 2012 – we had 502 videos in Brightcove. Today, we have 17,229. 3PlayMedia. In 2013 I was tasked with recommending a transcription vendor. I developed a set of requirements based on internal stakeholder interviews, then wrote an RFI and sent it to five prospective vendors, all of them listed on the Brightcove partner’s page. Obviously 3PlayMedia won the award. I liked the cost model, the cost, the quality that I saw in the samples they produced. I liked the intuitive browser-based UI for managing transcriptions settings and the ability to edit transcripts. I liked that they could create captions from transcripts, because I already had 200 transcripts in hand that I didn’t want to go to waste. I appreciated the seamless integration with Brightcove And I noted for the record that 3Play had an API. Little did I know how important that API would become. Still, there were requirements it did not meet. I had a back-office requirement to apportion costs to the appropriate project. The architecture at the time didn’t support that requirement. There was no concept of subaccounts at 3PLay. When you initiated a transcription from the Brightcove side, there was a single keyword – 3play – that you entered into Brightcove’s “tags” metadata field. 3Play’s daemon would pick it up, initiate the transcription, deposit the captions into Brightcove, and charge our 3Play account. When I described this problem to Marc Dunn and Josh Miller, they built the functionality to our specifications at no charge. Here’s the headline … If you need functionality, and it’s not there, ask for it. As an aside, we had another issue come up this past year. Synched transcript widget … Relied on the 3Play ID number. …. They rebuilt to rely on the Brightcove Video ID. We said that’s great, but … We want it to work with the Brightcove Reference ID. It’s under development now. Retriever. As our video exploded, and we began to contemplate video-centric products, we recognized the need for a dedicated Digital Asset Management system. Again, based on stakeholder analysis and an RFP process, we adopted Northplains’s Telescope product. To differentiate our implementation from the out-of-the-box Telescope, we named ours Retriever. Microscope. The architecture of our product demanded a final bit of kit. There was nothing on the market to do what we needed, so we built our own. Called “Microscope.” You might think of it as a packaging tool. We needed some means of packaging the transcript file, the closed captioning files, thumbnail images, and the metadata (as XML) into a zip archive for securing and distribution to the platform. At its heart is a SQL database and a .Net UI.
- Video asset is dropped into a hot folder, for ingestion into Retriever.
- Some metadata are required. One bit of metadata – Product Video Stream – determines whether closed captions will be automatically created. Another bit – Box D Discipline – influences the tag that is sent to Brightcove. A transformation in Retriever generates a manifest for Brightcove, which includes the appropriate 3play tag
- There is a setting in the 3Play API, available at the account level, where you instruct 3Play transcribers how to handle two types of problems: Inaudble audio, and proper nouns they are unsure of. You can instruct 3Play to skip over these problems, or to insert markers in the transcript. Once per day, Retriver checks internally for any videos sent for transcription that are not yet. It creates a list of them, then pings the 3play API for the status of each transcript. If clean, then downloaded. If there are markers, indicating errors, then Retriever generates an email to an internal distribution list. It’s a log of all transcripts at 3Play that need attention. Includes reference IDs for ease of locating them.
- Retriever sends transcripts (vtt, smi, dfxp) to Microscope. Retriever also integrates with FlipFactory. FlipFactory harvests keyframes every 5 seconds. Created as Base 64-encoded images (binary images stored as XML.) Those XML-encoded images are sent to Microscope, which converts them to jpg. A third-party vendor enters metadata into Microscope while viewing videos in Retriever. … Keywords. … Speakers … Abstracts …. Segmentation. Vendor also selects a keyframe for each segment and for the work. Retriever allows the selection of a specific frame; in Brightcove, can only select a timestamp, which might correlate with multiple frames. Microscope has everything it needs to create the zip package: metadata, images, transcript files.
- SOCR writes the third-party vendors metadata back to Retriever, to facilitate discovery and reuse.