Not really. The files in the /streams/hibernate folder are the final videos of the recordings. If you delete them all your recordings are gone.
The files in the /streams/$ROOM_ID folders are the raw recording files. Based on those files there is a complete video mixed (that is then produced into the /streams/hibernate folder). Theoretically you can delete the files in the /streams/$ROOM_ID folder as the final mixed video is already produced. However for recordings based on the interview room type, there is a functionality to re-render the raw data but with some parameters to adjust the audio (make it loader, delay the audio, et cetera). Those are useful if you want to post-edit the video from inside OpenMeetings because for instance one participant has a microphone that is a lot loader then some other participant. Once the video is "mixed" into the final format there would be no way of re-adjusting those settings. So there is some button in the OpenMeetings UI to re-render the raw files with some additional settings. If you delete the files in the /streams/$ROOM_ID folders bascially the UI functionality is pointing to files that do no more exist. Also there are entries in the database that point to the files in the /streams/$ROOM_ID directory. So in general, it would be basically a bad idea to just delete those folders, UI functionality might be broken and the data model would be inconsistent. Sebastian 2013/8/25 Lee Saunders <[email protected]> > Is it safe for me to delete the sub-folders in the streams directory? > > > On Sun, Aug 25, 2013 at 1:39 AM, Lee Saunders < > [email protected]> wrote: > >> Thank you for the technical information. >> I'm just going my my experience using another system in which each >> meeting was tied only to the originator and could remain open over any >> number of sessions, and then closed when complete. Once complete a PDF of >> the whiteboard and accompanying documentation was created as a soft copy >> for download, stored in the users account. So, even though the meeting had >> been closed, a downloadable representation of the meeting was available in >> an archive. I do see how Open Minutes works differently, though. >> >> All in all, Open Meetings is a great service. Thank you for creating it. >> >> >> On Sun, Aug 25, 2013 at 1:27 AM, [email protected] < >> [email protected]> wrote: >> >>> We actually never physically delete anything, we just mark/flag as >>> deleted and don't show it in the UI anymore. >>> >>> There are multiple reasons why you do that in software. For instance >>> there are are often foreign key constraints. That means that you can't >>> physically delete an user, cause this userId is a foreign key in some other >>> tables. And by deleting the user physically you would get an inconsistance >>> data model. >>> This will become a real issue when you work with databases that have >>> "real" foreign keys (postgres, oracle, MySQL InnoDB, et cetera). However >>> even with data on disk in files, just because you "can" delete those files >>> without throwing any error does not mean that this is a good idea, as for >>> example records in the database still point to that file. By doing that the >>> data model simply becomes inconsistent. Some references are missing, it >>> pretty much gets a mess if you start to delete files. >>> >>> Another reason is that you want to keep track on changes that have >>> happened. This is sometimes a legal requirement in companies and >>> government. You just never delete hard, data must be always possible to be >>> restored. For instance an user xyz claims his important file XXX was >>> deleted at the 28.12.2009, now the sys admins need to recover that file. >>> >>> There are however attempts to have some kind of clean up tasks that >>> delete such references to free up disk space. But if ever implemented it >>> has to be done very carefully and clear to the sys admin that there is no >>> way back, you will loose data and you probably should back up the data >>> before doing it. >>> >>> Bottom line is: Don't delete, just flag as deleted. >>> >>> Sebastian >>> >>> >>> >>> >>> >>> 2013/8/25 Lee Saunders <[email protected]> >>> >>>> Ah, I see. I guess that does make sense. I just worry about having a >>>> list of rooms that becomes too long to manage. >>>> Perhaps then, completed meetings could go into an archive\ completed >>>> events section, thus keeping them separate from pending events. >>>> >>>> I have also noticed that deleted recordings remain in the streams >>>> folder (..\webapps\openmeetings\streams\). Why don't they get deleted when >>>> moved to trash? >>>> >>>> All the best, >>>> >>>> Lee. >>>> >>>> >>>> >>>> On Sun, Aug 25, 2013 at 12:49 AM, [email protected] < >>>> [email protected]> wrote: >>>> >>>>> Hi Lee, >>>>> >>>>> I don't think we should delete the room after a calendar event was >>>>> terminated. Otherwise for example any uploaded or created data that was >>>>> part of the conference room itself would be gone. >>>>> Also you can attach existing rooms to multiple calendar events. So the >>>>> relationship between room to calendar event is not 1:1. >>>>> >>>>> Sebastian >>>>> >>>>> >>>>> >>>>> 2013/8/25 Lee Saunders <[email protected]> >>>>> >>>>>> Hello, >>>>>> >>>>>> I tested the calendar, but after the event had ended, the room >>>>>> persisted. >>>>>> Is there a way to terminate the event when the 'Exit' button is >>>>>> clicked rather than delete the event in the calendar and receive a >>>>>> 'Cancelled' message? >>>>>> >>>>>> I think that if an event is terminated before the start or end time, >>>>>> then yes, it is cancelled, but after the end time, a meeting has usually >>>>>> ended. >>>>>> >>>>>> Just a suggestion. >>>>>> >>>>>> All the best, >>>>>> >>>>>> Lee. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Sebastian Wagner >>>>> https://twitter.com/#!/dead_lock >>>>> http://www.webbase-design.de >>>>> http://www.wagner-sebastian.com >>>>> [email protected] >>>>> >>>> >>>> >>> >>> >>> -- >>> Sebastian Wagner >>> https://twitter.com/#!/dead_lock >>> http://www.webbase-design.de >>> http://www.wagner-sebastian.com >>> [email protected] >>> >> >> > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
