User Tools

Site Tools


scratchpad

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
scratchpad [2011/06/09 14:53] drdatascratchpad [2011/06/09 16:12] drdata
Line 17: Line 17:
 <tr> <tr>
 <th width="20%" align="left">Apache</th> <th width="20%" align="left">Apache</th>
-<td align="left"><a name="Apache"></a>Apache is <strong><a href="#open_source">open source</a></strong> Web server project that develops and maintains the Web server software used by <strong><a href="#Evergreen">Evergreen</a></strong>. It is the most popular Web server software and is used throughout the Web. The project began in 1994. The Apache software Foundation&#8217;s Web site is <a href="http://httpd.apache.org/">http://httpd.apache.org/</a>.+<td width="80%" align="left"><a name="Apache"></a>Apache is <strong><a href="#open_source">open source</a></strong> Web server project that develops and maintains the Web server software used by <strong><a href="#Evergreen">Evergreen</a></strong>. It is the most popular Web server software and is used throughout the Web. The project began in 1994. The Apache software Foundation&#8217;s Web site is <a href="http://httpd.apache.org/">http://httpd.apache.org/</a>.
 </td> </td>
 </tr> </tr>
Line 24: Line 24:
 <th align="left">Brick</th> <th align="left">Brick</th>
 <td><a name="brick"></a><br /> <td><a name="brick"></a><br />
-In an <strong><a href="#Evergreen">Evergreen</a></strong> installation, a &#8220;brick&#8221; is a unit consisting of one or more servers. It refers to a set of  servers with <strong><a href="#ejabberd">ejabberd</a></strong>, <strong><a href="#Apache">Apache</a></strong>, and all applicable Evergreen services.  It is possible to run all the software on a single server, creating a  &#8220;single server brick.&#8221;  Typically, larger installations will have more than one such brick and, hence, be more robust.</p> +<p>In an <strong><a href="#Evergreen">Evergreen</a></strong> installation, a &#8220;brick&#8221; is a unit consisting of one or more servers. It refers to a set of  servers with <strong><a href="#ejabberd">ejabberd</a></strong>, <strong><a href="#Apache">Apache</a></strong>, and all applicable Evergreen services.  It is possible to run all the software on a single server, creating a  &#8220;single server brick.&#8221;  Typically, larger installations will have more than one such brick and, hence, be more robust.</p> 
-Bricks will vary according to local requirements but a small brick might have one &#8220;head&#8221; with (<strong><a href="#ejabberd">ejabberd</a></strong>, <strong><a href="#Apache">Apache</a></strong>, and open-ils.settings) and one or more &#8220;drones&#8221; which will handle general application processing.</p>+ 
 +<p>Bricks will vary according to local requirements but a small brick might have one &#8220;head&#8221; with (<strong><a href="#ejabberd">ejabberd</a></strong>, <strong><a href="#Apache">Apache</a></strong>, and open-ils.settings) and one or more &#8220;drones&#8221; which will handle general application processing.</p>
 </td> </td>
 </tr> </tr>
Line 31: Line 32:
 <tr> <tr>
 <th align="left">The Cathedral &amp; the Bazaar</th> <th align="left">The Cathedral &amp; the Bazaar</th>
