Use Resources with SOGo

Since version 1.3.7 SOGo supports the management of resources like meeting rooms or beamers. A resource has, just like a person, a calendar, an email address and may be invited to events. The big difference is that resources auto accept invitations.

Configure resources with LDAP

LDAP needs a new scheme for resources: calendarResource which is defined in this IETF draft. (It is not final right now)

Martin Lehman contributed a schema file on the mailinglist (or use the attached version calresource.schema). Configure your LDAP server to use this schema file. Then use your favorite LDAP tool (TODO: link to the LDAP tools page) to add some resources:

  dn: uid=meetingroom,ou=Users,dc=example,dc=com
  objectClass: inetOrgPerson
  objectClass: organizationalPerson
  objectClass: person
  objectClass: top
  objectClass: CalendarResource
  objectClass: calEntry
  cn: Big Meetingroom
  sn: Meetingroom
  displayName: Example Big Meetingroom
  givenName: Big
  Kind: location
  mail: meetingroom@example.com
  Multiplebookings: 1
  uid: meetingroom

There are several things to note:

• The object classes in use:

  • CalendarResource and calEntry for Multiplebookings and Kind

  • person, organisationalPerson and inetOrgPerson for cn, sn, givenName, displayName, mail and uid

• required fields are uid, mail, Multiplebookings and Kind.

• optional but recommended fields are:

  • for easier searching: cn, sn and givenName

  • for displaying in addressbook: displayName

  when searching in addressbook, SOGo will search in mail, displayName, cn, sn and givenName where it will try to match strings from the beginning (ie 'me' will match 'meetingroom' but 'roo' won't match).

In case you are using the same LDAP dn as for your users (which is recommended because Lightning may only use one of SOGo's address sources for auto completion) you do not need to change anything in your configuration as SOGo will automatically detect a resource by objectClass: CalendarResource

• specifying KindFieldName or MultipleBookingsFieldName in GNUStepDefaults is not required when properly using the object class CalendarResource as described above. (Those fields are mainly required for SQL backends)

Configure resources with SQL databases

• TODO