<div dir="ltr"><div><div>Hi All.<br></div>Nice suggestions and debate, and I totally agree with Evan. I think It is our prerogative to lead in this field and show what technology can do, improving performance and delivery of service. I suppose the ISOC AMS was configured to meet certain criteria and objective, hence maybe other APIs are unable to integrate with other APPs as Eduardo Diaz asserted. As a developer, I reckon that this can be improved if there necessity beckons. <br>
<br></div><div>We in Kenya have been also thinking of better ways to use "tech" , especially how our local mobile money MPESA can be integrated for membership dues. This and Evan's idea is quite valid and I fully support it. Maybe the AMS administrator / developer could shed more light into these discussions.<br>
<br></div><div>Oharles Oloo<br></div><div><br><br><br><br><br><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Feb 24, 2014 at 8:20 PM, Evan Leibovitch <span dir="ltr"><<a href="mailto:evan@telly.org" target="_blank">evan@telly.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello everyone,<div><br></div><div>We are in the process of automating the Canada Chapter's membership application system using CiviCRM and Paypal, as we will be charging annual dues similar to some other chapters.</div>
<div><br></div><div>I would like to know if anyone at other chapters has tried to integrate the ISOC AMS with their own local membership database. We would like to simplify membership by having a single sign-up page that would enable someone to simultaneously obtain an ISOC Member ID and apply for membership in our chapter.</div>
<div><div><br></div><div>Alternately, are we as a chapter empowered to apply for membership on behalf of someone else, who has come to the Chapter site but does not yet have a global ISOC member ID?</div><div><br></div><div>
What I would like to avoid is a situation in which we turn away members because it's "too much trouble". We need to make it as easy as possible to attract members, and the three step process of </div><div><ol>
<li>Coming to our site to join<br></li><li>Being diverted to the AMS to create a membership and having to remember the ID<br></li><li>Coming back to the chapter site and using the new ID to apply for membership with us<br>
</li></ol></div><div>is IMO working against our ability to build membership. It is easy to complain that people should be able to persist through all those steps, but to me it is unacceptable to have barriers to membership that can be addressed using available technology.</div>
<div><br></div><div>Any suggestions, and especially experiences from others who have encountered this issue, are extremely welcomed. </div><div><br></div><div>Thank you.</div><span class="HOEnZb"><font color="#888888"><div>
<div><br></div>-- <br><div style="text-align:center">
<div style="text-align:left">Evan Leibovitch</div><div style="text-align:left">Toronto Canada</div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div style="text-align:center"><div style="text-align:left">
Em: evan at telly dot org</div></div><div style="text-align:center"><div style="text-align:left">Sk: evanleibovitch</div></div><div style="text-align:center"><div style="text-align:left">Tw: el56</div></div></blockquote>
</div></font></span></div></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 href="https://portal.isoc.org" target="_blank">https://portal.isoc.org</a><br></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><div>Charles Oluoch Oloo<br>Innovative Web Applications Developer<br>
Tel: +254-721-909757, 738-275001 <br></div>Alt. E-mail: <a href="mailto:coloo@kefri.org" target="_blank">coloo@kefri.org</a><br><div> <br><input type="hidden"><input type="hidden"><div></div><input type="hidden"><input type="hidden"><div>
</div></div></div>
</div>