Confirm, emeritus
998
edits
Changes
no edit summary
Use cases:
Contacts and contact providers:
# A user adds a contact provider to their address book. Among the various settings for this contact provider are options for setting whether or not this contact provider should be able to push changes to other contact providers. The user can also choose which fields can be pushed to this contact provider, and pushed to other contact providers from this provider.
# A user adds a contact provider to an address book that already has some contacts in it. Contacts are merged where applicable. Changes made locally are automatically pushed to the contact provider. The local contacts not already existing in the contact provider are pushed, assuming that we have write capabilities to that provider, and the user has specified that this is a provider that we want to push new data to.
# A user adds a contact provider to an address book that already communicates with one or more other contact providers. Contacts are merged where applicable. The user can view the contacts that were merged, and make any corrections or resolve any ambiguities that may have arisen from the merge.
# A user is offline and opens their address book. They are able to view , search, and edit their contacts, but changes are not pushed until they come back online. Once back online, any ambiguities or conflicts from pushing will be brought to the users attention for resolution.
# A user adds a contact provider that provides some sensitive or private information about each contact. During the setup process, the user makes sure to set the provider so that this information is not pushed to any other contact providers.
# A user with several contact providers in their address book decides to compose an email. While filling out the "To:" field, potential contacts are displayed for auto-completion.
# A user wants to add a contact with a large number of e-mail addresses and phone numbers. Unfortunately, one or more of their contact providers do not support more than 5 e-mail address and phone fields. While creating this contact, these limitations are shown to the user, who can then choose a subset of e-mail addresses and phone numbers to push to those providers.
# A user has added some contact providers whose supported fields do not map 1-to-1. When editing their contacts, they can easily see and manipulate which fields are being written to each provider.
# A user is removing a contact provider. If there exist fields that are only supported by that provider, the user is notified for resolution. The user has the option of deleting contacts that are only connected with that provider.
Contact groups:
# Contact groups from a provider (in some cases referred to as "mailing lists") are synchronized in a similar fashion to contacts themselves.
# Contacts can be organized into arbitrary groups. When possible, and if allowed by the user, these groups are pushed to contact providers.
# Contact groups can be nested arbitrarily deep. When nested groups are not possible for a contact provider, approximations are made.
# A default contact group called "All Contacts" allows a user to display all contacts existing within their address book
# Each contact provider gets a group created for it. Contacts in these groups have some or all fields synchronized with that provider. Moving a contact into this group will attempt to write that contact to that provider, and link its current fields to fields that the provider supports. The user is notified if this imperfectly performed.
}}
