On 9/12/12 1:09 AM, Tobias Wunden wrote: > Hi Denny, > > great to see that you are doing a decent review of the archive *and* > are sending feedback to this list :-)
Of course! I'd hop on IRC but I'd probably never hop off. :) >> In 1.3, all "recordings" show under the episodes tab, but in 1.4 >> the only way to get things in there is to check the "archive" box >> when scheduling. > > The reason for this change is that some developers were unhappy with > the archive now actually behaving like an archive, meaning it > actually archives your content, which requires space on your hard > drive. This is why you need to explicitly check the "archive" > checkbox. You can easily change your workflow definition to do > archival by default, just remove the checkbox from the ui portion of > the workflow definition and remove the "if" clause from the "archive" > operation. I get it, thanks! How do folks manage non-archived content? How would one retract a "recording" which was not archived, for instance? >> Further, when I do this, the "state" of the episode/archive is >> always "retracted". Further further, whenever I try to "do stuff" >> with "episodes" -- re-encode, retract, etc. -- it fails. I >> generally see jetty-related file errors like this in the log: >> >> WARN (AbstractEpisodeServiceRestEndpoint$2$1:353) - Error writing >> file contents to response org.mortbay.jetty.EofException at >> org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:789) >> >> Probably a configuration issue. I'm gonna mess around with the >> storage stuff in a second anyways, and see if that changes things. > > Actually less probably a configuration issue but a bug. 1.4 is still > work in progress and there are bugs that need to be resolved. If you > manage to reliably reproduce an issue, please consider filing a bug > at opencastproject.jira.com. I saw it in 1.3 too I think. If I figure out what's going on I'll file a ticket, or report back what dumb thing I did that broke it, for future breakers. :) >> It seems like there is a ton of functionality exposed through REST >> and very little exposed via the UI, which seems a bit odd... but I >> digress. > > There is an easy fix to that as well. Donate your insights into what > needs to be in the ui to the project in terms of mock ups, user > stories in Jira or even resources, and things will magically start to > appear in the ui as well :-) We have lots of ideas for the archive, > but we are currently lacking the equivalent amount of resources aka > money. I hear it. I'll try to contribute. I'm decent at Java and Javascript (prefer dojo over jquery), work with OSGI, have worked with ffmpeg & red5 type stuff on and off over the years, am big on automated testing and deployment, yadda yadda. I'm hard pressed for money's alter-ego Time though. :-/ >> Is the plan to rename "Episodes" to "Archives" (I think I saw >> convo about this)? And what do folks think about tooltips in the >> UI? Probably go a long way towards making things easier for >> newbies... > > Again, mock ups would be helpful that propose contents for these tool > tips. After that, all it takes is consensus and a developer who turns > the mocks into real code. Sweet! I like to have stuff like this come from the docs, or be linked to the docs. Perhaps a glossary? Having one, and using it to for generating tooltips (popup/inline) would take some of the pressure off of the names themselves -- re: recordings vs. workflow instances, etc.. Thanks for the information Tobias! :Denny -- The goal of life is to make your heartbeat match the beat of the universe, to match your nature with Nature. Joseph Campbell _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
