<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/02/16 22:52, David Lloyd wrote:<br>
</div>
<blockquote cite="mid:006601d164c2$ac0e8200$042b8600$@adam.com.au"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Neil,
it’s actually not clear to me what’s broken about the
current memberdb … I actually think we’re concentrating on
technical issues when the problem isn’t technical.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I
commend your work on membershipdb-ng.</span><br>
</p>
</div>
</blockquote>
<br>
It's a fair question David - and perhaps I haven't outlined the
problem we're trying to solve clearly. <br>
<br>
The current MemberDB has *broken* functionality in the following
ways:<br>
<ul>
<li>Membership reporting is inconsistent, and we require
consistent reporting to meet compliance requirements under the
Fair Trading Act (NSW), as LA is an incorporated association. </li>
<li>The platform itself is aged, and runs on a difficult to
support code base (an old version of PHP)</li>
</ul>
The current MemberDB has functionality *gaps* in the following ways:<br>
<ul>
<li>Memberships are not renewed, so we don't havea way to expire,
or confirm currency of Membership</li>
<li>There are no targeted communications functionality - so we
can't email subsets of Members, such as those in Victoria, those
who are female - to provide useful information</li>
<li>We use a variety of tools to manage memberships of committees,
and the current Membership platform does not make this easier. <br>
</li>
</ul>
A list of requirements was started at; <br>
<a class="moz-txt-link-freetext" href="https://docs.google.com/document/d/1tyTA3Fj5J9XL2D7UTIxw46smXGrLM5J-fI4g6GxK9hM/edit?usp=sharing">https://docs.google.com/document/d/1tyTA3Fj5J9XL2D7UTIxw46smXGrLM5J-fI4g6GxK9hM/edit?usp=sharing</a><br>
<br>
and I'd warmly welcome contributions to this. <br>
<br>
Kind regards,<br>
Kathy<br>
<br>
</body>
</html>