Re: Modeling User/Accounts


mySpamB8@xxxxxxxxx wrote:
I have a system with the following concepts:
*Programs (As in social service programs)
*Program Contacts (people who are associated with programs)
*Application Users (most users are Program Contacts, but some users are
system admins who aren't associated with a program)

All the above is fairly easily modeled, I think. However, I hit a snag
with the following spec:
*Application Users need an email address (for password retrieval
purposes).

Most users are program contacts, so for them, it's no problem getting
the email address from the ProgramContact instance. However, what do I
do for Users who happen not to be ProgramContacts? This email address
ought to be shared somehow, but I can't figure out how to model it.

Any tips would be appreciated.

From a relational perspective, I find that a Contact table is often
warrented. A given person or organization may have zero, one, or many
contact records. Sometimes such is overkill, but it is flexible in that
any entity can use it and any entity can have any number of contacts
(if permitted).

Typical contact table columns:

FirstName
LastName
MiddleInitial
Title
OrganizationName
Street_1
Street_2
City
State
Zip
Country
DayPhone
EveningPhone
Email
OtherNote (for pager, fax, IM, Rocket#, etc.)

Name info may not be needed in some cases if the entity (person or
business) already has one.

-T-



Thanks,
Jamie

.

Relevant Pages

  • Modeling User/Accounts
    ... *Programs (As in social service programs) ... the email address from the ProgramContact instance. ... ought to be shared somehow, but I can't figure out how to model it. ...
    (comp.object)
  • Re: Modeling User/Accounts
    ... *Programs (As in social service programs) ... system admins who aren't associated with a program) ... ought to be shared somehow, but I can't figure out how to model it. ...
    (comp.object)