On Thu, 2011-10-13 at 16:06 +0530, Chenthill wrote:
> On Wed, 2011-10-12 at 10:39 +0000, Woodhouse, David wrote:
> > On Wed, 2011-10-12 at 12:25 +0200, Patrick Ohly wrote:
> > > David, how does the Evolution EWS backend handle this? Does it silently
> > > throw away data or remap it when the EDS vCard doesn't fit into the
> > > data model?
> > Hm, haven't looked very hard at the addressbook code; that's a
> > for Chen. Looking at the convert_contact_to_xml() function at
> > I think we just iterate over the known properties and map them, and drop
> > anything we don't have a mapping for.
> > I'm not sure if we have a filter (or capability list) somewhere which
> > prevents the UI from *adding* fields that we don't understand. That
> > would make some sense, in the case where it is specifically an
> > Exchange-based 'folder' in Evolution rather than being a file-based
> > store which just happens to be synced today to Exchange.
> At the moment, I have created a mapping for possible fields. The fields
> which I was not able to match are,
> The backends currently provide the fields that are
The problem is not just to find a mapping and document supported fields.
If EWS is following the Exchange data model, then it has additional
constraints even on the fields which have a mapping, doesn't it?
For ActiveSync, those constraints are:
* three different email addresses (without a way to mark them as
* two postal addresses (one work, one home)
* ten different phone numbers:
* two business voice
* two home voice
* one business fax
* one business fax
* one cell
* one car
* one radio (whatever that means nowadays)
* one pager
Do these constraints also apply to EWS? What happens if a user creates a
contact with two cell phone numbers, for example?
The same applies to ews as well.
I don't see an issue with mapping
against the EContact fields for all the above mentioned fields. I see a
one-to-one mapping in
for all the fields above.
Your question on two cell phone numbers stays a problem with any
backend. Perhaps the existing exchange 2003 OWA connector is having the
We have an issue with representation in the UI. The UI does not reflect
the exact fields as per the EContact. This can be dealt with while
dealing the IM entry issue.
I do not see this as a major issue since OWA faces the same issue and I
have not observed much requests on this from users.