Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle assignments created with a YouTube URL using the regular URLPicker #5499

Closed
acelaya opened this issue Jun 16, 2023 · 1 comment · Fixed by #5503
Closed

Handle assignments created with a YouTube URL using the regular URLPicker #5499

acelaya opened this issue Jun 16, 2023 · 1 comment · Fixed by #5503

Comments

@acelaya
Copy link
Contributor

acelaya commented Jun 16, 2023

Right now we are using raw YouTube URLs for video transcript annotation assignments.

This means, the regular URLPicker can be "accidentally" used to provide a YouTube URL, with the problem that this picker does not validate the video actually exists and does not have any restrictions that would prevent its proper usage in via's video app (age-restricted, non-embeddable, etc).

There are a couple of things we could do:

  1. When a YouTube URL is introduced in the URLPicker, we could "warn" the user and suggest switching to the proper content picker with a CTA.
  2. Similar to the above, but we just display an error and prevent the user from continuing with saving the assignment.
  3. Considering we are already planning to move to a smarter content picker at some point, we could just not do anything for now.
@robertknight
Copy link
Member

Similar to the above, but we just display an error and prevent the user from continuing with saving the assignment.

I would suggest we do this as an initial step, since it is easy to implement and it ensures that we run all of our checks of whether the video is usable before the assignment is launched. As an improvement upon that, we can add migration from the default URL picker to the dedicated one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants