The mailing list for listmasters using Sympa

[Dallas Wisehaupt <address@concealed>]

We will be extracting the data for section and termcode from either our
central LDAP or the ERP system.

So the process in my mind right now is:
    1. get a list of courses running this term from LDAP or ERP
    2. generate family XML file for this term with a list root for each
       section
    3. add the lists using the --instantiate_family function for families
    4. figure out what to do when individual courses are added or
       dropped mid term
    5. at a point after the term is finished, close and remove all of
       the lists in this family

What I'm trying to flesh out at this point is step 2. One option is to
include the full queries in the XML file so that they are present for
each list. The other option, that I was kind of hoping for, is just
putting stubs for the queries in the XML and handle the meat of the
queries in a common inclusion file.

I know I can pull off the stubs for owners and moderators. If I have to
put the full query in for the subscribers that is fine. I am currently
using that approach for testing with a stub for owners and a 2 level
ldap query for the subscribers. I was just figuring we could cut down on
the replication of data and possibilities for error.

At this point, there will be a correlation between the list address and
the section and termcode. But, I haven't looked at any direct
relationship in the config file that would specify that.

Dallas

On Thu, 12 Apr 2007, Thomas Berry wrote:

> I agree, Sympa's list family feature is the way to go.  But, where is the 
> data for COURSE_SECTION and TERMCODE coming from?   Is it parsed from the 
> mailing list email address?
>
> Thomas
>
> Sylvain Amrani wrote:
> > Hi,
> >
> > You can use families to do that. You parameters are entries in your xml
> > file.
> >
> > You can also use ldap2_level queries :
> >
> >    1. you store your source_parameters in your ldap directory
> >    2. the 1st ldap query requests the source_parameters
> >    3. the 2nd ldap query use the result of the 1st one.
> >
> > Sylvain.

--
Dallas Wisehaupt                            Systems Administrator
address@concealed               The University of Scranton