Scope of initial version

[blizzz]

• LDAP connectivity settings
  • add one or more LDAP connections
  • optionally import from LDAP backend
  • per each specify base, filter, attribute mappings
  • and the addressbook display name
• A virtual addressbook
  • like the system addressbook, but browsable in the contacts app (so, perhaps might be a read-only user addressbook for this) (not desired). Read only nevertheless.
  • advantage: it feeds both contacts menu as well as auto-complete
  • implement as a DAV plugin
• A contacts menu data provider
  • offers an import actions if the contacts is only in the LDAP addressbook
  • ⚠ importing it a user addressbook makes is writeable, but it will be overwritten on updates with the sync (see further). But perhaps we can make it smart and merge only what has changed.
• Data handling
  • since contacts app loads all contacts, a live access to LDAP is not reasonable (appearance in contacts app not desired)
  • a regular background job will sync (and update) all records from LDAP
  • a sync button on the settings page can schedule a sync for the next run (e.g. also for initial sync)
  • in order to prevent information loss through carrdav clients, imported contacts are being mapped to the LDAP record (or its addressbook id) for future updates. (not desired)
  • When a contact cannot be found on LDAP anymore, it is removed from the virtual addressbook as well as the mapping. Connected imported contacts are left in the user addressbooks. (not desired)

EDIT: data handling turned out to be not necessary, as the search performance against LDAP is good

[blizzz]

done