The mailing list for listmasters using Sympa

[Michelle Murrain <address@concealed>]

Hi there,

First, thanks for the feedback on the db dump. It was basically what I 
needed, although not what I wanted. But it was enough.

I'm in the process of embarking on integrating Sympa with my open source 
web database system. I have a pretty specific list of features I need, 
and I am looking for advice and ideas. I'm finally going to get to use 
the db features of sympa that I chose it for in the first place, which 
is making me happy.

First, one of the things that I want/need, which is slightly separate 
from the integration issue, but a necessary part of the project, is an 
interface which allows users to choose the lists they'd like to 
subscribe to, in a simple, one page form.

For example, organization (domain) x has 5 lists: announce, events, 
discussion, foo_committee and bar_committee. They want an interface 
which allows people to subscribe and unsubscribe from their 5 lists via 
a set of check boxes (you've seen those interfaces).

Has anyone written an interface like that? Is it possibly in process for 
sympa development?

I'm thinking of two different avenues to do this: 1) direct interface 
with the database, or 2) Sending sympa the requests (either by email or 
via web services), which does allow sympa to handle the request, and do 
what might be appropriate (wait for approval, confirm etc.).

Has anyone done this sort of thing? What strategy did you use?

Now to the fun part: integration

The web database system I want to integrate with sympa does standard 
database stuff providing password protected access to content, database 
tables. It includes on-the-fly form generation, plus, now (this is the 
important part) personalized email based on record data and sets of 
selection criteria.

Basically, what I'd like to do is use the sympa database as the base 
repository of the data, and have Xina (the name of the system) read 
information from the sympa data. Part of the challenge is that the sympa 
database holds data for many domains - meaning there needs to be a way 
to segregate data by domain.

I have two ideas, and I'm realizing I'm liking one better, but here goes 
- this does mean I have to add a column to the subscribers_table with 
domain.

1) Write a script that runs nightly, and syncs a set of tables for each 
domain that the Xina system can read (and write to). This has the 
advantage of allowing data from the Xina system to make it into sympa. 
The disadvantage is that its periodic, thus not really 'live' data.

2) Use views. Create a view that selects data from the sympa table by 
domain, which then the Xina system can read. I like this one best, 
because it is absolutely live data, and also it lets sympa do what it 
does best, manage subscriptions.

Thanks for your sage comments.
--
.Michelle

--------------------------
Michelle Murrain
mmurrain at dbdes dot com
413-222-6350 ph
617-889-0929 ph
952-674-7253 fax <--- new
Page: address@concealed
AIM:pearlbear0 ICQ:129250575
Y!: michelle_murrain Jabber: address@concealed

"Work like you don't need the money. Love like you've never been hurt. 
Dance like nobody's watching." - Satchel Paige