Hi, So this was brought up at the dev meeting, and I was an advocate for taking the issue to list but I didn't have experience with the episode service so I asked if someone else would make the proposal (and thanks Ruediger).
Here are my concerns: 1. If it's not a "first rate" feature, does that mean it doesn't require documenting and isn't something we are going to advertise? What about testing? 2. If we are in agreement on the form the UI should take (perhaps a big if?), who is going to do the work? We are really hamstrung as a project in that we have one UX person and minimal ability to implement the UX suggestions. How are we going to remedy this? The first of these concerns needs to be dealt with right away; for 1.3, if this is not promoted to on by default, has it been tested and where are the docs (and where should they live) telling folks how to enable and use the feature? The second of these is something we should discuss on list here, but doesn't really change 1.3 (e.g. it is closed for general development). Chris On Thu, 23 Feb 2012 11:00:23 +0100 Ruediger Rolf <[email protected]> wrote: > Hi Judy, > > okay. Then this is probably stopped, as no one has supported this and > you block this. I hope you are available on the matterhorn users-list > after the release to explain to adopters how they can activate the > episode management in their release. > > Rüdiger > > Am 22.02.2012 17:50, schrieb Judy Stern: > > And just to make sure that this #proposal doesn't go thru without > > further discussion, I want to make it clear that I'm voting -1 for > > now. (This doesn't mean you can't change my mind, i.e. if my design > > counterproposal is really harder to implement that it looks..but > > really all I'm asking for is a move from top-level navigation to a > > subnavigation.) > > > > Judy > > > > On Feb 21, 2012, at 9:41 AM, Judy Stern wrote: > > > >> While I agree that the Episode service is very valuable, from a UX > >> perspective, I think it is a mistake to have it available by > >> default exactly as is, for many reasons that I have explained in > >> the earlier thread [3]. The mockup you point to, Rüdiger, is the > >> more ambitious one that I understand we can not possibly implement > >> at this time. I did also, however, propose two simpler approaches, > >> which keep the two UI's (one for looking at workflow instances, > >> the other for managing media packages) on separate pages but do > >> not make them seem so completely unrelated and do not introduce > >> potentially confusing terminology. In particular, Approach 2 [4] > >> changes very little (I believe, perhaps naively, it would be very > >> easy to implement), but simply makes both UI's available under the > >> Recordings tab. I would like to propose this (or something very > >> similar) as a counterproposal. > >> > >> Judy > >> > >> [3] > >> http://opencast.3480289.n2.nabble.com/Renaming-the-quot-Recordings-quot-tab-proposal-td6783119i20.html#a6803786 > >> [4] > >> http://opencast.jira.com/wiki/display/MH/Keeping+Episodes+UI+Separate+from+Workflow+Instances+UI#KeepingEpisodesUISeparatefromWorkflowInstancesUI-Approach2 > >> > >> > >> On Feb 21, 2012, at 8:56 AM, Ruediger Rolf wrote: > >>> Hi list, > >>> > >>> in the developer meeting today the question came up why the > >>> Episode UI [1] is not activated by default. Several people have > >>> not noticed this feature yet because of this. > >>> > >>> There was some discussion on this UI when it was created and > >>> there was not been a concensus on this UI. So the solution to > >>> this was to deactivate by default. There were some > >>> > >>> But the Episode service is one of the main enhancements in 1.3 > >>> and anyone in the dev meeting today felt sorry that most users > >>> cannot use it because of the hidden UI. > >>> > >>> There is already a proposal on how to combine the workflow and > >>> the episode service in the UI [2], but implementing this is out > >>> of focus for 1.3 and maybe even for 1.4 as no one has himself > >>> commited to this feature yet. > >>> > >>> So the proposal is to active the "episode" UI despite all > >>> concerns, with no or only minor changes (changing the name of the > >>> tab i.e.). We want to avoid a long discussion that may delay the > >>> release, as we hope that the release is only one release blocker > >>> away... so let us keep the discussion short and give your +1 or > >>> -1. > >>> > >>> Thanks > >>> Rüdiger > >>> > >>> [1] see here how to activated this: > >>> http://opencast.jira.com/wiki/display/MH/The+Episode+Service [2] > >>> I hope I found the right mockup: > >>> http://opencast.jira.com/wiki/display/MH/Combining+Episodes+and+Workflow+Instances > >>> > >>> -- > >>> > >>> ________________________________________________ > >>> Rüdiger Rolf, M.A. > >>> Universität Osnabrück - Zentrum virtUOS > >>> Heger-Tor-Wall 12, 49069 Osnabrück > >>> Telefon: (0541) 969-6511 - Fax: (0541) 969-16511 > >>> E-Mail: [email protected] > >>> Internet: www.virtuos.uni-osnabrueck.de > >>> > >>> _______________________________________________ > >>> Matterhorn mailing list > >>> [email protected] > >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn > >>> > >>> > >>> To unsubscribe please email > >>> [email protected] > >>> _______________________________________________ > > _______________________________________________ > > Matterhorn mailing list > > [email protected] > > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > > > > To unsubscribe please email > > [email protected] > > _______________________________________________ > > > > -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
