-
Notifications
You must be signed in to change notification settings - Fork 12
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
Manage Datasets -> Manage Video Storage (functionality enhancements) #1406
Comments
Added command to renumber backup videos, remove 7char strings, correct extension to match video type.
#1406: Enhancements to Dataset Manager -> Manage Video Storage functionality
Part of this issue has been deployed. Because Signbank has zillions more video files and video objects than when work on this issue was started in November, the management page has become extremely slow loading. (Signbank DB is now 4 GB. In November it was less than 1 GB after @Woseseltops removed the sessions storage at that time.) The search functionality is needed to reduce computation prior to loading. Also, a delete button for backups is needed. |
On this existing page, a dataset manager can view the paths of the gloss video objects. The page is view only.
Propose to make some (proposed) commands and filters of Gloss Video Admin available here (#1398)
Currently, in the display, the user sees the backup filename paths in read-only mode.
Add functionality to
Goal: The above allows the dataset manager to repair data in a targeted and convenient way
UPDATE: An additional area to peruse video files for the dataset that do not have any GlossVideo object pointing to them (due to the corresponding gloss having been deleted, its video file is not deleted).
For this, a link to the file in protected_media is constructed, allowing the dataset manager to download videos that are otherwise not accessible in the interface. (This is motivated by #1402) (implemented)
@Woseseltops this would be an ideal place to make use of those sockets to allow the page to remain open and receive live updates to the video storage, also from the API activity.
The text was updated successfully, but these errors were encountered: