Merge download and upload tasks messages [& critical design questions]#99
Merge download and upload tasks messages [& critical design questions]#99deldesir wants to merge 1 commit into
Conversation
Display links of successfully uploaded files.
|
I and others are trying to understand this PR:
Users should never see the word "uploaded" if they just clicked "Download to IIAB" — the word "uploaded" appears to be extremely confusing language making this PR very difficult to understand (?) And if so...
|
@deldesir Please deepen explanation(s) of what you are proposing!
PS @EMG70 asks how PRs #96 and #99 should be tested separately and/or together... |
They're the same.
I agree. The subsequent upload tasks that kick in right after videos' been downloaded do not fit well. They are there just because I forgot to remove them initially when I came with download task.
It should because we already have this reserved for direct files uploads/imports using the upload button. |
Yes, and single downloads too. The upload task along with a download one was a pure accident and wasn't designed. I was learning about the upload task and made the download one after it.
I can't be sure I know exactly what the answer is unless we try this scenario ourselves. I presume links of those videos would not be shown because.
Prior to #99, there was already some dynamic updating at play for almost all columns. This PR builds on it.
This video that keeps failing https://www.youtube.com/watch?v=QXQrvT23rPw (due to xklb "media check failure") would benefit from a dynamic sort of healing/recovering, but we're not there yet. Copy pasting the table was never possible to me. I was planning of implementing a mechanism to dump it.
Please test them together using the same testing scenarios from #97. If this turns out to be non practical or non user-friendly, I'll do necessary changes. |
@deldesir What ticket number is tracking the above issue?
|
|
@deldesir seems to have posted this to: |
|
I have used same videos from PR97 for consistency 1.Valid Download- still downloads ok but no thumbnail ❌ 2.Invalid URL ✅ fails as as expected in tasks 3.No Requested Files in the Database: Live video feed fails as expected ✅ 4.Shelf Title Retrieval: Playlist downloads ok as one row showing all videos ✅ 5.Download Cancellation: I think viewing all downloaded videos in one row is a good idea IMHO as they look all compacted to allow librarian/admin to immediately see output than having them as individual rows. |
I strongly disagree as cramming 100 videos (that's our target for most playlists/channels) into a giant paragraph of smallprint becomes... a disgusting / overwhelming mess (and I'm being very polite!) |
|
That's fair enough.The admin /librarian can still scroll and see all downloads if viewed as one video per row.👍 |
Yes: And the "Tasks" view will likely show basic/vital details for each of the playlist/channel's 100 videos, for example each row might show... (1) HH:MM:SS = duration of each video (2) date-of-publication of the video (3) "views-per-year" (or views-per-day) i.e. relative popularity of each video, e.g. as reported by YouTube |
|
RECAP: "Tasks" view is not just a bug-reporting / diagnostic tool. It's also a critical Dashboard of Curatorial Insights, that might profoundly help educators grasp the structure of their own/evolving content choices! 🎨 |
@deldesir please respond to both above, thanks to @EMG70's hard work above, Thank you!
PS I strongly suggest we not worry about 5. just yet. As all PR's MUST be as COMPACT as humanly possible. With CLEARLY-STATED PURPOSE. Any PR "afflicted by inflation" needs to broken apart into smaller PR's (each very valuable, communicating as many of the critical 5 W's as possible for each change!) |
CLARIFICATION: We will focus exclusively on playlists/channels' "TOP 100" videos (based on views-per-day, as reported by YouTube) going forward. Featuritis a.k.a. Scope Creep beyond agreed upon Requirements a.k.a. Second System Effect is the death of all projects — and the straight truth is we have to put an end to the endless wish list of bells & whistles right now! 💯 |
|
Noted. I will revert to "upload" task for every video downloaded. |
Thank You! And if 100 rows (depicting a playlist/channel's 100 videos) are extremely ugly in particular ways — we will assess as that time how to make that evolving UX progressively more purposeful — for the "curriculum designers" who will depend on it! 👣 Somewhat Related: |
|
I am perhaps late to the party, but I have a couple of comments.
Of course, my views are based on what I did in Admin Console where lists of content can be selected at the same time, but each member of the list is processed separately in a queue. This video download facility would have been a nice addition to CMDSRV. |
|
@tim-moody's insights are right on. One other point I and @deldesir should have mentioned... we're also looking for a "slightly gamified" (and definitely compelling!) view of each video as it's chosen/downloaded/ETC — to make "content gardening" much more fun!
(We don't yet have a great design: but hopefully in about a week we'll have an early prototype or visual mock-up at minimum, to kick the tires to start exploring this!) Somewhat off-topic but then again maybe not (!) is this odd NYT article from earlier this week 😁 https://nytimes.com/2024/01/14/business/media/netflix-streaming-movies-ratings.html |
|
@tim-moody wrote:
Great Question! I don't yet understand it and it's definitely a work in progress. @deldesir is sick this week but texted me...
Hopefully he can explain more in later weeks how this works and how it might be evolving, when he's feeling better 😃 |
|
This PR is no more relevant. @holta can we close it since we have retained one video per row approach? |
Ok if this PR is no longer relevant! |
🚀 Pull Request Overview:
This PR does the following changes:
📋 Checklist:
🔗 Related Issue: #89
📌 Testing scenarios:
See Issue #97
cc @EMG70