• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 328
  • Last Modified:

EmaiilGroups_TableDesigns

Does anyone havea good DB design for creating and soring email group lists.

Basically I have a contacts table with a structure like

contactid
first_name
last_nameemail_address
phone
cellphone
etc.

I have several applications and i need to alert several users after different processes execute.

For example, the production group may want to send john@aol.com and mike@aol.com after Production job runs.

QA group may want to send johN@aol.com and alice@aol.com after QA process runs.

etc,. etc.

so I am thinking of creating another table for storing Email groups with a list of the people that should receive the emails.
The list can be updated (i.e remove people and add new people).
0
sam15
Asked:
sam15
1 Solution
 
slightwv (䄆 Netminder) Commented:
I assume the question here is if there are other options?

What you describe is like a disto list and is what I would probably do.  This way, changes can be done with a table insert or delete not an app change.

I might also suggest the core table you describe can be deemed not normalized.  What if I have two email addresses or phone numbers?

Might want to add a contact-types table with the unique types then a intermediate table, person-contacts table to resolve the many to many relationships.
0
 
Wasim Akram ShaikCommented:
I agree with slightwv that you may have this issue of many-many relationships...

I had got this similar situation long back, instead of mails we use trigger sms after the activity completion..

will post the description of my table may be it will work for you too...



Module   varchar2(100),    --- name of the module on which alert has to be sent, group all contacts by their modules(in your case it is activity)
Owner     varchar2(100),    --- to all the concerned persons to whom alert(email here) to go
threshold  varchar2(100), --- you can ignore this, its needed incase of escalations(not applicable here for you)
alert_flag   varchar2(1) default 'Y', -- this is to be used for whether alert is to be triggered or not, using this you can avoid deletion of records if no alert has to be sent.
mobile_no  number, -- contact number of person to whom alert has to be sent
email_id varchar2(200) -- email id of contact to whom alert has to be triggered
last_update_date date, -- last date of when the alert has been triggered
remarks      varchar2(200)  --- can be used for your own tracking purposes aftr program completion...
0
 
BuggyCoderCommented:
assuming that contactid is primary key for all the contacts, i would rather have table like this to store groups for one job
groupid int (Primary Key)
jobid int (Foriegn key from some other table that contains job information)
groupName varchar(100)(Just a friendly name for group)
groupDetail xml(contacts that are part of this group represented in xml)

xml can look like this:-
<group>
<Contact>
<Id>1</Id>
<Name>John</Name>
<Email>john.j@test.com</Email>
</Contact>

<Contact>
<Id>2</Id>
<Name>mark</Name>
<Email>mark.a@test.com</Email>
</Contact>
</group>

Open in new window

0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
sam15Author Commented:
Yes, A person might have multiple emails.

I thought there would be some standard schema design for something like this. I was trying to pick up some ideas. I have seen some databases where they store the email distribution lists as a long string separated by commas like (joe@aol.com,mike@yahoo.com,susan@msn.com).
I think though this is not good normalized solution and difficult to maintain.

But it seems to me the ERD would be like

USERS can have ONE OR MANY email addresses.
EMAIL GROUPS/LISTS can have ONE OR MANY USERS.

It seems to me this requires 4 tables:
a) CONTACTS to store user info,
b) CONTACTS_EMAILS to store email addresses,
c) EMAIL_GROUPS to store email distribution lists
d) EMAIL_LOG to store the email information to be sent via job.

Any ideas, or links with sample schemas for this.
0
 
BuggyCoderCommented:
why don't you like to go for xml option....
any specific reasons for that....
0
 
slightwv (䄆 Netminder) Commented:
>>I think though this is not good normalized solution and difficult to maintain.

Agreed.

>>But it seems to me the ERD would be like

I'm thinking (off the top of my head...might need tweaked a little):
contacts: contact_id, name (or first and last)
       1, Larry
       2, Moe
       3, Curly
contact_methods: method_id, type
       1, email
       2, phone
       3, carrier pigeon

contact_contact:  cc_id, contact_id, method_id, value, is_primary
       1,1,1,'larry@stooges.com','Y'
       2,1,2,'1112223333','Y'
       3,2,1,'moe@stooges.com','Y'

email_groups:  group_id,group_name
       1,'Stooges'

email_group_members: member_id, group_id, cc_id
       1,1,1
       2,1,3
     

       

>>why don't you like to go for xml option

XML can be hard to maintain.  To do a simple phone number change involves opening/updating the entire XML doc likely with the DOM.

Imagine removing a 'type' all together:  Since Carrier Pigeons are extinct:  Just delete a few rows.  If stored in XML, deleted nodes from every record.  Very messy.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now