Sandy Drobic wrote:

Robert Lewis wrote:

...

So, here is an example. League official his honor Mr. Smith wants to set up a mailing list for his baseball league.

Picture a hierarchical tree, with "ALL" at the root. "ALL" is an email list that contains everybody's name, email, phone#, etc. A subset of "ALL" is "LEAGUE", which contains players, coaches, parents, hot-dog vendors, stadium managers, etc. That is, everybody connected with the league, but not Mr. Smith's other contacts (like his friends, his family, etc)

So, under "LEAGUE" are folders for each team. and for food-vendors, umpires, coaches, each stadium. AND, get this, any one person can appear in any, or all lists.

If a person is added to a particular team, his info should *automatically* be added to all of the nodes above him. In this example adding to "team" should automatically add to "LEAGUE" and to "ALL".

This is a job for a sql database, where you have a web interface for managing the users/groups. Adding/deleting/moving users is a job for a script.

...

info cards should be able to be graphically drag-n-dropped to copy or move between nodes.

That would be difficult for a web interface, though not impossible to do.

...

Individuals need to be identified across several fields, not just email address or phone number because several people, like husband and wife, might share the same email and phone number. Thunderbird fails this.

Integrated with email for sending to everybody in a list. If two lists are emailed to, no dups should be sent.

Again, this is a job for a sql query.

So, how much is your client willing to pay for this? If it is not in the 4 digit range, you need some poor sod that won't be paid for the work.

Thanks Sandy. It's for a church so that probably tells you how much someone is likely to pay. Someone suggested using LDAP. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org