Re: [Koha] cost of koha
Yesterday at 5:24am -0800 BWS Johnson wrote: I thank Paul POULAIN for providing detail about contribution by different developers.
So, some comparison of this sort (cost to benefit ratio, total cost of ownership etc), which may help potential user or decision maker to take infomed decision and not be misguided by marketing executive of proprietary software
That's not an easy question at all.
Agreed. But if respectable members on this list pool their information to have a such type of white paper, then that will boost usage and promotion of Koha. Is there something like "Koha advocacy"? -- H. S. Rai _____________________________________________________________________ http://www.grex.org/~hsrai | Alternate E-mail: hsraidce@iitr.ernet.in ___________________________|_________________________________________ : ####[ GNU/Linux One Stanza Tip (LOST) ]####################### Sub : Synchronising time with net time servers LOST #240 To synchronise the time on your system with Time Servers on the net (e.g. time.nuri.net, time.hmt.org), Do : #rdate -s some.time.server;/usr/sbin/setclock ####[mallet (at) efn.org]##################################### :
H S Rai, I think that time and resources expended on this topic is a waste. Even if the cost factors were not in Koha's favor, flexibility and customization dictate the usage of non proprietary software. Here in the United States, most in libraries and academia are so brainwashed (maybe intellectually lazy would be a better term) that even when I offer to set up open soft software for free and give them the server, they still prefer to take the lazy way out and pay exorbitant sums for inferior proprietary software. I have virtually given up such endeavors here in the US. They will have to suffer the consequences of such insane decisions when their economy inevitably contracts due to worker laziness and incompetence. I for example am working in the Central Asian region, where management is very receptive since they do not have any other choice (no funds available for proprietary software). Much like the farmer who has to build it himself, they will either have to bite the bullet and use Open Source Software, or never enter the information technology age. A Chinese proverb states "do not cast your pearls in front of swine" and we should not waste our time on such endeavors. Every resource spent on improving the software is a much better option since it will help people who are willing to use it, instead of wasting our precious time trying to convince people who should know better. Gerry wrote:
Yesterday at 5:24am -0800 BWS Johnson wrote:
I thank Paul POULAIN for providing detail about contribution by different developers.
So, some comparison of this sort (cost to benefit ratio, total cost of ownership etc), which may help potential user or decision maker to take infomed decision and not be misguided by marketing executive of proprietary software
That's not an easy question at all.
Agreed. But if respectable members on this list pool their information to have a such type of white paper, then that will boost usage and promotion of Koha.
Is there something like "Koha advocacy"?
Gerry Arthus wrote:
technology age. A Chinese proverb states "do not cast your pearls in front of swine" and we should not waste our time on such endeavors.
Hardly Chinese. "Give not that which is holy unto the dogs, neither cast ye your pearls before swine, lest they trample them under their feet, and turn again and rend you". MATTHEW 7:6. Thus spate Google :-) Mike
Hi all, Now that I have been playing with Koha for a month or so I'm now putting together a formal proposal for the society that I'm a member of to use Koha. We have a few thousand items that will be placed in the catalog and we would like to make the OPAC available on our web site. However some items would be of great value to book collectors. Publishing this info on the web would mean that someone with contacts could make a nice shopping list and clean us out one night. Just as there is a 'checkbox' for catalog items that are 'not reservable' how much code would be required to have a checkbox 'not for web publication'? Or a drop down box that one can use to limit the search availability to specific levels users. I would envisage having more than one user in the koha users table; say guest user, member, library user and then the usual admin user with increasing access in that order. Guests can't see items that are flagged as accessable to member and above. Does anyone else have this need or is it possible to do this already in Koha. (I see on this list there are probs with Apache::Registry ) Mike -- Michael Lake -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects.
participants (4)
-
Gerry Arthus -
H S Rai -
Michael Lake -
Michael Lake