Sometimes, a transcription finishes to process in the transcription list UI and when you click, it does not take you to the transcription page, and in the console it shows an error saying the filename in metadata is not defined.
But then if you leave it enough time, after a bit you are able to click again and be taken to the transcription page.
In this scenario it seems to be because in db.js the callbacks from theinterative_transcription_generator returning a transcription, the metadata info, and a video preview file, might not happen the order one would expect. Eg reading the metadata might take longer etc.. And the transcription callback is the one setting the transcription status to true to mark it as done. Which as a result makes the transcription in the transcription list clickable.
One possible solution is to add a few extra status attributes for the individual callbacks to the transcription json model.
Sometimes, a transcription finishes to process in the transcription list UI and when you click, it does not take you to the transcription page, and in the console it shows an error saying the filename in metadata is not defined.
But then if you leave it enough time, after a bit you are able to click again and be taken to the transcription page.
In this scenario it seems to be because in
db.js
the callbacks from theinterative_transcription_generator
returning a transcription, the metadata info, and a video preview file, might not happen the order one would expect. Eg reading the metadata might take longer etc.. And the transcription callback is the one setting the transcriptionstatus
totrue
to mark it as done. Which as a result makes the transcription in the transcription list clickable.One possible solution is to add a few extra status attributes for the individual callbacks to the transcription json model.
eg with default values
Then in "pseudocode" for transcription calllback
for video preview callback
for metadata read callback