My script suite to import various data types into an OUCS server is nearly complete - at least it works for many data samples.
The Contacts duplicates are after all checked by "brute force" - verifying presence and value of entries in the user's existing PAB, and not-posting entries from provided VCARD input file to Convergence, accordingly. There are cases when this fails, and a few bugs to iron out, but hopefully this can even become productized some day
New question arose: it seeems that when VCARD markup comes in wrapped lines (like LDIF, ICS and others - if an attribute value is long, it is wrapped at some length limit, with subsequent lines for an attribute starting with a space) and this is fed into Convergence import.wabp, the resulting imported values in the PiServerDB LDAP entries have an embedded line-break - i.e. in the middle of a long name for a "properly" single-valued displayName, etc.
Is there some format mismatch between the standards, the exporting tools we used (DavMail mostly, and our parsing scripts) and the Convergence WABP importer?
Does the WABP importer have any practical line-length limit? We can parse the markup to remove line breaks for such attributes, and feed Convergence some really long unbroken lines as a result - what would happen? in fact, I'll try that soon...
Thanks for any new ideas, and for old help,