Our data will come from a SQL query as well. I have gotten a sample of the data (the real data will have to be cleaned) and was going to see if I could put together a CJLI stream that would build a set of lists and add the initial subscribers. Since this is real data, I'll mangle the addresses. As mentioned in my first post, most of the header will be standard boilerplate, with only a few changes (listname, description, owner(s), expiration date ) performed as needed.
There is some desire to have the owners have the ability to turn archives on. So ... I dunno
________________________________________
From: LISTSERV site administrators' forum [[log in to unmask]] on behalf of KC Wise [[log in to unmask]]
Sent: Thursday, May 16, 2013 7:39 PM
To: [log in to unmask]
Subject: Re: Creating Lists by the hundreds (thousands?)
Looking forward to the answers here as well. I've got hundreds of list that
need to be created. Most of them dynamic lists via SQL Query.
Thanks
KC
-----Original Message-----
From: LISTSERV site administrators' forum
[mailto:[log in to unmask]] On Behalf Of F J Kelley
Sent: Thursday, May 16, 2013 4:01 PM
To: [log in to unmask]
Subject: Creating Lists by the hundreds (thousands?)
Hello Folks,
This *seems* like something others will have done, so I thought I'd ask ...
We make a good deal of use of course management software. There is a
concern the mail software in these might allow the harvesting of email
addresses. There are two alternatives:
-- Exchange Distribution Groups (the campus uses hosted Exchange for email)
-- Listserv.
Each class would have a list or group associated with it.
Using Powershell, we could script the creation of groups, then turn these
over to the owners. The groups/lists would be populated based on who has
signed up for the course. Over the semester, some students will join and
others will leave, and this could be handled by the group management
features of Outlook Web App (OWA). However, FERPA restrictions mean some
students cannot be added with the GUI (they do not appear in the Global
Address List), and there is a general preferance the groups themselves be
hidden from the Address List, so someone (us) would be doing group
management. A lot of it.
With a Listserver, the same data used to create the group could be used to
populate the list. Creating the list header is not that difficult (most of
the settings would be unchanged no matter the list, including secondary
owners).
Still, we could expect hundreds, perhaps thousands of lists to be requested
essentially by machine.
As my note began, I suspect others have dealt with problems much like this,
and I was wondering how they had solved it.
Thanks for any help/thoughts/etc
--Joe
############################
To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
############################
To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
############################
To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
|
