[SOGo] Suggestion for best practice calender usage/roll-out
Hi, we plan to roll-out SOGo to our users soon and we do have to consider different thought, knowledge and wishes from all users to manage calendars. My question is, what are your experiences, pros and cons to handle and use calendars? E.g. I was thinking of personal/privat calenders per user, calendars for groups/departments and calendars for all (like holidays). But now, where to put what kind of appointment? E.g. two members of our department have a meeting, so put that in the department or private calendar? For me not taking part in that meeting there is no need to know when, where and topic etc Or is the calender management always different? There isn't just one way of doing it. Right? What do you think? Any good whitpaper or book on timemanagement for groups? :)) BTW I like Time Management for System Administrators http://www.oreilly.de/catalog/9780596007836/ Regards . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 Fax +49 7141 969 55 420 E-Mail goetz.reini...@filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt smime.p7s Description: S/MIME Kryptografische Unterschrift
Re: [SOGo] Suggestion for best practice calender usage/roll-out
hi, Am 09.01.2013 10:21 schrieb Götz Reinicke - IT Koordinator: E.g. I was thinking of personal/privat calenders per user, calendars for groups/departments and calendars for all (like holidays). this is how we do it - by default, every department has public calendars for holidays and for appointments that are relevant the department at large. these calenders serve as a kind of bulletin board and are owned by a pseudo-user, there won't be invitations for these events. private appointments are handled by the organizer (in her/his personal calender) and the invitees, incl. notifications and the usage of free-/busy-information. additional calenders are available on request - we urge the users to _not_ create calenders and share them themselves if they have a more-than-private scope. works quite well so far … adequate training and documentation is essential. hth / with kind regards, t. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Suggestion for best practice calender usage/roll-out
Hi Götz Reinicke Am 2013-01-09 10:21, schrieb Götz Reinicke - IT Koordinator: we plan to roll-out SOGo to our users soon and we do have to consider different thought, knowledge and wishes from all users to manage calendars. My question is, what are your experiences, pros and cons to handle and use calendars? E.g. I was thinking of personal/privat calenders per user, calendars for groups/departments and calendars for all (like holidays). But now, where to put what kind of appointment? E.g. two members of our department have a meeting, so put that in the department or private calendar? For me not taking part in that meeting there is no need to know when, where and topic etc Or is the calender management always different? There isn't just one way of doing it. Right? What do you think? Any good whitpaper or book on timemanagement for groups? :)) This heavily depends on your organisation style. We usually do meetings between the participants. You always see the free/busy information on all accounts. But there is also a department account which is configured as resource with infinite amount. It is also shared with all members of the department. So if you have an appointment, which should be visible to the whole department, then you invite this department account too. As it is a resource, it will autoaccept your invitation and your meeting is visible immediately to all department members (all informations, not only free/busy). Kind regards, Christian Mack -- Christian Mack Gruppe Informationsdienste Rechenzentrum Universität Konstanz -- users@sogo.nu https://inverse.ca/sogo/lists