-<td align="left">A book written by Eric S. Raymond (O&#8217;Reilly, 1999). A must read if you are new to <strong><a href="#open_source">open source</a></strong></p> +<td align="left">A book written by Eric S. Raymond (O&#8217;Reilly, 1999). A must read if you are new to <strong><a href="#open_source">open source</a></strong> 
-Librarians who read it and hear the poetry behind the details will realize that open source works very much like we do.</p> +<p>Librarians who read it and hear the poetry behind the details will realize that open source works very much like we do.</p> 
-Wikipedia has a short discussion of the major principles of open source development in its entry on this book:<br />+<p>Wikipedia has a short discussion of the major principles of open source development in its entry on this book:<br />
 <a href="http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar">http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar</a></p> <a href="http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar">http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar</a></p>
-The essay is also available on the Web at Raymond&#8217;s Website, although the printed version is easier to read:<br />+<p>The essay is also available on the Web at Raymond&#8217;s Website, although the printed version is easier to read:<br />
 <a href="http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/">http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/</a></p> <a href="http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/">http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/</a></p>
 </td> </td>
Line 42: Line 43:
 <tr> <tr>
 <th align="left">Cloud computing</th> <th align="left">Cloud computing</th>
-<td align="left"><a name="cloud"></a>&#8220;&#8230;Web-based processing, whereby shared resources, software, and information are provided to computers and other devices (such as smartphones) on demand over the Internet.&#8221; <a href="http://en.wikipedia.org/wiki/Cloud_computing">http://en.wikipedia.org/wiki/Cloud_computing</a>.</p> +<td align="left"><a name="cloud"></a>&#8220;&#8230;Web-based processing, whereby shared resources, software, and information are provided to computers and other devices (such as smartphones) on demand over the Internet.&#8221; <a href="http://en.wikipedia.org/wiki/Cloud_computing">http://en.wikipedia.org/wiki/Cloud_computing</a>. 
-ILS vendors offer hosting where they manage the servers used by the online catalogs of libraries and provide access to those catalogs via the Internet. Terms such as <em>Software as a Service (SaaS)</em> refer to these kinds of services. In this sense, all such hosted solutions used by libraries are cloud computing and <strong><a href="#Evergreen">Evergreen</a></strong> was doing cloud computing before the term became popular. As with many new things in the IT world, the definition of what constitute cloud computing is a bit fuzzier and covers a multitude of computing arrangements.</p>+ 
 +<p>ILS vendors offer hosting where they manage the servers used by the online catalogs of libraries and provide access to those catalogs via the Internet. Terms such as <em>Software as a Service (SaaS)</em> refer to these kinds of services. In this sense, all such hosted solutions used by libraries are cloud computing and <strong><a href="#Evergreen">Evergreen</a></strong> was doing cloud computing before the term became popular. As with many new things in the IT world, the definition of what constitute cloud computing is a bit fuzzier and covers a multitude of computing arrangements.</p>
 </td> </td>
 </tr> </tr>
Line 49: Line 51:
 <tr> <tr>
 <th align="left">commit</th> <th align="left">commit</th>
-<td align="left"><a name="commit"></a>To make proposed changes in software code permanent. In open source software development, the ability to commit is usually limited to a core group of experienced, skilled developers.</p>+<td align="left"><a name="commit"></a>To make proposed changes in software code permanent. In open source software development, the ability to commit is usually limited to a core group of experienced, skilled developers.
 </td> </td>
 </tr> </tr>
Line 55: Line 57:
 <tr> <tr>
 <th align="left">community</th> <th align="left">community</th>
-<td align="left"><a name="community"></a>In the <strong><a href="#open_source">open source</a></strong> world, there is much talk about the &#8220;community&#8221; of users and developers of the software. In open source development, the term “community” usually refers to users and developers who work in concert to develop open source software, communicating openly and collaborating on the direction of the project. Effectively, these software projects and their development courses are directed by the community through email lists, IRC channels, and an array of communications mechanisms. As a result, anyone in the community can develop improvements to the software and those improvements come not just from a relatively small number of developers at a company which owns the software.</p> +<td align="left"><a name="community"></a>In the <strong><a href="#open_source">open source</a></strong> world, there is much talk about the &#8220;community&#8221; of users and developers of the software. In open source development, the term “community” usually refers to users and developers who work in concert to develop open source software, communicating openly and collaborating on the direction of the project. Effectively, these software projects and their development courses are directed by the community through email lists, IRC channels, and an array of communications mechanisms. As a result, anyone in the community can develop improvements to the software and those improvements come not just from a relatively small number of developers at a company which owns the software. 
-A robust community surrounding an open source project creates an environment that is similar to that a proprietary vendor has from a large customer base. Robust communities create a larger pool of resources to sponsor and contribute to projects. Such communities also mitigate risk for users of the software.</p>+<p>A robust community surrounding an open source project creates an environment that is similar to that a proprietary vendor has from a large customer base. Robust communities create a larger pool of resources to sponsor and contribute to projects. Such communities also mitigate risk for users of the software.</p>
 <p><strong><a href="#Evergreen">Evergreen</a></strong> has an active community and its Web home is at: <a href="http://www.open-ils.org">http://www.open-ils.org</a></p> <p><strong><a href="#Evergreen">Evergreen</a></strong> has an active community and its Web home is at: <a href="http://www.open-ils.org">http://www.open-ils.org</a></p>
 </td> </td>
Line 81: Line 83:
 <tr> <tr>
 <th align="left">DIY</th> <th align="left">DIY</th>
-<td align="left"><a name="DIY"></a>Do It Yourself. One of open source advantages is, of course, that it is free and readily available for download by anyone. A result has been that both <strong><a href="#Evergreen">Evergreen</a></strong> has been adopted by libraries without paying for the software or for support but by staff at libraries learning the systems and installing it.</p> +<td align="left"><a name="DIY"></a>Do It Yourself. One of open source advantages is, of course, that it is free and readily available for download by anyone. A result has been that both <strong><a href="#Evergreen">Evergreen</a></strong> has been adopted by libraries without paying for the software or for support but by staff at libraries learning the systems and installing it. 
-It does happen but there is considerable technical knowledge required to carry it off and some of the DIY implementations have used paid support options a la carte&mdash;picking and choosing what support they need. The technical knowledge is held by people and those people who install these systems are generally highly paid so DIY can be a &#8220;pay me now, pay me later proposition.&#8221; However, work is going on in both communities to improve documentation and make the DIY process easier.</p> + 
-Evergreen has a complex infrastructure that sets a high bar for the required knowledge to install and support it but it , also has DIY implementations and is in the process of being adopted by several very large consortia which have capable IT staffs who are doing DIY implementations.</p>+<p>It does happen but there is considerable technical knowledge required to carry it off and some of the DIY implementations have used paid support options a la carte&mdash;picking and choosing what support they need. The technical knowledge is held by people and those people who install these systems are generally highly paid so DIY can be a &#8220;pay me now, pay me later proposition.&#8221; However, work is going on in both communities to improve documentation and make the DIY process easier.</p> 
 + 
 +<p>Evergreen has a complex infrastructure that sets a high bar for the required knowledge to install and support it but it , also has DIY implementations and is in the process of being adopted by several very large consortia which have capable IT staffs who are doing DIY implementations.</p>
 </td> </td>
 </tr> </tr>
Line 89: Line 93:
 <tr> <tr>
 <th align="left">ejabberd</th> <th align="left">ejabberd</th>
-<td align="left"><a name="ejabberd"></a>&#8220;<a href="http://www.process-one.net/en/ejabberd/">ejabberd</a> is a high performance instant messaging server. It enables users to communicate in real time and allows status and presence information to be securely and rapidly transferred between servers.&#8221;</a> ejabbered is free source software distributed under the <strong><a href="#GNU">GNU</a></strong> <strong><a href="#GPL">GPL</a></strong>. It is an application server for the <a href="http://xmpp.org/">eXtensible Messaging and Presence Protocol (XMPP)</a>. ejabbered is used to exchange data in Evergreen.</p> +<td align="left"><a name="ejabberd"></a>&#8220;<a href="http://www.process-one.net/en/ejabberd/">ejabberd</a> is a high performance instant messaging server. It enables users to communicate in real time and allows status and presence information to be securely and rapidly transferred between servers.&#8221;  ejabbered is free source software distributed under the <strong><a href="#GNU">GNU</a></strong> <strong><a href="#GPL">GPL</a></strong>. It is an application server for the <a href="http://xmpp.org/">eXtensible Messaging and Presence Protocol (XMPP)</a>. ejabbered is used to exchange data in Evergreen. 
-The ejabbered Web page is <a href="http://www.process-one.net/en/ejabberd/">http://www.process-one.net/en/ejabberd/</a> and the Wikipedia entry is found at: <a href="http://en.wikipedia.org/wiki/Ejabberd">http://en.wikipedia.org/wiki/Ejabberd</a>.</p>+ 
 +<p>The ejabbered Web page is <a href="http://www.process-one.net/en/ejabberd/">http://www.process-one.net/en/ejabberd/</a> and the Wikipedia entry is found at: <a href="http://en.wikipedia.org/wiki/Ejabberd">http://en.wikipedia.org/wiki/Ejabberd</a>.</p>
 </td> </td>
 </tr> </tr>
Line 102: Line 107:
 <tr> <tr>
 <th align="left">Evergreen</th> <th align="left">Evergreen</th>
-<td align="left"><a name="Evergreen"></a>The first <strong><a href="#ILS">ILS</a></strong> designed to handle the processing of geographically dispersed, resource-sharing library networks. It is the first <strong><a href="#CLS">Consortial Library System</a></strong>. Evergreen is the <strong><a href="#open_source">open source</a></strong> software that runs a growing number of libraries and consortia. The Wikipedia entry gives more information: <a href="http://en.wikipedia.org/wiki/Evergreen_%28software%29">http://en.wikipedia.org/wiki/Evergreen_(software)</a>. It first went live in 2006 in the Georgia <strong><a href="#PINES">PINES</a></strong> consortium.</p> +<td align="left"><a name="Evergreen"></a>The first <strong><a href="#ILS">ILS</a></strong> designed to handle the processing of geographically dispersed, resource-sharing library networks. It is the first <strong><a href="#CLS">Consortial Library System</a></strong>. Evergreen is the <strong><a href="#open_source">open source</a></strong> software that runs a growing number of libraries and consortia. The Wikipedia entry gives more information: <a href="http://en.wikipedia.org/wiki/Evergreen_%28software%29">http://en.wikipedia.org/wiki/Evergreen_(software)</a>. It first went live in 2006 in the Georgia <strong><a href="#PINES">PINES</a></strong> consortium. 
-Evergreen is licensed under the <strong><a href="#GNU">GNU</a></strong>General Public License (<strong><a href="#GPL">GPL</a></strong>).</p> + 
-<a name="EGCommunity"></a><br />+<p>Evergreen is licensed under the <strong><a href="#GNU">GNU</a></strong>General Public License (<strong><a href="#GPL">GPL</a></strong>).</p> 
 +</td> 
 +</tr> 
 + 
 +<tr> 
 +<th align="left">Evergreen Community</th> 
 +<td align="left"><a name="EGCommunity"></a><br />
 <strong>Community Resources</strong><br /> <strong>Community Resources</strong><br />
-The Evergreen community Website is at: <a href="http://www.evergreen-ils.org/">http://www.evergreen-ils.org/</a>.</p> +<p>The Evergreen community Website is at: <a href="http://www.evergreen-ils.org/">http://www.evergreen-ils.org/</a>.</p> 
-The community communicates via mailing lists as listed on this page:<br />+ 
 +<p>The community communicates via mailing lists as listed on this page:<br />
 <a href="http://evergreen-ils.org/listserv.php">http://evergreen-ils.org/listserv.php</a></p> <a href="http://evergreen-ils.org/listserv.php">http://evergreen-ils.org/listserv.php</a></p>
-and via Internet Relay Chat (IRC) channels. More information can be found here:<br />+ 
 +<p>and via Internet Relay Chat (IRC) channels. More information can be found here:<br />
 <a href="http://evergreen-ils.org/irc.php">http://evergreen-ils.org/irc.php</a></p> <a href="http://evergreen-ils.org/irc.php">http://evergreen-ils.org/irc.php</a></p>
-Evergreen blog aggregator is at Planet Evergreen: <a href="http://planet.evergreen-ils.org/">http://planet.evergreen-ils.org/</a></p> + 
-<strong>Sources of information on Evergreen history and background:</strong><br />+<p>Evergreen blog aggregator is at Planet Evergreen: <a href="http://planet.evergreen-ils.org/">http://planet.evergreen-ils.org/</a></p> 
 + 
 +<p><strong>Sources of information on Evergreen history and background:</strong><br />
 Georgia Public Library Service, &#8220;White Paper: PINES/Evergreen/Equinox,&#8221; <a href="http://pines.georgialibraries.org/files/WhitePaper-PINES-Evergreen-Equinox-8-09.pdf">http://pines.georgialibraries.org/files/WhitePaper-PINES-Evergreen-Equinox-8-09.pdf</a><br /> Georgia Public Library Service, &#8220;White Paper: PINES/Evergreen/Equinox,&#8221; <a href="http://pines.georgialibraries.org/files/WhitePaper-PINES-Evergreen-Equinox-8-09.pdf">http://pines.georgialibraries.org/files/WhitePaper-PINES-Evergreen-Equinox-8-09.pdf</a><br />
 <br /> <br />
Line 124: Line 139:
 <br /> <br />
 Weber, Jonathan, &#8220;Evergreen: Your Homegrown ILS,&#8220; <cite>Library Journal</cite>, December 15, 2006. <a href="http://www.libraryjournal.com/article/CA6396354.html">http://www.libraryjournal.com/article/CA6396354.html</a></p> Weber, Jonathan, &#8220;Evergreen: Your Homegrown ILS,&#8220; <cite>Library Journal</cite>, December 15, 2006. <a href="http://www.libraryjournal.com/article/CA6396354.html">http://www.libraryjournal.com/article/CA6396354.html</a></p>
-As well as numerous blog posts. Planet Evergreen: <a href="http://planet.evergreen-ils.org/">http://planet.evergreen-ils.org/</a> is probably the best source for these posts.</p>+ 
 +<p>As well as numerous blog posts. Planet Evergreen: <a href="http://planet.evergreen-ils.org/">http://planet.evergreen-ils.org/</a> is probably the best source for these posts.</p>
 </td> </td>
 </tr> </tr>
Line 130: Line 146:
 <tr> <tr>
 <th align="left">Evergreen Superconsortium</th> <th align="left">Evergreen Superconsortium</th>
-<td align="left"><a name="Superconsortium"></a>In a June, 2010 blog post, Bob Molyneux and Mike Rylander discussed something each independently noticed and, curiously, each had invented the same new word to describe: the &#8220;Superconsortium.&#8221; Briefly, they noted that consortia in the Evergreen community were banding together to do common development on Evergreen. Since then, this method of development has grown and has given another economical means to improve Evergreen.</p> +<td align="left"><a name="Superconsortium"></a>In a June, 2010 blog post, Bob Molyneux and Mike Rylander discussed something each independently noticed and, curiously, each had invented the same new word to describe: the &#8220;Superconsortium.&#8221; Briefly, they noted that consortia in the Evergreen community were banding together to do common development on Evergreen. Since then, this method of development has grown and has given another economical means to improve Evergreen. 
-The original post is here: <a href="http://evergreen-ils.org/blog/?p=339">http://evergreen-ils.org/blog/?p=339</a>.</p>+ 
 +<p>The original post is here: <a href="http://evergreen-ils.org/blog/?p=339">http://evergreen-ils.org/blog/?p=339</a>.</p>
 </td> </td>
 </tr> </tr>
Line 139: Line 156:
 <td align="left"><a name="EGsupport"></a><br /> <td align="left"><a name="EGsupport"></a><br />
 <strong><a href="#Evergreen">Evergreen</a></strong>, being open source, does not have one support company which handles all support so users are not subject to <strong><a href="#vendor_lockin">vendor lockin</a></strong>. A list of firms supporting Evergreen is kept on the Evergreen wiki:<br /> <strong><a href="#Evergreen">Evergreen</a></strong>, being open source, does not have one support company which handles all support so users are not subject to <strong><a href="#vendor_lockin">vendor lockin</a></strong>. A list of firms supporting Evergreen is kept on the Evergreen wiki:<br />
-<a href="http://www.evergreen-ils.org/dokuwiki/doku.php?id=faq:evergreen_companies">http://www.evergreen-ils.org/dokuwiki/doku.php?id=faq:evergreen_companies</a></p> +<a href="http://www.evergreen-ils.org/dokuwiki/doku.php?id=faq:evergreen_companies">http://www.evergreen-ils.org/dokuwiki/doku.php?id=faq:evergreen_companies</a> 
-Free support is also available via the <a href="#EGCommunity">community resources</a> listed with the entry on Evergreen.</p>+<p>Free support is also available via the <a href="#EGCommunity">community resources</a> listed with the entry on Evergreen.</p>
 </td> </td>
 </tr> </tr>
Line 146: Line 163:
 <tr> <tr>
 <th align="left">Fork</th> <th align="left">Fork</th>
-<td align="left"><a name="fork"></a>In this context, a software development fork results when developers take a copy of the project software and begin a separate development path. Software forks are largely an aspect of software developed using open source principles and, in effect, it is what Wikipedia refers to as a <a href="http://en.wikipedia.org/wiki/Fork_(software_development)">&#8220;schism.&#8221;</a> Usually a group of the developers decides to take the open code and create something new based on it. Forks can be friendly or unfriendly and can be seen as a <a href="http://meatballwiki.org/wiki/RightToFork">source of strength</a> or weakness in open source development. Schisms are seen in other aspects  of human activity, such as religion.</p> +<td align="left"><a name="fork"></a>In this context, a software development fork results when developers take a copy of the project software and begin a separate development path. Software forks are largely an aspect of software developed using open source principles and, in effect, it is what Wikipedia refers to as a <a href="http://en.wikipedia.org/wiki/Fork_(software_development)">&#8220;schism.&#8221;</a> Usually a group of the developers decides to take the open code and create something new based on it. Forks can be friendly or unfriendly and can be seen as a <a href="http://meatballwiki.org/wiki/RightToFork">source of strength</a> or weakness in open source development. Schisms are seen in other aspects  of human activity, such as religion. 
-<a href="http://www.catb.org/jargon/html/F/fork.html">Jargon File</a> argues that forks are rare and, hence, the &#8220;individual instances look large in hacker folklore.&#8221;</p>+ 
 +<p><a href="http://www.catb.org/jargon/html/F/fork.html">Jargon File</a> argues that forks are rare and, hence, the &#8220;individual instances look large in hacker folklore.&#8221;</p>
 </td> </td>
 </tr> </tr>
Line 153: Line 171:
 <tr> <tr>
 <th align="left">FOSS or FLOSS</th> <th align="left">FOSS or FLOSS</th>
-<td align="left"><a name="FLOSS"></a><strong>F</strong>ree (<strong>L</strong>ibre) <strong><a href="#open_source"><strong>O</strong>pen <strong>S</strong>ource</a></strong> <strong>S</strong>oftware. Also called <a name="#OSS">&#8220;OSS</a>&#8221;.+<td align="left"><a name="FLOSS"></a><strong>F</strong>ree (<strong>L</strong>ibre) <strong><a href="#open_source"><strong>O</strong>pen <strong>S</strong>ource</a></strong> <strong>S</strong>oftware. Also called <strong><a href="#OSS">&#8220;OSS&#8221;</a></strong>.
 </td> </td>
 </tr> </tr>
Line 159: Line 177:
 <tr> <tr>
 <th align="left">Free software</th> <th align="left">Free software</th>
-<td align="left"><a name="Free"></a>Free software is not to be confused with <strong><a href="#open_source">open source</a></strong> software although the two often have similar objectives, they do not always.</p> +<td align="left"><a name="Free"></a>Free software is not to be confused with <strong><a href="#open_source">open source</a></strong> software although the two often have similar objectives, they do not always. 
-See <cite>the Free Software Definition</cite> at <a href="http://www.gnu.org/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</a> for a discussion of the philosophy behind free software.</p> + 
-For a discussion of the differences in philosophy between Free software and <strong><a href="#open_source">open source</a></strong> software, see <cite>Why Open Source misses the point of Free Software</cite> at <a href="http://www.gnu.org/philosophy/open-source-misses-the-point.html">http://www.gnu.org/philosophy/open-source-misses-the-point.html</a>. The Wikipedia entry for the Free software movement is at: <a href="http://en.wikipedia.org/wiki/Free_software_movement">http://en.wikipedia.org/wiki/Free_software_movement</a>.</p>+<p>See <cite>the Free Software Definition</cite> at <a href="http://www.gnu.org/philosophy/free-sw.html">http://www.gnu.org/philosophy/free-sw.html</a> for a discussion of the philosophy behind free software.</p> 
 + 
 +<p>For a discussion of the differences in philosophy between Free software and <strong><a href="#open_source">open source</a></strong> software, see <cite>Why Open Source misses the point of Free Software</cite> at <a href="http://www.gnu.org/philosophy/open-source-misses-the-point.html">http://www.gnu.org/philosophy/open-source-misses-the-point.html</a>. The Wikipedia entry for the Free software movement is at: <a href="http://en.wikipedia.org/wiki/Free_software_movement">http://en.wikipedia.org/wiki/Free_software_movement</a>.</p>
 </td> </td>
 </tr> </tr>
Line 167: Line 187:
 <tr> <tr>
 <th align="left">FUD</th> <th align="left">FUD</th>
-<td align="left"><a name="FUD"></a>Fear, Uncertainty, Doubt. Do you want to trust your library&#8217;s functions to open source software written by a bunch of tattooed, dope-smoking hippies with orange hair?</p> +<td align="left"><a name="FUD"></a>Fear, Uncertainty, Doubt. Do you want to trust your library&#8217;s functions to open source software written by a bunch of tattooed, dope-smoking hippies with orange hair? 
-FUD, as the example above might demonstrate, has been a useful marketing tool for sellers of proprietary software but with the growth of the <strong><a href="#Evergreen">Evergreen</a></strong> and other open source communities in the library world, it has a waning influence. By instilling FUD in prospective users about the viability, robustness, and support of open source competitors, proprietary vendors have attempted to make open-source projects with hundreds of developers and excellent support seem like a casual basement project for a few hobbyist programmers.</p>+ 
 +<p>FUD, as the example above might demonstrate, has been a useful marketing tool for sellers of proprietary software but with the growth of the <strong><a href="#Evergreen">Evergreen</a></strong> and other open source communities in the library world, it has a waning influence. By instilling FUD in prospective users about the viability, robustness, and support of open source competitors, proprietary vendors have attempted to make open-source projects with hundreds of developers and excellent support seem like a casual basement project for a few hobbyist programmers.</p>
 </td> </td>
 </tr> </tr>
Line 179: Line 200:
  
 <tr> <tr>
-<th align="left">Git</a></th>+<th align="left">Git</th>
 <td align="left"><a name="Git"></a>A distributed software revision control system now used by Evergreen. It was developed by Linus Torvalds for Linux kernel development and is free software distributed under the terms of the <a href="#GPL">GNU GPL.</a>. For more information see the <a href="http://en.wikipedia.org/wiki/Git_%28software%29">Wikpedia</a> entry. <td align="left"><a name="Git"></a>A distributed software revision control system now used by Evergreen. It was developed by Linus Torvalds for Linux kernel development and is free software distributed under the terms of the <a href="#GPL">GNU GPL.</a>. For more information see the <a href="http://en.wikipedia.org/wiki/Git_%28software%29">Wikpedia</a> entry.
 </td> </td>
Line 223: Line 244:
 <th align="left">Linux</th> <th align="left">Linux</th>
 <td><a name="Linux"></a>An <strong><a href="#open_source">open source</a></strong> operating system used by <strong><a href="#Evergreen">Evergreen</a></strong>. <td><a name="Linux"></a>An <strong><a href="#open_source">open source</a></strong> operating system used by <strong><a href="#Evergreen">Evergreen</a></strong>.
-The Linux Foundation (<a href="http://www.linuxfoundation.org/">http://www.linuxfoundation.org/</a>) maintains Linux.com (<a href="http://www.linux.com/">http://www.linux.com/</a>.) The Linux Wikipedia entry is at: <a href="http://en.wikipedia.org/wiki/Linux">http://en.wikipedia.org/wiki/Linux</a> and that of the Linux Foundation is: <a href="http://en.wikipedia.org/wiki/Linux_Foundation">http://en.wikipedia.org/wiki/Linux_Foundation</a>.</p>+ 
 +<p>The Linux Foundation (<a href="http://www.linuxfoundation.org/">http://www.linuxfoundation.org/</a>) maintains Linux.com (<a href="http://www.linux.com/">http://www.linux.com/</a>.) The Linux Wikipedia entry is at: <a href="http://en.wikipedia.org/wiki/Linux">http://en.wikipedia.org/wiki/Linux</a> and that of the Linux Foundation is: <a href="http://en.wikipedia.org/wiki/Linux_Foundation">http://en.wikipedia.org/wiki/Linux_Foundation</a>.</p>
 </td> </td>
 </tr> </tr>
Line 229: Line 251:
 <tr> <tr>
 <th align="left">Load Balancing</th> <th align="left">Load Balancing</th>
-<td><a name="Loadbalancing"></a>An integral part of a robust server setup and one used in many Evergreen installations where the use of an array of redundant commodity servers runs best if the workload on the servers is distributed.</p>+<td><a name="Loadbalancing"></a>An integral part of a robust server setup and one used in many Evergreen installations where the use of an array of redundant commodity servers runs best if the workload on the servers is distributed. 
 <blockquote>&#8220;In networking, load balancing is a technique to distribute  workload evenly across two or more computers, network links, CPUs, hard drives, or other resources, in order to get optimal resource utilization, maximize throughput, minimize response time, and avoid overload. Using multiple components with load balancing&mdash;instead of a single component&mdash;may increase reliability through redundancy. The load balancing service is usually provided by a dedicated program or hardware device (such as a multilayer switch or a DNS server).&#8221;<br /> <blockquote>&#8220;In networking, load balancing is a technique to distribute  workload evenly across two or more computers, network links, CPUs, hard drives, or other resources, in order to get optimal resource utilization, maximize throughput, minimize response time, and avoid overload. Using multiple components with load balancing&mdash;instead of a single component&mdash;may increase reliability through redundancy. The load balancing service is usually provided by a dedicated program or hardware device (such as a multilayer switch or a DNS server).&#8221;<br />
-<a href="http://en.wikipedia.org/wiki/Load_balancing_(computing)">http://en.wikipedia.org/wiki/Load_balancing_(computing)</a></p></blockquote>+<a href="http://en.wikipedia.org/wiki/Load_balancing_(computing)">http://en.wikipedia.org/wiki/Load_balancing_(computing)</a></blockquote>
 </td> </td>
 </tr> </tr>
Line 237: Line 260:
 <tr> <tr>
 <th align="left">Memcached</th> <th align="left">Memcached</th>
-<td><a name="memchached"></a>&#8220;Free &amp; open source, high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding  up dynamic web applications by alleviating database load.&#8221; from: <a href="http://memcached.org/">http://memcached.org/</a>.</p> +<td><a name="memchached"></a>&#8220;Free &amp; open source, high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding  up dynamic web applications by alleviating database load.&#8221; from: <a href="http://memcached.org/">http://memcached.org/</a>. 
-A factor which can greatly speed up Evergreen searches is by loading the entire database in memory so searches can be done much faster than they could be if the database had to be searched on the hard drives. Memcached is the means by which this mirroring of the database in memory is done.</p>+ 
 +<p>A factor which can greatly speed up Evergreen searches is by loading the entire database in memory so searches can be done much faster than they could be if the database had to be searched on the hard drives. Memcached is the means by which this mirroring of the database in memory is done.</p>
 </td> </td>
 </tr> </tr>
Line 256: Line 280:
 <tr> <tr>
 <th align="left">open source</th> <th align="left">open source</th>
-<td align="left"><a name="open_source"></a>Open source is a number of things. It is a class of licenses, a culture, a community, and a way of producing and sharing software. It is not to be confused with <strong><a href="#Free">free software</a></strong>, although the two movements share many objectives.</p> +<td align="left"><a name="open_source"></a>Open source is a number of things. It is a class of licenses, a culture, a community, and a way of producing and sharing software. It is not to be confused with <strong><a href="#Free">free software</a></strong>, although the two movements share many objectives. 
-In these senses, it is normally distinguished from <strong><a href="#proprietary">proprietary</a></strong> licenses or software. Software produced by this method is released under an open source license like the <strong><a href="#GPL">GPL</a></strong> and the <strong><a href="#source_code">source code</a></strong> is freely available. There are a number of open source licenses. Generally, these licenses permit users to adapt, make changes, and improve software. The <strong><a href="#GPL">GPL</a></strong>, used by <strong><a href="#Evergreen">Evergreen</a></strong>, is a bit stricter than some other open source licenses and, among other things, also requires the adapted software be released through a <strong><a href="#GPL">GPL</a></strong> license.</p> + 
-The Website of the Open Source Initiative is at <a href="http://opensource.org/">http://opensource.org/</a>. The Wikipedia entry: <a href="http://en.wikipedia.org/wiki/Open-source_software">http://en.wikipedia.org/wiki/Open-source_software</a></p> +<p>In these senses, it is normally distinguished from <strong><a href="#proprietary">proprietary</a></strong> licenses or software. Software produced by this method is released under an open source license like the <strong><a href="#GPL">GPL</a></strong> and the <strong><a href="#source_code">source code</a></strong> is freely available. There are a number of open source licenses. Generally, these licenses permit users to adapt, make changes, and improve software. The <strong><a href="#GPL">GPL</a></strong>, used by <strong><a href="#Evergreen">Evergreen</a></strong>, is a bit stricter than some other open source licenses and, among other things, also requires the adapted software be released through a <strong><a href="#GPL">GPL</a></strong> license.</p> 
-Open source is relatively new to the library world. One normally speaks of the alternative <strong><a href="#proprietary">proprietary</a></strong> vendors as &#8220;legacy&#8221; or &#8220;traditional&#8221; vendors.</p> + 
-<strong>Additional sources of information on open source software in libraries</strong></p> +<p>The Website of the Open Source Initiative is at <a href="http://opensource.org/">http://opensource.org/</a>. The Wikipedia entry: <a href="http://en.wikipedia.org/wiki/Open-source_software">http://en.wikipedia.org/wiki/Open-source_software</a></p> 
-Engard, Nicole, <cite>Practical Open Source Software for Libraries</cite>, (Chandos Publishing, 2010.)</p>+ 
 +<p>Open source is relatively new to the library world. One normally speaks of the alternative <strong><a href="#proprietary">proprietary</a></strong> vendors as &#8220;legacy&#8221; or &#8220;traditional&#8221; vendors.</p> 
 + 
 +<p><strong>Additional sources of information on open source software in libraries</strong></p> 
 +<p>Engard, Nicole, <cite>Practical Open Source Software for Libraries</cite>, (Chandos Publishing, 2010.)</p>
 </td> </td>
 </tr> </tr>
Line 279: Line 307:
  
 <tr> <tr>
-<th align="left"><a name="open_source_disadvantages"></a>open source software disadvantages:</th> +<th align="left">open source software disadvantages:</th> 
-<td align="left">+<td align="left"><a name="open_source_disadvantages"></a>
 <ul> <ul>
 <li> Who supports it if you can&#8217;t?</li> <li> Who supports it if you can&#8217;t?</li>
Line 289: Line 317:
  
 <tr> <tr>
-<th align="left"><a name="OSS">OSS</th> +<th align="left">OSS</th> 
-<td align="left"><strong><a href="#open_source"></a>open source</strong> software</td>+<td align="left"><a name="OSS"></a><strong><a href="#open_source"></a>open source</strong> software</td>
 </tr> </tr>
  
 <tr> <tr>
 <th align="left">OSS4lib</th> <th align="left">OSS4lib</th>
-<td align="left">Website that maintains a listing of free software and systems designed for libraries but is broader than the <strong><a href="#ILS">ILS/LMS</a></strong> focus of this glossary. It was started in 1999. Its Website is at: <a href="http://www.oss4lib.org/">http://www.oss4lib.org/</a></td>+<td align="left"><a name="OSS4lib"></a> Website that maintains a listing of free software and systems designed for libraries but is broader than the <strong><a href="#ILS">ILS/LMS</a></strong> focus of this glossary. It was started in 1999. Its Website is at: <a href="http://www.oss4lib.org/">http://www.oss4lib.org/</a></td>
 </tr> </tr>
  
 <tr> <tr>
 <th align="left">Perl</th> <th align="left">Perl</th>
-<td align="left"><a name="Perl"></a>&#8220;Perl is a highly capable, feature-rich programming language with over 22 years of development.&#8221; (<a href="http://www.perl.org">http://www.perl.org/</a>.) Perl is used extensively in the Evergreen community.</p> +<td align="left"><a name="Perl"></a>&#8220;Perl is a highly capable, feature-rich programming language with over 22 years of development.&#8221; (<a href="http://www.perl.org">http://www.perl.org/</a>.) Perl is used extensively in the Evergreen community. 
-From Wikipedia&#8217;s entry:</p> + 
-<blockquote>&#8220;Perl is a general-purpose programming language originally developed for text manipulation, but as of 2010 used for a wide range of tasks including system administration,  web development, network programming, games, bioinformatics, and GUI development.</p>+<p>From Wikipedia&#8217;s entry:</p> 
 +<blockquote>&#8220;Perl is a general-purpose programming language originally developed for text manipulation, but as of 2010 used for a wide range of tasks including system administration,  web development, network programming, games, bioinformatics, and GUI development.<br />
 &#8220;The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal).&#8221;<br /> &#8220;The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal).&#8221;<br />
-<br />(<a href="http://en.wikipedia.org/wiki/Perl">http://en.wikipedia.org/wiki/Perl</a>)</p> +<br />(<a href="http://en.wikipedia.org/wiki/Perl">http://en.wikipedia.org/wiki/Perl</a>)</blockquote>
-</blockquote>+
 </td> </td>
 </tr> </tr>
Line 311: Line 339:
 <tr> <tr>
 <th align="left">PINES</th> <th align="left">PINES</th>
-<td align="left"><a name="PINES"></a>The Georgia statewide public library resource sharing network. It currently has 51 systems and 280 library outlets. It was the first system to use <strong><a href="#Evergreen">Evergreen</a></strong>. The <a href="http://gapines.org/opac/en-US/skin/default/xml/index.xml">PINES catalog</a> searches the largest installation of Evergreen with a 10 million item collection. In 2010, PINES circulated 19 million items.</p> +<td align="left"><a name="PINES"></a>The Georgia statewide public library resource sharing network. It currently has 51 systems and 280 library outlets. It was the first system to use <strong><a href="#Evergreen">Evergreen</a></strong>. The <a href="http://gapines.org/opac/en-US/skin/default/xml/index.xml">PINES catalog</a> searches the largest installation of Evergreen with a 10 million item collection. In 2010, PINES circulated 19 million items. 
-The PINES web home is at <a href="http://pines.georgialibraries.org/">http://pines.georgialibraries.org/</a>.</p> + 
-<strong>Sources of information on PINES’s history and background:</strong></p> +<p>The PINES web home is at <a href="http://pines.georgialibraries.org/">http://pines.georgialibraries.org/</a>.</p> 
-A short history <cite><a href="http://pines.georgialibraries.org/10-years-pines">10 Years of PINES</a></cite> provides a retrospective on PINES.<br />+ 
 +<p><strong>Sources of information on PINES’s history and background:</strong></p> 
 + 
 +<p>A short history <cite><a href="http://pines.georgialibraries.org/10-years-pines">10 Years of PINES</a></cite> provides a retrospective on PINES.<br />
 Hardy, Elaine, &#8220;The Georgia Public Library Service and Georgia’s Public Libraries: A timeline of important events in Georgia public library history.&#8221; <cite>Georgia Library Quarterly</cite>, Summer 2008, pp. 12-18. Includes a full, rich bibliography on PINES and the events leading up to the formation of PINES.</p> Hardy, Elaine, &#8220;The Georgia Public Library Service and Georgia’s Public Libraries: A timeline of important events in Georgia public library history.&#8221; <cite>Georgia Library Quarterly</cite>, Summer 2008, pp. 12-18. Includes a full, rich bibliography on PINES and the events leading up to the formation of PINES.</p>
 </td> </td>
Line 321: Line 352:
 <tr> <tr>
 <th align="left">PostgreSQL</th> <th align="left">PostgreSQL</th>
-<td align="left"><a name="Postgres">PostgreSQL</a>, commonly shortened to &#8220;Postgres,&#8221; is a powerful, <strong><a href="#open_source">open source</a></strong> relational database system that is used in <strong>Evergreen</strong>. It has more than 15 years of active development and a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness. To learn more about PostgreSQL visit <a href="http://www.postgresql.org/">http://www.postgresql.org/</a>.</p> +<td align="left"><a name="Postgres">PostgreSQL</a>, commonly shortened to &#8220;Postgres,&#8221; is a powerful, <strong><a href="#open_source">open source</a></strong> relational database system that is used in <strong>Evergreen</strong>. It has more than 15 years of active development and a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness. To learn more about PostgreSQL visit <a href="http://www.postgresql.org/">http://www.postgresql.org/</a>. 
-Wikipedia&#8217;s entry: <a href="http://en.wikipedia.org/wiki/PostgreSQL">http://en.wikipedia.org/wiki/PostgreSQL</a></p>+ 
 +<p>Wikipedia&#8217;s entry: <a href="http://en.wikipedia.org/wiki/PostgreSQL">http://en.wikipedia.org/wiki/PostgreSQL</a></p>
 </td> </td>
 </tr> </tr>
Line 349: Line 381:
 <td align="left"> <td align="left">
 <ul> <ul>
-<li> Supported by the company you buy it from. This fact can be bad if it is the only option because of potential <strong><a href="#vendor_lockin">vendor lockin</a></strong> or it can be good if the company is strong and committed to support and development of its software.+<li> Supported by the company you buy it from. This fact can be bad if it is the only option because of potential <strong><a href="#vendor_lockin">vendor lockin</a></strong> or it can be good if the company is strong and committed to support and development of its software.</li>
 <li> Slow development cycle which may have difficulty balancing the requirements of various users. For instance, what happens if your vendor will not develop something you require?</li> <li> Slow development cycle which may have difficulty balancing the requirements of various users. For instance, what happens if your vendor will not develop something you require?</li>
 <li> Some vendors have been bought by firms that don&#8217;t know the library field nor have any particular affinity to it. It often appears that the decision to purchase these library vendors was financial. In these cases at least, support and development have arguably suffered.</li> <li> Some vendors have been bought by firms that don&#8217;t know the library field nor have any particular affinity to it. It often appears that the decision to purchase these library vendors was financial. In these cases at least, support and development have arguably suffered.</li>
Line 365: Line 397:
 <tr> <tr>
 <th align="left">Repository</th> <th align="left">Repository</th>
-<td align="left"><a name="repository">An online archive for open source software where current and past versions of the software can be found. Popular repositories include <a href="http://sourceforge.net/">SourceForge</a> and <a href="http://freshmeat.net/">Freshmeat</a>.+<td align="left"><a name="repository"></a>An online archive for open source software where current and past versions of the software can be found. Popular repositories include <a href="http://sourceforge.net/">SourceForge</a> and <a href="http://freshmeat.net/">Freshmeat</a>.
 </td> </td>
 </tr> </tr>
Line 376: Line 408:
 <tr> <tr>
 <th align="left">source code</th> <th align="left">source code</th>
-<td align="left"><a name="source_code"></a>&#8220;..text written in a computer programming language.&#8221; </p> +<td align="left"><a name="source_code"></a>&#8220;..text written in a computer programming language.&#8221;  
-Source code is written in a human-readable language by software programmers or developers. Before it can be run on computers, it must be <strong><a href="#compiled">compiled</a></strong> into language that these computers can read. Wikipedia has more (<a href="http://en.wikipedia.org/wiki/Source_code">http://en.wikipedia.org/wiki/Source_code</a>) including related links.</p>+ 
 +<p>Source code is written in a human-readable language by software programmers or developers. Before it can be run on computers, it must be <strong><a href="#compiled">compiled</a></strong> into language that these computers can read. Wikipedia has more (<a href="http://en.wikipedia.org/wiki/Source_code">http://en.wikipedia.org/wiki/Source_code</a>) including related links.</p>
 </td> </td>
 </tr> </tr>
Line 402: Line 435:
 <th align="left">Vendor lockin</th> <th align="left">Vendor lockin</th>
 <td align="left"><a name="vendor_lockin"></a>If you buy from a <strong><a href="#proprietary">proprietary</a></strong> vendor, it is protected from competition for your business by<br /> <td align="left"><a name="vendor_lockin"></a>If you buy from a <strong><a href="#proprietary">proprietary</a></strong> vendor, it is protected from competition for your business by<br />
-<ol+<ul
-<li> your multi-year contract,  +<li> your multi-year contract,</li>  
-<li> from the challenges of data <strong><a href="#migration">migration</a></strong>, and  +<li> from the challenges of data <strong><a href="#migration">migration</a></strong>, and</li>  
-<li> the fact that it alone supports the software including development and updates. +<li> the fact that it alone supports the software including development and updates.</li>  
-</ol>+</ul>
 </td> </td>
-</tr>+</tr>                                                                
 </table> </table>
  
 <p align="left">Thanks to Anoop Atre, Galen Charlton, Jason Etheridge, Nicole Engard, Rogan Hamby, and Glen Holt for many helpful suggestions. They are not, of course, responsible for any errors.</p> <p align="left">Thanks to Anoop Atre, Galen Charlton, Jason Etheridge, Nicole Engard, Rogan Hamby, and Glen Holt for many helpful suggestions. They are not, of course, responsible for any errors.</p>
 </html> </html>
scratchpad.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.