LDAP: Conditionally use 'description' as Note
The inetOrgPerson, organizationalPerson, and person objectClass(es) can contain attribute description
. The evolutionPerson objectClass can contain attribute note
.
addressbook/backends/ldap/e-book-backend-ldap.c contains E_STRING_PROP (E_CONTACT_NOTE, "note"),
and ignores the attribute description
.
I believe the note and description field serve the same purpose, but “description” is standard, “note” is not, so Evolution-data-server shall read “description” and deprecate “note”.