-
Notifications
You must be signed in to change notification settings - Fork 6
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
Edit meta data via UI #9
Comments
jschroeter
added a commit
that referenced
this issue
Feb 11, 2018
jschroeter
added a commit
that referenced
this issue
Feb 11, 2018
Merged
jschroeter
added a commit
that referenced
this issue
Apr 10, 2018
jschroeter
added a commit
that referenced
this issue
Apr 10, 2018
jschroeter
added a commit
that referenced
this issue
Apr 10, 2018
jschroeter
added a commit
that referenced
this issue
Apr 16, 2018
jschroeter
added a commit
that referenced
this issue
Apr 16, 2018
jschroeter
added a commit
that referenced
this issue
Apr 16, 2018
jschroeter
added a commit
that referenced
this issue
Apr 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the video meta data can only be edited manually by editing the JSON files in the file system. It would be helpful to add an UI for that which allows to edit
To keep it simple I would not support the deletion of videos through the UI. Moving a video into folders could be supported later on (#10).
The most important question: do we, and if yes: how do we handle permissions?
Currently I see these options in order of my favorites:
1. don't have permissions at all: everyone with access to the frontend is allowed to edit meta data
2. handle permissions via reverse proxy, e.g. define an URL like /edit which is password protected by the proxy. This makes it very simple and flexible, e.g. LDAP modules could be used.
3. implement LDAP support in the application
One edit button -> display input fields for all meta fields + if possible auto-completion
One save button
One cancel button
The text was updated successfully, but these errors were encountered: