3 ms·
The intention of this project is great. But I doubt if it can even work well. The whole project depends on the fact that everything to synchronize can be standa
by flying_sheep 8y ago
The intention of this project is great. But I doubt if it can even work well. The whole project depends on the fact that everything to synchronize can be standardized. But this is almost impossible.
Let's say "Birth of Date". Some contact providers support BOD without year. But some support only the whole date. If the companies do no even agree on this tiny little item, how can they agree on larger deviations? Like max number of phone numbers in a contact profile? The size/format of profile image? Address format? and so on
- rdiddly 8y agoTo me it doesn't seem like the rocket science you're making it out to be. Most teams store data in non-silly ways that correspond to the common reality that the data represent. For example everybody knows what a date of birth is, and that it has a day, month and year. If the year is missing from the source data, you set it null in your intermediary data model. If it's required in the destination data... basic solution would be choose a default and notify the user; deluxe solution would be to give them some choices up front what to do about it (since you'll already know about the mismatch based on knowing the source & destination providers). Max number of phone numbers: if the source contains more than the destination's max, stop at the max (basic) or display a list and ask the user to eliminate some (deluxe).