It would be good in this to consider LDAP or other means of getting valid
info for users... What I mean by that is that there would be a way to
customize the way that info is imported from LDAP into the vCard or
CDB_DIRECTORY to allow for listings to be the way each system wants them (so
not forcing LastName, First or FirstName LastName of Blah etc)
> Sun Apr 30 2017 05:57:09 PM EDT from IGnatius T Foobar @ Uncensored
>Subject: Re: Last message was a bit unclear
>
> (continued)
>
>Obviously this needs to change. The vCard shouldn't be the authoritative
>source of the user's email address(es). And of course we're not going to
>share the Global Address Book with other Citadels anymore ... or if we do, it
>won't be driving a downstream address database.
>
>CDB_DIRECTORY can be rebuilt at any time by zeroing it and repopulating it.
>That behavior can continue.
>
>The obvious solution is to just stick all of the user's Internet email
>addresses in the user record. But that's less than optimal because we would
>need to put it in a fixed width field that has finite capacity and still
>consumes all that space per user whether it's used or not.
>
>So we might need a new table that is the opposite of CDB_DIRECTORY, which is
>indexed by user and then contains a variable length record with zero or more
>Internet email addresses for that user. I generally don't like adding new
>tables, but maybe it has to be done here. Or maybe I can add it to the
>CDB_USERSBYNUMBER table which is a simple mapping of user numbers to user
>names. Either way it's one more thing to export/import.
>
>I'm kind of just thinking out loud here.
>
>Any way you slice it, if the CDB_DIRECTORY table is no longer driven from
>the Global Address Book, then the publishing of individual users to the GAB
>becomes completely optional. And if the email addresses in the vCard become
>informational rather than the authoritative source of the user's Internet
>addresses, then it solves the problem of users being able to edit their own
>addresses.
>
>
>
>
