Hi all, John Lance here. You may remember me from such past blog postings as "Exporting Contacts" and "Lance 4 U.S. Prez" (remember, I have not been endorsed by any political party, Hollywood folks, or anyone in the media. And if that doesn't make me appealing, I don't know what will. - Our slogan: "John Lance: Willing to say he believes in what you believe in to get your vote.")
Moving right along...
Along with the exporting of contacts we are examining the importing of contacts, specifically around the Comma Seperated Value (csv) and other similar formats. One of the questions we are examining is how to allow Samantha and Ted to map the source file fields. Since a csv files format can vary depending on the source (for example, a Yahoo CSV will not necessarily match an Outlook CSV) there is always the chance that Ted will have to tweak how the fields are mapped. So a silly example would be if the CSV's first name field was being mapped to the last name field and vice versa. Ted could use the mapping utility to go in and correct that prior to importing.
Ok, so now that you have the background, here's the question.
When Ted imports a bunch of contacts, does he need the ability to do a "one off" mapping. For example, if he is importing 20 contacts, of which 19 have been mapped correctly but 1 has been erroniously mapped, do you think Ted would like to "remap" that one contact or is he more likely to simply import all 20 and then go in and edit the one erronious contact? Oh, and if you think a "one off" is needed, please try to give specific use cases or examples.
Thanks. And remember, vote Lance in '08 - cause he believes what you believe.
Mapping Imported Contacts