<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 13/03/2013 7:43 PM, Julian Vincent
wrote:<br>
</div>
<blockquote
cite="mid:CABKB0hipmwNqhRwG61WZ6BjAfVUxNYQPRt3rfLXDccVLkQNm-g@mail.gmail.com"
type="cite">
<p dir="ltr">Can I suggest something different ie </p>
<p dir="ltr">1. Since members primarily interact/interface with
their chapters<br>
2. Why not let members sign up on chapter sites instead<br>
3. Chapters can then provide members database to HQ every month
to then be updated into the AMS<br>
4. Hence if prospect new members go to <a
moz-do-not-send="true" href="http://isoc.org">isoc.org</a>,
they will then be pointed to the respective chapter website<br>
5. This way members will get to know their chapters and its
activities before deciding to sign up and hopefully engage and
contribute. <br>
</p>
</blockquote>
<br>
Julian - in practice this is close to how we do it in ISOC-AU now.
Because we charge a membership fee, they have to sign up at our
local webpage so we can capture credit-card details etc, and comply
with Australian privacy legislation.<br>
<br>
The process here in Australia is:<br>
1. Prospective member sign up at isoc.org, and we get them in AMS as
possible members<br>
2. We send them a polite email pointed them to our local membership
signup page at <a class="moz-txt-link-abbreviated" href="http://www.internetsociety.org.au">www.internetsociety.org.au</a>, and pointing out there is
a fee involved<br>
3. Hopefully they fill in our local form, we process their details
and payment<br>
4. We enter them in our local membership system and local mailing
lists<br>
5. If they came through ISOC first, we find their prospective member
record and flag them as a real member of the chapter in AMS<br>
6. If they came to the local site first, we re-key their details
into AMS - eventually.<br>
<br>
For infrequent signups this works OK. If signups were more frequent
we'd want to set up a more automated transfer from our local system
into AMS, rather than re-keying them manually.<br>
Most new members come directly, and bypass the ISOC global site.<br>
<br>
I agree, it would be fantastic if, on the ISOC global page, as soon
as they selected the Australian chapter they were presented with the
link and a message to our local signup page instead of proceeding,
to save the new member-to-be keying in their information twice -.<br>
<br>
(even better, the ISOC site auto-filled-in all the fields in our
local form that the member-to-be has already typed into the ISOC
page!)<br>
<br>
Hope this helps.<br>
<br>
Paul.<br>
<blockquote
cite="mid:CABKB0hipmwNqhRwG61WZ6BjAfVUxNYQPRt3rfLXDccVLkQNm-g@mail.gmail.com"
type="cite"><br>
<p dir="ltr">Thank you. </p>
<p dir="ltr">Cheers,</p>
<p dir="ltr">Julian Vincent<br>
Chair<br>
Malaysian Chapter</p>
<div class="gmail_quote">On Mar 13, 2013 2:52 PM, "Paul Brooks"
<<a moz-do-not-send="true"
href="mailto:paul.brooks@isoc-au.org.au">paul.brooks@isoc-au.org.au</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>On 9/03/2013 1:38 AM, Ted Mooney wrote:<br>
</div>
<blockquote type="cite">
<div>To all Internet Society Chapters,</div>
<div><br>
</div>
<div>ISOC Staff are undertaking a long overdue maintenance
of our database. We are starting with member records
and want you to know the plan and what it means for you.</div>
<div><br>
</div>
<div>Over the course of the next two to four weeks, we
will monitor all primary email addresses of all member
records. Any email address that returns four "hard
bounces" to our system will flag that member record as
"unreachable". At the end of four weeks we will
unsubscribe all such records in the database from
receiving email from ISOC, and we will cancel these
memberships. </div>
<div><br>
</div>
<div>We will not, at this time remove any name from the
database. We will also, within two weeks following this
action, compile a list of all removed members and make
that list available to all Chapters affected. <br>
</div>
</blockquote>
<br>
Ted - can I suggest a better process might be to compile the
list of all candidates for deletion, make that list
available to the chapter to resolve/confirm/check *before*
cancelling the memberships, and only unsubscribe + cancel
those that the chapter confirms are no longer members or
have not been able to contact locally?<br>
<br>
If a contact has multiple email addresses listed, if the
primary one returns bounces will your process attempt to
contact the secondary email addresses before cancelling
their membership?<br>
<br>
<br>
Might be a smaller chance of embarrassing collateral damage
and false negatives causing people to be incorrectly
cancelled and having to be reinstated again if things are
done in this sequence.<br>
<br>
Regards,<br>
Paul.<br>
<br>
<pre cols="86">--
Paul Brooks
Board member
ISOC-AU - Internet Society of Australia</pre>
</div>
<br>
_______________________________________________<br>
As an Internet Society Chapter Officer you are automatically
subscribed<br>
to this list, which is regularly synchronized with the
Internet Society<br>
Chapter Portal (AMS): <a moz-do-not-send="true"
href="https://portal.isoc.org" target="_blank">https://portal.isoc.org</a><br>
</blockquote>
</div>
<br>
-- <br>
This message has been scanned for viruses and
<br>
dangerous content by
<a moz-do-not-send="true" href="http://www.lateralplains.com/"><b>MailScanner
at Lateral Plains</b></a>, <br>
and is believed to be clean.
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
As an Internet Society Chapter Officer you are automatically subscribed
to this list, which is regularly synchronized with the Internet Society
Chapter Portal (AMS): <a class="moz-txt-link-freetext" href="https://portal.isoc.org">https://portal.isoc.org</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="86">--
Paul Brooks
Board member
ISOC-AU - Internet Society of Australia</pre>
</body>
</html>