-
Notifications
You must be signed in to change notification settings - Fork 31
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
Ability to search video transcripts #56
Comments
Im thinking there are a couple of ways to approach this.
Open to suggestions if anyone has any other alternative for this feature implementation. |
I think the feature has value even with tagging. I know personally I've wanted to search based on some word or phrase I remember hearing in a video; that level of detail can't be picked up by tags. We'd definitely want to use some pre-existing solution for search. There are several open source search solutions available. I believe Atlas search is an additional expense (not necessarily a problem). It may not be possible to find a premade solution that can be run for free (again, not necessarily a problem). |
With Atlas search, I believe it's free (I've used it before). I'm not sure if there's a cost based on a lot of usage but its something I can take a look at and report here. Based on those findings, we can decide the course of action. In terms of updating the production MongoDB for the transcript, would you be okay with that being a manual step? Im not quite sure how that would be automated or if effort would be better spent elsewhere than automating a one-time-per-class task. Im thinking of a text box in the "edit class" page where you would paste the entire transcript. |
From the idea discussed in #27 (comment)
Make some way for a user to search though the video transcript for text/content and return the classes that have that content
For example if a user searches for "flexbox", all the classes that discussed flexbox would be returned. Not sure if its still necessary or how feasible this feature is, but lets discuss here.
Resources:
The text was updated successfully, but these errors were encountered: