481021 - Allow easy access to resource and location principals and calendars [meta]

Status: RESOLVED INVALID

(Calendar :: Internal Components, enhancement)

Description

[Jelle de Jong]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009020409 Iceweasel/3.0.6 (Debian-3.0.6-1)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.18pre) Gecko/20090113 Debian/5.0 (Codename: lenny) Iceowl/0.9

The caldav standard and the darwin calendar server allow for the creation of resources and locations calenders. Like rooms, and beamers. I want to be possible to use iceowl to use these resources and location calenders. So iceowl can be used in organization to make planning of rooms and used equipment.

Reproducible: Always

Comment 1

[Philipp Kewisch [:Fallen][📱📆]]

I was pretty sure we had a bug to allow creating calendar resources on caldav servers, but I can't find it now. Confirming for now.

Comment 2

[Philipp Kewisch [:Fallen][📱📆]]

This will probably be a meta bug actually, as there are loads of things we could do in this area. Possible dependent bugs:

* Add interfaces that allow any calendar provider to hook in searches for users/resources and calendars
* Add an autocomplete type for searching users/resources through the provider
  - Use the autocomplete type in the event dialog location field
  - Use the autocomplete type in the attendees dialog (also setting the CUTYPE correctly)
* Provide some sort of resource browser (maybe as an extension)

In the caldav provider there is not yet an optimal way to do the searches. What works for now and might actually work for many existing servers is doing a principal-property-search on the principal URL, following rfc 3744. There are also two non-standard attributes (type="ROOM" and test="anyof") here. Example:

<?xml version="1.0" encoding="UTF-8"?>
<A:principal-property-search xmlns:A="DAV:" type="ROOM" test="anyof">
  <A:property-search>
    <A:prop>
      <A:displayname/>
    </A:prop>
    <A:match match-type="contains">myquerystring</A:match>
  </A:property-search>
  <A:property-search>
    <A:prop>
      <C:email-address-set xmlns:C="http://calendarserver.org/ns/"/>
    </A:prop>
    <A:match match-type="starts-with">myquerystring</A:match>
  </A:property-search>
  <A:prop>
    <A:principal-URL/>
    <C:first-name xmlns:C="http://calendarserver.org/ns/"/>
    <C:record-type xmlns:C="http://calendarserver.org/ns/"/>
    <C:last-name xmlns:C="http://calendarserver.org/ns/"/>
    <C:email-address-set xmlns:C="http://calendarserver.org/ns/"/>
    <B:calendar-user-type xmlns:B="urn:ietf:params:xml:ns:caldav"/>
    <A:displayname/>
    <B:calendar-user-address-set xmlns:B="urn:ietf:params:xml:ns:caldav"/>
  </A:prop>
</A:principal-property-search>


Calconnect is starting to work on a new draft to allow simple searches on the server that allow more flexibility for querying with less bits transferred. This is not out yet though.

Comment 3

[MikeLing]

Hi~ Philipp, I am very interesting about this bug, but I see the gsoc2015 tag. I am a postgraduate student but I haven't enrolled before September 10,2015. So could I take part in this project? I will be grateful if you can offer me some information.:)

Comment 4

[Wayne Mery (:wsmwk)]

obsolete