Closed Bug 892514 Opened 11 years ago Closed 10 years ago

UI to Add Pre-recorded Events to Air Mozilla

Categories

(Webtools Graveyard :: Air Mozilla, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: richard, Assigned: peterbe)

References

Details

(Whiteboard: cm3)

Neither the current Suggestion wizard nor the old event entry form are good fits for someone wanting to add a pre-recorded event to the Air Mozilla archive.

We need a dedicated UI for this.
Whiteboard: cm3
Flags: needinfo?(seanbolton.me)
Submitted a UI with single page event creation (Bug 897584).
Flags: needinfo?(seanbolton.me)
Depends on: 929556
We discussed this very briefly on IRC but let's try again...

Now that we have file upload working, when you start the Request wizard I think we can and should extend that with some basic flows. 

ON the start page (https://air.mozilla.org/requests/) where you type in the Title, I think we should extend that with one more radio button. "Pre-recorded or Upcoming event?"

If you selected "Pre-recorded", on the next screen it would ask you to select a file from your Upload History. If you don't have any files uploaded, it would be a link there to upload a new file. (some smarts using sessions could help you get back to where you were).
Also, if you selected "Pre-recorded" it would automatically select location "Cyberspace" when you get to the Details page and on the Details page we completely hide the "Start date" question. 

For "Upcoming event" nothing would be different from how it is currently.

What say you?
That sounds good. I'm assuming the start DTG gets set to "now".
And when you say "start DTG", I'm assuming you mean "start date". Yes.
Assignee: nobody → peterbe
Status: NEW → ASSIGNED
One snag I've hit is this; when you Approve a requested event that is marked as NOT upcoming and has a file upload, then when you approve it and mark it as "Scheduled" it becomes a live event :(

That's because it doesn't immediately have an archive_time but it has a start_time (which is by default, when the request was added). 

A thought: Perhaps introduce a new status. Something similar to "Pending". Currently we use "Pending" to mean we're waiting for it to be archived automatically. What about a status called "Pre-recorded". 

I need your thoughts on this to be able to get unstuck on this.
Flags: needinfo?(richard)
We still have to archive (transcode) these, so isn't that the status we should start with?   But if I'm missing something,  I don't have a problem using "Pre-recorded" as the starting status.
Flags: needinfo?(richard)
Hmm... Perhaps we can stick with "Initiated". It was just that "Initiated" *feels* like the next step is for it to be "Scheduled". But perhaps it can work. For now. We can revisit this later.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.