RE: [Phpgroupware-developers] address book

[Brian Johnson]

Now I'm spouting off a bit on something I don't totally understand

My understanding of the LDAP standard allows users to create information and
stick it in with whatever formatting they want - just like any other
database

I think that there is a standard for contact info in LDAP directories but it
still may not suit our purposes.  Does the LDAP standard include the data
format for contact information including the separation of individuals and
organizations?

Also, LDAP installation and use is a PAIN IN THE BUTT!  Only a few Linux
distros support it as part of their package and even then, it doesn't
install smoothly.  I found finding complete documentation (as in How-to's)
to be problematic and there are few user-friendly LDAP clients (for Linux)

All I wanted to do was switch to LDAP for user authentication so that I
wouldn't have to make user accounts for the system and separate ones for
phpgw - it caused problems with rpm of all things - I switched back after a
month of struggling

To force phpgw users to use LDAP is NOT _the_ anwser until LDAP matures into
a more user friendly system



-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf Of Buchan Milne
Sent: Tuesday, April 16, 2002 4:44 AM
To: address@hidden
Subject: Re: [Phpgroupware-developers] address book


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Reading this thread, I can't help thinking that you guys are talking
about LDAP. IMHO, LDAP should be the preferred contacts storage backend,
simply because:

a)There is a standard
b)It is supported by almost all software. Outlook, Outlook Express,
Mozilla, Netscape, Pegasus Mail, Evolution etc all support it to
different extents.

So, I think that any thoughts on this should include the possibility of
easily migrating to LDAP (ie importing contacts from Outlook, Outlook
Express etc into LDAP).

Buchan



address@hidden wrote:
| On 16 Apr 2002 at 9:14, Peter Moulding wrote:
|
|
|>I agree with the need to expand the address book. My own preference is
|>to adopt the parent child system used in some other phpgw tables.
|>
|>Let us enter companies as parents and people as children of the company
|>entries. If a person needs departments, they can add the departments as
|>the children and people as grandchildren.
|>
|>This would allow any structure without additional tables.
|>
|>Peter
|>
|
|
| i have exactly done this separation into organizations and
individuals. i used the exsting
| addressbook as basis and normalized the table structure.
| the next thing i'm working on is a migration tool from the "old"
addressbook to the new one.
|
| the app is already working and it would be great if some of you would
test it and give me their
| opinion about it. i only have to fix some major bugs this day and
could make it available this
| evening.
|
| heiko
|
|
| _______________________________________________
| Phpgroupware-developers mailing list
| address@hidden
| http://mail.gnu.org/mailman/listinfo/phpgroupware-developers



- --
|----------------Registered Linux User #182071-----------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE8u+RUrJK6UGDSBKcRAoQjAJ9bTc8HWL0LnbjLF9rx1BVE3szpIACcCgbY
uo6GBDrSXJn/ewE5g9Bs2Xk=
=voPK
-----END PGP SIGNATURE-----


_______________________________________________
Phpgroupware-developers mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/phpgroupware-developers