Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Video Component with existing Transcripts
For all the subsequent transcript uploads, Video Component will request VAL for transcripts via UUID, and VAL will be able to give all the transcripts attached to that UUID. On deleting transcript from the video component, VAL will require the UUID from the Video Component.

Import / Export across the same platform
On the course export, all the transcripts (metadata + content) will be exported with course. On the course import, All the transcript metadata will be back into VideoTranscript data model . We and we can regenerate new UUIDs (which will serve as video_ids) for the imported transcripts , and these will be for video components that do not have an edx_video_id – there will be chance for – This will benefit us when we import/export across the different platforms but there will be transcripts data duplication if we are exporting/importing in a same platform.

Import / Export across the different platforms (e.g. edX to Edge etc)
This is the case when we export a course (for example, from edX platform to edX Edge). On the course export, all the transcripts (metadata + content) will be exported with course. On the course import, there will be no chance that transcripts could conflict with existing records in VideoTranscript data model as we are regenerating new UUIDs for the imported transcripts.

Is this such an often Use Case frequent UseCase that we have to allow data-duplication? (not sure)