<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"> 
    
<channel>
    

    <title>Idea #9: It&#8217;s time for a systems upgrade</title>
    <link>http://blogs.jta.org/ENTRY_PERMALINK_HERE/idea-9-its-time-for-a-systems-upgrade/</link>
    <description>Let&#8217;s pool our resources and build the strongest technical backend we can for the organized Jewish world.</description>
    <dc:language>en-us</dc:language>
    <dc:creator>littletinbox@gmail.com</dc:creator>
    <dc:rights>Copyright 2010</dc:rights>
    <dc:date>2010-02-09T;20:12:00-05:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.pmachine.com/" />
 


    <item>
      <title>Comment by Harlan Cohen</title>
      <link>hrcohen@ameritech.net</link>
      <description>&#8220;Time and again I’m struck by how under&#45;resourced the back&#45;end is, even at large Jewish institutions. Our user databases are static and full of holes in the data, making it near impossible to target our outreach and communications. So we rely on an outdated broadcast model and wonder why we have a hard time reaching people. That’s just one example.&#8221;


I think you are completely aware why back end systems languish, but allow me to elaborate for you. 


In my limited exposures to fundraising and synagogue administration (two separate experiences), I perceive progress is not made any faster than a key leader wills it.


When my synagogue first went to personal computing for the administrative system, it was soon settled that Apple Macintosh&#8217;s would not be in the mix and monitors would be gray&#45;scale and not color. This is about the time DOS was still prevalent and Windows was becoming interesting. These were cost savings but completely arbitrary and disregarding of trends and science (the human capacity to get more information out of color displays) in the latter case. But a complete fit to the chairman&#8217;s (a very competant executive of a tech company) view of the world.


When my university employer was discussing a full blown alumni web site, we saw the bells and whistles in demos and could not determine how to proceed because we really didn&#8217;t know what was most important to our prospective audience nor what would justify the expense. Leadership was rightly focussed on the close of a capital campaign but the alumni board wanted some attention to this languishing issue.


So are you certain of your audience (who they are, what they need and what they want and the difference between the two) and the priorities on the organization&#8217;s part (generally saving money or increasing revenue and hopefully both)?


At another university the change over to client&#45;server from mainframe alumni and development system was as much a product of the desire of the university to rid itself of the mainframe operating and maintenance costs as much as anyone thinking the new software was.in some way a salvation.


I understand third&#45;hand that one Jewish Federation group had a fine administrative system that also allowed other federations to outsource access and work. The demise of the hardware vendor seems to have broken those relationships and the consulting firm that implemented the system was not involved further with that federation or any other. At least I never heard more about it.


So do relationships continue to thrive if the infrastructure is ignored or did the infrastructure fail to evolve because the relationships were not thriving?


Since volunteerism is encouraged in both universities and synagogue venues, the resources obtained aren&#8217;t necessarily the resources you need. Nor will minimally salaried positions draw people with cutting edge skills.&amp;nbsp; If we could build systems that acted the same only better after ten years, this wouldn&#8217;t be so much of a problem. But developers want to keep trying new paradigms and forgetting old ones until they resurrected in the next full generation of methodologies and tools. 


So I hope you appreciate what I wrote and I hope I didn&#8217;t take up too much of your time in the reading.</description>
      <content:encoded><![CDATA[<p>&#8220;Time and again I’m struck by how under-resourced the back-end is, even at large Jewish institutions. Our user databases are static and full of holes in the data, making it near impossible to target our outreach and communications. So we rely on an outdated broadcast model and wonder why we have a hard time reaching people. That’s just one example.&#8221;
</p>
<p>
I think you are completely aware why back end systems languish, but allow me to elaborate for you. 
</p>
<p>
In my limited exposures to fundraising and synagogue administration (two separate experiences), I perceive progress is not made any faster than a key leader wills it.
</p>
<p>
When my synagogue first went to personal computing for the administrative system, it was soon settled that Apple Macintosh&#8217;s would not be in the mix and monitors would be gray-scale and not color. This is about the time DOS was still prevalent and Windows was becoming interesting. These were cost savings but completely arbitrary and disregarding of trends and science (the human capacity to get more information out of color displays) in the latter case. But a complete fit to the chairman&#8217;s (a very competant executive of a tech company) view of the world.
</p>
<p>
When my university employer was discussing a full blown alumni web site, we saw the bells and whistles in demos and could not determine how to proceed because we really didn&#8217;t know what was most important to our prospective audience nor what would justify the expense. Leadership was rightly focussed on the close of a capital campaign but the alumni board wanted some attention to this languishing issue.
</p>
<p>
So are you certain of your audience (who they are, what they need and what they want and the difference between the two) and the priorities on the organization&#8217;s part (generally saving money or increasing revenue and hopefully both)?
</p>
<p>
At another university the change over to client-server from mainframe alumni and development system was as much a product of the desire of the university to rid itself of the mainframe operating and maintenance costs as much as anyone thinking the new software was.in some way a salvation.
</p>
<p>
I understand third-hand that one Jewish Federation group had a fine administrative system that also allowed other federations to outsource access and work. The demise of the hardware vendor seems to have broken those relationships and the consulting firm that implemented the system was not involved further with that federation or any other. At least I never heard more about it.
</p>
<p>
So do relationships continue to thrive if the infrastructure is ignored or did the infrastructure fail to evolve because the relationships were not thriving?
</p>
<p>
Since volunteerism is encouraged in both universities and synagogue venues, the resources obtained aren&#8217;t necessarily the resources you need. Nor will minimally salaried positions draw people with cutting edge skills.&nbsp; If we could build systems that acted the same only better after ten years, this wouldn&#8217;t be so much of a problem. But developers want to keep trying new paradigms and forgetting old ones until they resurrected in the next full generation of methodologies and tools. 
</p>
<p>
So I hope you appreciate what I wrote and I hope I didn&#8217;t take up too much of your time in the reading.
</p>]]></content:encoded>
    <dc:date>2011-02-25T;01:28:00-05:00</dc:date>
    </item>

 
</channel>
</rss>
