View source for Features

 {{Languages}}
Features of DAViCal are linked to features of CalDAV client.

== Comparison of CalDAV clients ==

{{Tlist}}
{{TRlist}}Features\Clients
{{THlist}}[[CalDAV Clients/Evolution|Evolution]]
{{THlist}}[[CalDAV Clients/Mozilla Calendar|Mozilla]]
{{THlist}}[[CalDAV Clients/Mulberry|Mulberry]]
{{THlist}}[[CalDAV Clients/Chandler|Chandler]]
{{THlist}}[[CalDAV Clients/Cadaver|Cadaver]]
{{THlist}}[[CalDAV Clients/Kontact|Kontact]] 
{{THlist}}[[CalDAV Clients/iCal|iCal 3.0.1+]] 
{{TRlist}}[[#Handle Private Events|Handle Private Events]]
| yes  || yes  || yes || yes || no || yes || yes
{{TRlist}}[[#Handle Confidential Events|Handle Confidential Events]]
| yes  || yes  || yes || ?   || no || no  || yes
{{TRlist}}[[#Handle Alarms|Handle Alarms]]
| yes  || yes  || yes || yes || no || yes || yes
{{TRlist}}[[#Alarm per Calendar|Alarm per Calendar]]
| yes  || 0.8   || ?   || ?  || no || yes || no
{{TRlist}}[[#Free Busy|Free Busy]]
| yes  || 0.8+  ||  ?  || ?  || no || yes || yes
{{TRlist}}Auto detect subscribable calendar
|  || wip [http://wiki.mozilla.org/Calendar:Hamburg_F2F_Meeting details] || yes  ||  ||  ||  || 3.0.1, but only your own calendars
{{TRlist}}Access Rights: UI to manipulate ACL
|  || wip  || yes, unsupported in DAViCal  || ? || ? || ? || yes, unsupported in DAViCal
|}

==== legend ====
{{Tlist}}
{{TRlist}}yes || feature implemented, and working (almost) perfectly 
{{TRlist}}no  || not available 
{{TRlist}}wip || work in progress, something is already there but not completely working as expected 
{{TRlist}}?   || unknown 
{{TRlist}}x.y.z   || From Client version x.y.z
{{TRlist}}D x.y.z || From DAViCal version x.y.z
|}

{{TOCright}}
== Feature Details ==

=== Handle Private Events ===

The user has the ability to set the privacy of an event. If set to ''Private'' the event is hidden to all except: the Administrator, the users that have the Administer's right on its calendar, or the user himself. DAViCal is able to filter and returns no information when this situation appears

=== Handle Confidential Events ===

The user has the ability to set the privacy of an event. If set to ''Confidential'' the event is visible, but only information that the user is busy. This applies to all  except the Administrator, the users that have the Administer' right on its calendar, or the user themselves. DAViCal is able to filter and returns only the information needed.

=== Handle Alarms ===

The user has the ability to set an alarm on events. In [[CalDAV Clients/Mozilla Calendar|Mozilla Calendar]] the user can set an alarm but can also recognise alarms of all other calendars. DAViCal supports alarm filtering: if the user is the Administrator, the users that have the Administer' right on its calendar, or the user themselves, the user receives an alarm for the event, otherwise the full event will be created without an alarm. For information about configuring hiding of alarms for non-owners and non-admins of calendars see [[Configuration/settings/hide_alarm|hide_alarm]].

=== Alarm per Calendar ===

The calendar client offers a way to specify which one of the subscribed calendar can trigger an alarm.

=== Free Busy ===

With such a feature, the user, with its calendar client, can request the server to find free time for all their attendees. 

The client should provide a specific view like this one 

[http://wiki.mozilla.org/images/e/e0/Wcap-freebusy.png http://wiki.mozilla.org/images/e/e0/Wcap-freebusy.png] 

== General DAViCal Server Features ==

=== Multiple calendars per user ===

The CalDAV specifications allowed for one user to have many calendars.  A calendar in the specification is called a collection and has a path like a directory in a file system, for example: I can have 2 calendars "/max/work/" "/max/home/" 

=== ACL ===

for more details : [[Improved Permissions]]

=== ICS Import ===

You have 2 ways for doing this in the web interface provided, 
# You can import in place an ics file that will replace a specific calendar collection in the server
# You can import all ics files stored on a directory on the server into DAViCal for a specific user deduced from the ics file name. 

You specify the path on the server and the path of the calendars newly created, for example: on my server I have the directory /ics_files_directory, I've got 2 ics files :'' /ics_files_directory/'''max'''.ics'',''/ics_files_directory/'''andrew'''.ics''. I set '''''ics_files_directory''''' as the path on the server, and '''''home''''' for the newly created calendars. All ics files will be imported respectively in collections ''/max/home'' and ''/andrew/home''

=== Supported DAV Methods ===

GET,HEAD,OPTIONS,PUT (target exists),PUT (no target exists),PROPPATCH,PROPFIND,DELETE,LOCK (target exists),LOCK (no target exists), MKCOL, MKCALENDAR,UNLOCK,REPORT,FREEBUSY  for more details : [[Improved Permissions]] 

=== Alarms and TODO Handling ===

DAViCal provides a way to not share alarms and todos of a calendar when the requester of the calendar is not the owner or does not have the 'Administer' right. 
===LDAP Authentication===

for more details see [[Configuration/Authentication_Settings/LDAP]]
* when a user from the LDAP directory log in, and does not exist then DAViCal creates a new user or if they do exist updates the user if necessary (timestamp comparison) 
* ability to sync LDAP directory to DAViCal : this operation do the following :  
*# check valid users in LDAP directory 
*# check users in DAViCal 
*#: then 
*# if a user is present in DAViCal but not in LDAP, mark them as inactive in DAViCal 
*# if a user is present in LDAP but not in DAViCal, create the user in DAViCal
*# if a user in present in LDAP and DAViCal, update the information in DAViCal

=== External Bind ===

It is possible to import a remote calendar that is available from the web. For more information, see the article [[External Bind]].