The Davical based calendar server crashed due to some inconsistencies in upstream package distribution is the source repository and we have not been able to restore the calendar server. The calendar entries are lost (and yes, we are ashamed).
Users will need to login to ownCloud (https://owncloud.iitd.ac.in) and create a calendar called defaultcalendar (unless it already exists) to be able to access it from the Roundcube webmail interface. Users can add/configure other calendars in Roundcube from Settings -> Caldav Settings.
Please see the help after logging in to ownCloud (https://owncloud.iitd.ac.in) on how to configure other calendar clients to work with the ownCloud calendar server. Apple (Mac/iPad/iPhone) users can use the mobileconfig utility available at http://www.cc.iitd.ernet.in/CSC/index.php?option=com_content&view=article&id=79.
[Deprecated, retained for historical reasons, Sptember 26, 2013]
CSC has commissioned a calendar server based on the CalDAV protocol which can be accessed from both within and outside IITD. Each user will have a default personal calendar available at an URL like https://caldav.iitd.ac.in/caldav.php/uid/calendar. Users can create multiple calendars and set fine grained access control rights for other users.
The calendar server is based on Davical and supports a host of features including public and private events, scheduling, invitations, free-busy query, per-user access control lists, multiple calendar support, ICS import etc. Please see the Davical wiki for details.
The calendar can be accessed from multiple devices and clients including Evolution, Mozilla calendar (works with Firefox and Thunderbird), iPhone/iCal, Android calendars with CalDAV support, several extensions for Outlook etc. A basic client has also been configured in the Roundcube webmail interface. Please see the Davical wiki for popular clients and the client configuration page.
Users cn modify the access control lists for their calendars by logging in at https://caldav.iitd.ac.in. This facility is available from only within IITD.
To set up a shared calendar, for example for a meeting room booking system or an appointment scheduler to be shared with one's secretary, an user can do the following:
- Login to https://caldav.iitd.ac.in
- Click on User functions -> View my details, and click on Create Collection to create a new calendar. The user needs to provide a DAV path which should be like /caldav.php/uid/newcalendar and provide a Display name for the new calendar. The user also needs to set up a time zone (Asia/Calutta) and set the Schedule transparency to transparent.
- From the Collection Grant section the user needs to grant all privileges, except perhaps change of access control rights, to other users with whom the calendar is to be shared. Unfortunately, the LDAP groups are not yet integrated with the caldav server and the access control rights for each user will have to be done manually for now. We will add support for group based access control in due course of time.
Other users can access the calendar created above from their favourite calendar clients. For example, to subscribe to the newly created calendar using the procedure described above, an user can do the following from the Roundcube webmail interface:
- Go to Settings -> Calendar -> Categories and click on + for a new subscription.
- Provide a Display name for the calendar, choose an appropriate diplay colour and click on Save.
- Click on Properties (the radio button on the right) and set the calendar path and access password (the default must be removed and the user's password must be provided). The calendar path should be https://caldav.iitd.ac.in/caldav.php/uid/newcalendar where uid is the user id of the person who owns the calendar.
- An user can subscribe to at most three calendars using the above procedure from the Roundcube webmail interface.
All users with write access to the new calendar can add events and all with read access can view it. Unfortunately, the Roundcube webmail interface does not display who has created the event. User's may have to add this information themselves in the event description.