Transcription json
Last updated
Last updated
In this section we are looking at the Transcription JSON schema used in autoEdit.
Connected to this is defining a schema for transcription, to make sure all components that work with this have a defined interface/specification. Eg
example.
example. As well as their and documentation.
pocketsphinx plain text.
An array of words object, to represent lines this could also be a nested array of word objects.
Where the word object at a minimum as a start, end time and text attribute.
However the blocker for now is that changing the data structure for transcription at this stage would involve a pretty substantial refactor.
autoEdit JSON Transcription schema at a high level it models the objects present in a transcription.
In this representation:
Transcription
Paragraphs ← speaker
Lines
Words
Speakers are associated to paragraphs. Paragraphs are treated as sections of lines.
A list of speakers can also be kept separate, similarly to how IBM Watson stt API returns the results of speaker diarization.
Name of paragraph and line attribute are ambiguos. It should be lines and words instead(?).
This is a bigger refactoring but instead of array data structure, could use hash/dictionary.
This way id is the key. and can make use of key value methods available in js. Lookup speed would improve(?) and could easily get array of values using js method.
considered the to make use of React component, built on top of Draft.js to improve the word correction feature.
.
