Hi Olli, thanks for that elaborate comment. Again, as of 1.5 there will be an archive and therefore a single point of authority for Mediapackages. Up until then, the cleanup operation is the way to "solve" disk size limitation issues, and your answer seems to indicate that you would *not* want this by default. Correct?
Tobias On 20.06.2012, at 12:11, Olli Salo <[email protected]> wrote: > > Hello folks, > > in our case (Univ of Helsinki) we want to keep the originals in MH so that we > can transcode them thru future workflows when necessary (for example: atm we > use flash but I wish we'll be able to convert the vids to h.264 soon). > Moreover, we want to make sure that MH's metadata is as accurate as possible > and that there would be no orphan media files on the disk. These hopes in > mind we also want to give each mediapackage a distinct lifetime, which in our > case is 12 months. After 12 months we ask (a shell script) the > teacher/professor to extend the lifetime of a mediapackage - if necessary. If > the mediapackage's owner doesn't extend the lifetime, the media file will > first be hidden and then - some months later - deleted permanently and > removed from the disk. > > In my opinion it is _crucial_ that MH keeps track of all the metadata and > that the media files are handled by MH. Only this way a cleanup process is > able to remove both the unnecessary files and folders and also the metadata > from the database. It would be a nightmare if the files and the db would be > out of sync. > > Olli > > > > On 19.6.2012 22:57, Christopher Brooks wrote: >> We already have a bit of an issue with disk space in MH, so we would >> end up turning this back on right away. We archive outside of the >> system atm. >> >> To me it's no big deal to have it on or off by default, so 0 from me, >> >> Chris >> >> On Tue, 19 Jun 2012 19:24:24 +0200 >> Tobias Wunden <[email protected]> wrote: >> >>> As part of our default workflow, we enforce the "cleanup" operation, >>> which is removing all files referenced by a single media package from >>> the file system in order to save space and prevent disks from filling >>> up. So far for the pros of making this the default behavior. >>> >>> On the downside, mediapackages get added to the various indexes in >>> Matterhorn (workflow, episode, search) that can't be used for further >>> (or repeated) processing since they are basically invalid, having >>> pointers to files and catalogs that don't exist anymore. This will be >>> true until we have a working archive in place which unfortunately >>> does note seem doable until 1.5. >>> >>> In order to make sure people make an active choice to have their >>> original media and catalogs removed, I #propose to comment out that >>> operation and add documentation right into the workflow that explains >>> what happens if a user choses to enable it. But if they don't they >>> are still by default maintaining a working installation with valid >>> media packages. >>> >>> I am especially looking for feedback from adopters. >>> >>> Tobias >>> _______________________________________________ >>> Matterhorn mailing list >>> [email protected] >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn >>> >>> >>> To unsubscribe please email >>> [email protected] >>> _______________________________________________ >> >> >> > > > -- > Olli Salo > Tietotekniikkakeskus > Helsingin yliopisto > Tel: +358 9 191 21782 > Gsm: +358 50 407 5509 > Email: [email protected] > > > _______________________________________________ > 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] _______________________________________________
