Hi, all. I'm just starting out with LDAP, so before I even start with the
technical details of my project (which is to make an address-book system
suitable for use with Mozilla Thunderbird and (if possible) Outlook and
Outlook Express, I'm trying to figure out just how to organize my data.
This being a church, there are a number of different "units" that I have to
deal with. Here's just an example:
- A family (husband, wife, N-number of children) with a single family e-mail
address.
- A single person with an e-mail address.
- A single person with a home and work e-mail address.
- A family with multiple e-mail addresses (husband email #1, husband email
#2, wife email #1, child email #1, whole-family email #1)
So here's a hypothetical family:
husband: John Doe
wife: Jane Doe
child #1: Suzy Doe
child #2: Billy Doe
husband e-mail #1: [EMAIL PROTECTED]
husband e-mail #2: [EMAIL PROTECTED]
wife e-mail #1: [EMAIL PROTECTED]
child #1's email #1: [EMAIL PROTECTED]
My question is, what kind of LDAP records can I make that can accomodate
this type of arrangement? If I was doing this in SQL, I might just break
every individual out into separate records (with each individual having a
one-to-many table to connect them to their e-mail addresses), then use other
tables to define which individual records are connected, making up a family.
But having just started LDAP, I don't really know how to set this up.
For instance, I thought about just having a single "Family Unit" LDAP record
that would store everything about a family (and would be flexible enough to
handle a family of 1 person or 15 people). But what made it complicated is
is that I want people to be able to search for "John Doe" in Mozilla
Thunderbird and have it automatically present BOTH of his e-mail addresses
as options. So it seems to me that I need to have separate LDAP records for
both of John Doe's e-mail addresses.... right?
But if I do that, how can I avoid having to duplicate all the OTHER data
about John Doe (address, city, state, etc.) that I want to keep in a single
record? Can I define a "family" record that has the whole Doe family's
info, then a separate "stub" record that has only their e-mail addresses,
which can somehow be tied back to the Doe family's main record?
My apologies if I using the wrong terminology or anything here! Like I say,
I can picture how I might do it in SQL, but I don't know enough about LDAP
to know even how to begin with this (i.e. whether I'm going to need to
create new schemas or anything.)
Thanks to anyone who can help!
_________________________________________________________________
Refi Now: Rates near 39yr lows! $430,000 Mortgage for $1,399/mo - Calculate
new payment
http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-17727&moid=7581
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
