Not sure if you all saw this: http://ils.foss4lib.org but it's comparing Koha 3.10 to Evergreen 2.4 - we should probably get it up to date since Koha is not 3 releases ahead and has many of the features it says it doesn't. Nicole
On Thu, Jul 3, 2014 at 1:08 AM, Nicole Engard <nengard@gmail.com> wrote:
Not sure if you all saw this: http://ils.foss4lib.org but it's comparing Koha 3.10 to Evergreen 2.4 - we should probably get it up to date since Koha is not 3 releases ahead and has many of the features it says it doesn't.
+1! Who can do it? -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
I'm actually pretty ambivalent about it. I don't see pitching Koha vs Evergreen is helpful. Either of them are always going to be better than any proprietary system. Simply because they are not proprietary. We'd be better off with a tool that shows how they are both better than Alma for example. (For one our developments are steered by users not an equity firm :)) That's my roundabout way of saying "I won't be updating it" Chris On 4 July 2014 6:16:00 am NZST, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
On Thu, Jul 3, 2014 at 1:08 AM, Nicole Engard <nengard@gmail.com> wrote:
Not sure if you all saw this: http://ils.foss4lib.org but it's comparing Koha 3.10 to Evergreen 2.4 - we should probably get it up to date since Koha is not 3 releases ahead and has many of the features it says it doesn't.
+1! Who can do it?
-- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi I agree with Chris that comparison perhaps it is not useful, however this is a nice way of listing koha features quickly, from the point of view of users it could be interesting check main differences and from koha community is also an interesting source of development ideas ;) Hugo 2014-07-03 21:22 GMT+02:00 Chris Cormack <chrisc@catalyst.net.nz>:
I'm actually pretty ambivalent about it. I don't see pitching Koha vs Evergreen is helpful. Either of them are always going to be better than any proprietary system. Simply because they are not proprietary.
We'd be better off with a tool that shows how they are both better than Alma for example. (For one our developments are steered by users not an equity firm :))
That's my roundabout way of saying "I won't be updating it"
Chris
On 4 July 2014 6:16:00 am NZST, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
On Thu, Jul 3, 2014 at 1:08 AM, Nicole Engard <nengard@gmail.com> wrote:
Not sure if you all saw this: http://ils.foss4lib.org but it's comparing Koha 3.10 to Evergreen 2.4 - we should probably get it up to date since Koha is not 3 releases ahead and has many of the features it says it doesn't.
+1! Who can do it?
-- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- *Hugo Agud - Orex Digital * *www.orex.es <http://www.orex.es>* Director Passatge de la Llançadera, 3 · 08338 Premià de Dalt - Tel: 93 539 40 70 hagud@orex.es · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema.
I'm with Hugo and Chris - in that it's not really a useful tool, but I worry that people will see it and say oh Koha (or Evergreen) can't do XYZ and so isn't as good as Proprietary System ABC. Just thought you should all know it's out there so you can educate people accordingly - I know I will. Nicole
Hi All, I'm sorry that the features listing is out-of-date but we will be bringing it up to speed very soon. As Nicole and Hugo mentioned, it is more about letting people know that the Koha and Evergreen product DO have all the features that people expect from the proprietary ILSs. I'd love to add Alma and Symphony, WMS, and Sierra, etc, to the list but sadly, that is way more of an undertaking than my company or Lyrasis can handle. So, by putting this product out there, we are at least taking some pressure off the service providers (e.g. ByWater, Equinox, Catalyst, PTFS, Libime???) who might not have the marketing departments that Innovative and SirsiDynix and OCLC have. It would be great to get a little help from the Koha community on this as it ultimately benefits everyone by enticing more people to move to Koha (and Evergreen). I understand your reluctance but I hope you'll see this resource as something desired to support Open Source, not hinder. If you'd like to contribute, let me know. In the meantime, we do expect to get it updated in the next couple of weeks or so. But feedback about features we're misrepresented or which need to be added are ALWAYS welcome! Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group (707) 763-6869 // Lori.Ayre@galecia.com Availability: http://doodle.com/loriayre <Lori.Ayre@galecia.com>Specializing in software solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Thu, Jul 3, 2014 at 1:39 PM, Nicole Engard <nengard@gmail.com> wrote:
I'm with Hugo and Chris - in that it's not really a useful tool, but I worry that people will see it and say oh Koha (or Evergreen) can't do XYZ and so isn't as good as Proprietary System ABC. Just thought you should all know it's out there so you can educate people accordingly - I know I will.
Nicole _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
I am unable to create patron categories. I am having a lot of problems getting Koka (version 3.14.08) up and running. I am running things on Linux (Fedora 7). I have complied, tested, and installed the latest and greatest versions of YAZ and Zebra. I am running MySQL 14. I have run zebrasrv but I do not see any ports (9999 or 9998) open when I run netstat -tulpn. I don’t have a2enmod nor a2ensite on my computer, but after symbolically linking the koha-httpd.conf to my Apache conf.d directory, and after editing the IP address from localhost to my machine’s “real” IP address, I am able to connect to both the public interface as well as the intranet with my Web browser. Once I connected to the intranet I was prompted for a few installation instructions. I accepted the vast majority of the defaults. It tried to load the sample data, and it returned an error, of sorts — "Using a password on the command line interface can be insecure.” This error comes from the mysql client. Despite this, there is data in my database because I can use mysqldump to… dump the contents of my koha database to a file. After reconnecting to the intranet I was told to create a patron, but patrons can not be created without both libraries and patron profiles. Creating a library was easy. Fill in form, and the library is created. Apparently reading and writing to the database works in this case. Creating a patron profile is problematic. I fill to the form trying to create a staff patron. I summit the form. The screen goes blank for a second or two, and returns saying "No categories have been defined. Create a new category.” I’m stuck in an endless loop. What am I missing? — Eric Lease Morgan
Creating a patron profile is problematic. I fill to the form trying to create a staff patron. I summit the form. The screen goes blank for a second or two, and returns saying "No categories have been defined. Create a new category.” I’m stuck in an endless loop.
I have a very similar problem when I try to create Z39.50 servers. Fill in Z39.50 form. Submit. Screen comes back and says “Ok”. Go to Z39.50 server page, but no servers are listed. Dump database. Grep database dump for LCDB (the Library of Congress database name). Not found. Sometimes writing to the database works, like with the creation of a library. But writing to the database for patron categories or Z39.50 servers does not. What am I missing? Maybe writing to the database is sometimes done through the Perl API, and maybe sometimes it is done through the MySQL client? When using the Perl API no error? When using the MySQL client get “warning”. By the way, I tried installing the latest and greatest version of Koha a couple of weeks ago — version 3.16 — and had the exact same problems. So I thought I’d go back one version, just in case I was on the “bleeding” edge. (Next will try to import some bibliographic data from the command line. Wish me luck?) — Eric “Beginning To Grasp At Straws” Morgan
I am unable to create patron categories….
And now I have a very similar problem with staging MARC records as well as Z39.50 servers as well as patron categories. They simply do not show up. I have a set of MARC records in (presumably) USMARC format. Using the Web-based interface I upload the records and Koha comes back telling me: Staging results: * 1465 records in file * 0 records not staged because of MARC error * 1465 records staged * Did not check for matches with existing records in catalog * 0 item records found and staged I then use the Manage Staged Records function and Koha says, "There are no records in this batch to import. Manage staged MARC records.” When I use the Staged MARC management function I see two sets of records (because I’ve done this twice) but clicking on them tells me: File name: pamphlets.marc Comments: pamphlets Type: Bibliographic records Staged: 2014-07-04 13:52:22 Status: Cleaned Matching rule applied: No matching rule in effect Action if matching record found: Add incoming record Action if no match found: Add incoming record Item processing: Always add items And then "There are no records in this batch to import. Manage staged MARC records.” Something just doesn’t seem “turned on”. Stuff goes in but does not come out. — Eric Lease Morgan
Eric,
I am having a lot of problems getting Koka (version 3.14.08) up and running. I am running things on Linux (Fedora 7). I have complied, tested, and installed the latest and greatest versions of YAZ and Zebra. I am running MySQL 14. I have run zebrasrv but I do not see any ports (9999 or 9998) open when I run netstat -tulpn. I don’t have a2enmod nor a2ensite on my computer, but after symbolically linking the koha-httpd.conf to my Apache conf.d directory, and after editing the IP address from localhost to my machine’s “real” IP address, I am able to connect to both the public interface as well as the intranet with my Web browser.
Brave. I wouldn't be willing to use Koha under a non-Debian-based Linux distribution. There be dragons. Perhaps you mean RHEL 7? Fedora 7 is pretty old. Also, I'm not sure what you mean by "MySQL 14," but you should really probably be using MySQL or MariaDB 5.1+ if that's not what you have. The default configuration for Zebra does not open any ports. Koha uses unix sockets for communicating with Zebra by default.
Creating a patron profile is problematic. I fill to the form trying to create a staff patron. I summit the form. The screen goes blank for a second or two, and returns saying "No categories have been defined. Create a new category.” I’m stuck in an endless loop.
What am I missing?
You need to create a patron *category* not a new staff patron. Under Administration->Patron categories (http://manual.koha-community.org/3.16/en/patscirc.html#patcats ). Regarding your other e-mail, I have no idea why adding a Z39.50 server wouldn't be working. It works fine for me. However, to address your thought that sometimes Koha is using the command line client and sometimes it's using Perl DBI to access the database, the only time Koha uses the command line client is for the initial installation. Other than that, pretty much everything is via DBI. Good luck! Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/
On Jul 4, 2014, at 11:56 AM, Jared Camins-Esakov <jcamins@cpbibliography.com> wrote:
I am having a lot of problems getting Koka (version 3.14.08) up and running...
Brave. I wouldn't be willing to use Koha under a non-Debian-based Linux distribution. There be dragons.
Perhaps you mean RHEL 7? Fedora 7 is pretty old. Also, I'm not sure what you mean by "MySQL 14," but you should really probably be using MySQL or MariaDB 5.1+ if that's not what you have. The default configuration for Zebra does not open any ports. Koha uses unix sockets for communicating with Zebra by default.
Yes, I am running RHEL 7, and yes it is older rather than younger. And yes, I am running MySQL version 5.6.15. And, yes, I see that Zebra runs under Unix sockets, not necessarily ports. My bad. — Eric Lease Morgan
Could you check About Koha > Perl modules and tell us what stuff is red or yellow (orange?)? On Fri, Jul 4, 2014 at 3:13 PM, Eric Lease Morgan < eric_morgan@infomotions.com> wrote:
On Jul 4, 2014, at 11:56 AM, Jared Camins-Esakov < jcamins@cpbibliography.com> wrote:
I am having a lot of problems getting Koka (version 3.14.08) up and running...
Brave. I wouldn't be willing to use Koha under a non-Debian-based Linux distribution. There be dragons.
Perhaps you mean RHEL 7? Fedora 7 is pretty old. Also, I'm not sure what you mean by "MySQL 14," but you should really probably be using MySQL or MariaDB 5.1+ if that's not what you have. The default configuration for Zebra does not open any ports. Koha uses unix sockets for communicating with Zebra by default.
Yes, I am running RHEL 7, and yes it is older rather than younger. And yes, I am running MySQL version 5.6.15. And, yes, I see that Zebra runs under Unix sockets, not necessarily ports. My bad.
— Eric Lease Morgan
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
On Jul 4, 2014, at 2:18 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
I am having a lot of problems getting Koka (version 3.14.08) up and running...
Could you check About Koha > Perl modules and tell us what stuff is red or yellow (orange?)?
Alas, none of the modules are red nor yellow nor orange. Everything is black, and I’ve created a screen dump of the Perl modules output. [1] [1] modules - http://infomotions.com/tmp/modules.png — Eric Morgan
I am having a lot of problems getting Koka (version 3.14.08) up and running…
Alas, nor am I able to successfully use bulkmarcimport.pl. I su to the user koha. I set two environment variables: * export KOHA_CONF=/etc/koha/koha-conf.xml * export PERL5LIB=/usr/local/koha/lib I then run bulkmarcimport: $ bulkmarcimport.pl -file /tmp/pamphlets.marc And for each record in pamphlets.marc I get the following error: .DBD::mysql::st execute failed: Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3222, <GEN15> line 1465. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET biblionumber = ?, volume = ?, number = ?, itemtype = ?, isbn = ?, issn = ?, publicationyear = ?, publishercode = ?, volumedate = ?, volumedesc = ?, collectiontitle = ?, collectionissn = ?, collectionvolume= ?, editionstatement= ?, editionresponsibility = ?, illus = ?, pages = ?, notes = ?, size = ?, place = ?, lccn = ?, marc = ?, url = ?, cn_source = ?, cn_class = ?, cn_item = ?, cn_suffix = ?, cn_sort = ?, totalissues = ?, ean = ?, agerestriction = ? Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3236, <GEN15> line 1465. I’m getting tired. — Eric Lease Morgan
Looks like you have an incomplete/broken DB schema. Have you already populated sensitive data? Otherwise i'd drop the database, create an empty one, and use the webinstaller to create the correct one. On Fri, Jul 4, 2014 at 3:46 PM, Eric Lease Morgan < eric_morgan@infomotions.com> wrote:
I am having a lot of problems getting Koka (version 3.14.08) up and running…
Alas, nor am I able to successfully use bulkmarcimport.pl.
I su to the user koha. I set two environment variables:
* export KOHA_CONF=/etc/koha/koha-conf.xml * export PERL5LIB=/usr/local/koha/lib
I then run bulkmarcimport:
$ bulkmarcimport.pl -file /tmp/pamphlets.marc
And for each record in pamphlets.marc I get the following error:
.DBD::mysql::st execute failed: Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3222, <GEN15> line 1465. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET biblionumber = ?, volume = ?, number = ?, itemtype = ?, isbn = ?, issn = ?, publicationyear = ?, publishercode = ?, volumedate = ?, volumedesc = ?, collectiontitle = ?, collectionissn = ?, collectionvolume= ?, editionstatement= ?, editionresponsibility = ?, illus = ?, pages = ?, notes = ?, size = ?, place = ?, lccn = ?, marc = ?, url = ?, cn_source = ?, cn_class = ?, cn_item = ?, cn_suffix = ?, cn_sort = ?, totalissues = ?, ean = ?, agerestriction = ? Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3236, <GEN15> line 1465.
I’m getting tired.
— Eric Lease Morgan
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
On Jul 4, 2014, at 2:53 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
$ bulkmarcimport.pl -file /tmp/pamphlets.marc
And for each record in pamphlets.marc I get the following error:
.DBD::mysql::st execute failed: Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3222, <GEN15> line 1465. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET
Looks like you have an incomplete/broken DB schema. Have you already populated sensitive data? Otherwise i'd drop the database, create an empty one, and use the webinstaller to create the correct one.
Thank you for the prompt replies. Done, but alas, to no avail. First I dropped my database and then recreated it: $ mysqladmin -uroot -p drop koha Enter password: Dropping the database is potentially a very bad thing to do. Any data stored in the database will be destroyed. Do you really want to drop the 'koha' database [y/N] y Database "koha" dropped $ mysqladmin -uroot -p create koha Enter password: I then logged into the intranet and it told me I needed to create a database. It went through a number of checks and found nothing wrong; all dependencies were found. It then tried to populate the database, and I got an error, just like before: The following error occurred while importing the database structure: Warning: Using a password on the command line interface can be insecure. Please contact your system administrator This error -- “Using a password...” — is the output sent by the mysql client when I include a value with the -p switch as in: mysql -ufoo -pbar abcd < efgh.sql When I re-connect to the Web interface it thinks I have a database in place, and it asks me questions like "Select your MARC flavor” and "Selecting Default Settings”. It then tries to do another import (with sample data?) and the says success, but again with a peppering of "Using a password on the command line interface can be insecure.” messages. See my screen dump. [1] Maybe I can initialize my koha database by hand? What file contains the database structure? What file(s) contains the sample data? Maybe my mysql client is getting in the way with its "Using a password on the command line interface can be insecure.” message. [1] screen dump - http://infomotions.com/tmp/install.png — Eric Lease Morgan
On Jul 4, 2014, at 3:16 PM, Eric Lease Morgan <eric_morgan@infomotions.com> wrote:
$ bulkmarcimport.pl -file /tmp/pamphlets.marc
And for each record in pamphlets.marc I get the following error:
.DBD::mysql::st execute failed: Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3222, <GEN15> line 1465. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET
Looks like you have an incomplete/broken DB schema. Have you already populated sensitive data? Otherwise i'd drop the database, create an empty one, and use the webinstaller to create the correct one.
Maybe I can initialize my koha database by hand?
I tried populating my database with many .sql files found in installer/data/mysql. Examples included but were not limited to: * mysql -uroot -p koha < kohastructure.sql * mysql -uroot -p koha < sysprefs.sql * mysql -uroot -p koha < en/mandatory/auth_values.sql * ... I then reconnected via the Web interface, and was prompted to do installation, again. (Bummer). It seemed to import things, again, but with the same errors as before, plus a few more about duplicate values. After this I was still not able to create patron profiles, etc. I then tried to import the sample z39.50 servers: $ mysql -uroot -p koha < sample_z3950_servers.sql And I got this error: ERROR 1364 (HY000) at line 1: Field 'description' doesn't have a default value I then hacked sample_z3950_servers.sql to add a description field and look like this: INSERT INTO z3950servers (description,host, port, db, userid, password, name, checked, rank, syntax, encoding,recordtype) VALUES ('foobar', 'lx2.loc.gov',210,'LCDB','','','LIBRARY OF CONGRESS',1,1,'USMARC','utf8','biblio’); I then imported the sample z3950 file, again. Next, using the Web interface, I was (successfully) able to search the Library of Congress. After identifying a record of interest, I tried to import it, but failed miserably because there were a whole bunch of fields missing. I was finally stymied when I could not select a value in Tab #9 for "Koha [default] item type”. I’m not giving up! — Eric Lease Morgan
Eric, the problem seems to be MySQL 5.6, I haven't got through a detailed review (I don't have it for testing right now) but there are several changes since MySQL 5.5, notably several default configurations and other backwards incompatible changes [1]. I recommend that you downgrade to MySQL 5.5, or better install on top of Ubuntu LTS/Debian Wheeze. I recommend Ubuntu 12.04 Server. And follow the official instructions [2]. Also, I'd like you to fill a bug in our tracker http://bugs.koha-community.org Name it something like 'Webinstaller fails to load sql data on MySQL 5.6'. Please paste the errors you saw, not all of them, but a representative example. Hopefully we can find a solution for this. Unfortunately not everyone might be interested as the vast majority of the devs, so please be patient, or ask for advise on the bug itself if you want to provide a fix yourself. Best regards Tomás [1] http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html [2] http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages El jul 4, 2014 4:59 PM, "Eric Lease Morgan" <eric_morgan@infomotions.com> escribió:
On Jul 4, 2014, at 3:16 PM, Eric Lease Morgan <eric_morgan@infomotions.com> wrote:
$ bulkmarcimport.pl -file /tmp/pamphlets.marc
And for each record in pamphlets.marc I get the following error:
.DBD::mysql::st execute failed: Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3222, <GEN15> line 1465. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET
Looks like you have an incomplete/broken DB schema. Have you already populated sensitive data? Otherwise i'd drop the database, create an empty one, and use the webinstaller to create the correct one.
Maybe I can initialize my koha database by hand?
I tried populating my database with many .sql files found in installer/data/mysql. Examples included but were not limited to:
* mysql -uroot -p koha < kohastructure.sql * mysql -uroot -p koha < sysprefs.sql * mysql -uroot -p koha < en/mandatory/auth_values.sql * ...
I then reconnected via the Web interface, and was prompted to do installation, again. (Bummer). It seemed to import things, again, but with the same errors as before, plus a few more about duplicate values. After this I was still not able to create patron profiles, etc.
I then tried to import the sample z39.50 servers:
$ mysql -uroot -p koha < sample_z3950_servers.sql
And I got this error:
ERROR 1364 (HY000) at line 1: Field 'description' doesn't have a default value
I then hacked sample_z3950_servers.sql to add a description field and look like this:
INSERT INTO z3950servers (description,host, port, db, userid, password, name, checked, rank, syntax, encoding,recordtype) VALUES ('foobar', 'lx2.loc.gov',210,'LCDB','','','LIBRARY OF CONGRESS',1,1,'USMARC','utf8','biblio’);
I then imported the sample z3950 file, again. Next, using the Web interface, I was (successfully) able to search the Library of Congress. After identifying a record of interest, I tried to import it, but failed miserably because there were a whole bunch of fields missing. I was finally stymied when I could not select a value in Tab #9 for "Koha [default] item type”.
I’m not giving up!
— Eric Lease Morgan
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
El jul 4, 2014 11:43 PM, "Tomas Cohen Arazi" <tomascohen@gmail.com> escribió:
Hopefully we can find a solution for this. Unfortunately not everyone
might be interested as the vast majority of the devs, 'use Debian/Debian-based distributions for developing/deploying' Sorry, writing on the phone at bed, did something unintended that deleted that text. Tomás
On Jul 4, 2014, at 10:43 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
Eric, the problem seems to be MySQL 5.6, I haven't got through a detailed review (I don't have it for testing right now) but there are several changes since MySQL 5.5, notably several default configurations and other backwards incompatible changes [1].
I recommend that you downgrade to MySQL 5.5, or better install on top of Ubuntu LTS/Debian Wheeze. I recommend Ubuntu 12.04 Server. And follow the official instructions [2].
Also, I'd like you to fill a bug in our tracker http://bugs.koha-community.org Name it something like 'Webinstaller fails to load sql data on MySQL 5.6'. Please paste the errors you saw, not all of them, but a representative example.
Hopefully we can find a solution for this. Unfortunately not everyone might be interested as the vast majority of the devs, so please be patient, or ask for advise on the bug itself if you want to provide a fix yourself.
[1] http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html [2] http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages
Alas, I can not afford to downgrade MySQL nor find an additional operating system. Instead, I have installed Koha version 3.16.01 on a machine with MySQL 5.1. Tomorrow I will dump the initialized database and import it into MySQL on a different machine where I plan to run Koha for “real". Wish me luck. I’m making progress. And, I will file a bug report. — Eric Lease Morgan
On Jul 5, 2014, at 12:07 PM, Eric Lease Morgan <eric_morgan@infomotions.com> wrote:
I recommend that you downgrade to MySQL 5.5, or better install on top of Ubuntu LTS/Debian Wheeze. I recommend Ubuntu 12.04 Server. And follow the official instructions [2].
[1] http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html [2] http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages
Alas, I can not afford to downgrade MySQL nor find an additional operating system. Instead, I have installed Koha version 3.16.01 on a machine with MySQL 5.1. Tomorrow I will dump the initialized database and import it into MySQL on a different machine where I plan to run Koha for “real". Wish me luck. I’m making progress.
Four steps forward and three steps back. I installed Koha 3.16.01 on a different host. I dumped the database. I installed Koha 3.16.01 on yet a different host, sans database initialization. Then, my hand, I populated my koha database with the database dump from the first host. After doing this I was able to add patrons, namely, myself. There were no weird errors. All of this was four steps forward. Then I: 1. used the Z39.50 interface to add some bibliographic records. I searched the Library of Congress for books on origami. I got a list. I tried to add one to my catalog. After filling out a number of fields I said go, but it did not save. I forget what the error was. I tried other searches, and no matter what I searched for I got no results. It seemingly broke. One step backwards. 2. tried to stage some records. Import. See all 1,400 of them. I cleaned them. I try to import the staged records and get "No data available in table”. A second step backwards. 3. su’ed to the koha user. I set my environment variables. I ran bulkimport.pl and I got the same errors as before. ".DBD::mysql::st execute failed: Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3222, <GEN15> line 1465. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET” Searches against my OPAC return Zebra error 109. I have no bibliographic data. A third step backward. I’m running out of options. I will: 1. try to repeat the above process but with version 3.14 2. break down and use my “different host” — Eric
Eric, I've read the changes from 5.5 to 5.6, and don't seem to be a way to prevent the problems you found with any option switch. I don't think 3.14 would do it better. You should fill the bug, and remeber you can have a separate DB server until we solve it. Regards To+ On Sun, Jul 6, 2014 at 12:19 PM, Eric Lease Morgan < eric_morgan@infomotions.com> wrote:
On Jul 5, 2014, at 12:07 PM, Eric Lease Morgan < eric_morgan@infomotions.com> wrote:
I recommend that you downgrade to MySQL 5.5, or better install on top of Ubuntu LTS/Debian Wheeze. I recommend Ubuntu 12.04 Server. And follow the official instructions [2].
[1] http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html [2] http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages
Alas, I can not afford to downgrade MySQL nor find an additional operating system. Instead, I have installed Koha version 3.16.01 on a machine with MySQL 5.1. Tomorrow I will dump the initialized database and import it into MySQL on a different machine where I plan to run Koha for “real". Wish me luck. I’m making progress.
Four steps forward and three steps back.
I installed Koha 3.16.01 on a different host. I dumped the database. I installed Koha 3.16.01 on yet a different host, sans database initialization. Then, my hand, I populated my koha database with the database dump from the first host. After doing this I was able to add patrons, namely, myself. There were no weird errors. All of this was four steps forward. Then I:
1. used the Z39.50 interface to add some bibliographic records. I searched the Library of Congress for books on origami. I got a list. I tried to add one to my catalog. After filling out a number of fields I said go, but it did not save. I forget what the error was. I tried other searches, and no matter what I searched for I got no results. It seemingly broke. One step backwards.
2. tried to stage some records. Import. See all 1,400 of them. I cleaned them. I try to import the staged records and get "No data available in table”. A second step backwards.
3. su’ed to the koha user. I set my environment variables. I ran bulkimport.pl and I got the same errors as before. ".DBD::mysql::st execute failed: Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3222, <GEN15> line 1465. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET” Searches against my OPAC return Zebra error 109. I have no bibliographic data. A third step backward.
I’m running out of options. I will:
1. try to repeat the above process but with version 3.14 2. break down and use my “different host”
— Eric
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F
I recommend that you downgrade to MySQL 5.5, or better install on top of Ubuntu LTS/Debian Wheeze. I recommend Ubuntu 12.04 Server. And follow the official instructions [2].
[1] http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html [2] http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages
I have (finally) gotten Koha up and running. The bottom is this: 1) I needed to use MySQL version 5.5, and 2) I needed to edit koha-conf.xml to correctly configure zebrasrv. Here is a more detailed description: 1. I’m running an older version of the Linux operating system - RHEL 5 — and its software has been installed using a huge mixture of locally compiled source files and yum. 2. The Koha installation process did not like my mysql client because it throws an error to STDOUT when passwords are passed on the command line. 3. After many (many) other attempted work arounds, I downgraded MySQL to version 5.5. I was using version 5.6. After this, the Web-based installation process went without a hitch. (Whew!) 4. I could now do bulk imports using the Web interface, and I could search remote Z39.50 servers to add bibliographic records to my catalog. But I could not search nor find things in the catalog. Searches against zebrasrv always returned error #109. Moreover, I could not use the command line application (bulkmarcimport.pl) to do… bulk imports. 5. Taking a closer look at koha-conf.xml I saw that some of the paths were not correct. For example, my biblios index was not located in /var/lib/koha/zebradb/ but rather /etc/koha/zebradb/. I changed them accordingly. Unfortunately, zebrasrv still returned error #109. After rooting around on the Web I discovered an additional path I needed to configure. Specifically, I needed to edit files like zebra-biblios.cfg and configure modulePath to point to my locally compiled idzebra modules. [1] (They are in /usr/local/lib/idzebra-2.0/modules, not /usr/lib/idzebra-2.0/modules.) 6. After restarting zebrasrv, I was able to do everything. Add records. Index records. Find records. (Double whew!) Library catalogs (OPACs, “discovery systems”, whatever you want to call them) are not simple applications/systems. They are a mixture of VERY specialized inventory lists, various types of people with various skill and authorities, indexing, and circulation, etc. Then we — as librarians — add things like messages of the day, record exporting, browsable lists, visualizations, etc. that complicate the whole thing. It is simply not possible to create a library catalog in the “Unix way”. [2] At the same time, I’ve been advocating open source software for quite a while, and I understand the meaning of “free” in this context. I’m not complaining. Really. That said, my next step is to discover and turn on all the ways Koha can expose its bibliographic and authority content to the ‘Net. The things like Z39.50, SRU, and OAI-PMH come to mind. The ultimate goal is to discover the feasibility of exposing bibliographic and authority content in YAF — “linked data”. [3, 4] I’m very impressed with the Koha community. It is large and international in scope. If all Koha implementations were to make their content available as linked data, then the whole would so much greater than the sum of its parts. But right now I need to rest. (Whew, again!) Thank you for your patience. [1] zebra configuration - http://stackoverflow.com/questions/23928040/koha-3-14-zebra-search-is-not-wo... [2] Unix Way - http://en.wikipedia.org/wiki/Unix_philosophy [3] YAF - Yet Another Format [4] linked data - http://en.wikipedia.org/wiki/Linked_data — Eric Lease Morgan
On 11 July 2014 21:15, Eric Lease Morgan <eric_morgan@infomotions.com> wrote:
The ultimate goal is to discover the feasibility of exposing bibliographic and authority content in YAF — “linked data”.
Awesome! This might be redundant, but I'd like to point out there are some efforts in this direction already: Some thougts from me are on the wiki: http://wiki.koha-community.org/wiki/Linked_Data_RFC Chris Cormack has been working on an automatic conversion from MARC to RDF-in-a-triplestore when records are saved in Koha: https://gitorious.org/koha/mainline/commits/ff19b7040d550811ec0f5eaee93f6fb6... (Not sure if that is the best link for it) (I think Chris would like to rewrite this to use Catmandu::Exporter::RDF) I have been working off and on on a Linked Data Browser for Koha: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10788 By far the most ambitious project related to Koha and RDF/Linked Data (that I know of) is the one at Oslo Public Library (where I am currently on paternity leave from a part time, temporary position). Their aim is to have RDF as the master data format (which includes cataloguing in RDF) and push MARC-records converted from RDF into Koha, so Koha can do circulation and other menial tasks. ;-) Some relevant blogposts: http://digital.deichman.no/blog/2014/01/16/oslo-public-library-chooses-the-f... http://digital.deichman.no/blog/2014/06/19/oslo-public-library-chooses-rdf-l... http://digital.deichman.no/blog/2014/07/06/rdf-linked-data-cataloguing-at-os... They/we have stuff like a marc2rdf converter: https://github.com/digibib/marc2rdf and are working on a cataloguing interface (independent of Koha): https://github.com/digibib/armillaria
If all Koha implementations were to make their content available as linked data, then the whole would so much greater than the sum of its parts.
For me, just converting MARC to RDF is not that interesting or useful. It gets interesting when - we start to have proper identifiers for things, instead of text strings, and when - librarians can start to augment the data from the MARC records with new kinds of data (that would never have fitted into MARC) that we can then use to create useful new features Let's get the conversation going! :-) Best regards, Magnus
Hi Eric,
Maybe I can initialize my koha database by hand?
no, it is not a good idea. If you want to try again: -- drop and rebuild an empty db -- run web installer, select marc21 as format and select to import also every optional table by web installer then login, create a biblio, create a user with superlibrarian permission, logout and relogin with new user. Then try again to import a biblio record with z39.50 from LOC. if you have problem to save data into MySQL, it is probably a bug. To search you need to have active z39.50 and to have indexed the record. Bye Zeno Tajoli
FYI, the Features site (http://ils.foss4lib.org) includes over 1000 ILS features, the vast majority of which are functional in both Koha and Evergreen. Updates are current through nearly all of the version 3.14 new features (this will soon be reflected more clearly). Can you clarify for me which features are listed as NO which are actually YES in Koha now? I will correct those ASAP. The features database was generated from RFP's and RFI's published by libraries in the recent past, and supplemented with new features development from the past 18 months of Koha and Evergreen versions. Of course, the Features site cannot list every bit of functionality in the Koha software, but we hope its value lies in meeting the stated needs of libraries seeking a new ILS with the current capabilities of open source systems. As the person responsible for updates over the past 18 months I welcome additional documentation of new functions. Currently, I study the notes in Bugzilla and comb the release notes and documentation for explanations of new functionality, but I could definitely use additional information. The Bywater videos offer excellent depth--thank you Nicole Engard!--and I would love to see more. Respectfully, Diana Spaulding The Galecia Group On Thu, Jul 3, 2014 at 6:42 PM, Lori Bowen Ayre <lori.ayre@galecia.com> wrote:
Hi All,
I'm sorry that the features listing is out-of-date but we will be bringing it up to speed very soon. As Nicole and Hugo mentioned, it is more about letting people know that the Koha and Evergreen product DO have all the features that people expect from the proprietary ILSs. I'd love to add Alma and Symphony, WMS, and Sierra, etc, to the list but sadly, that is way more of an undertaking than my company or Lyrasis can handle. So, by putting this product out there, we are at least taking some pressure off the service providers (e.g. ByWater, Equinox, Catalyst, PTFS, Libime???) who might not have the marketing departments that Innovative and SirsiDynix and OCLC have.
It would be great to get a little help from the Koha community on this as it ultimately benefits everyone by enticing more people to move to Koha (and Evergreen). I understand your reluctance but I hope you'll see this resource as something desired to support Open Source, not hinder.
If you'd like to contribute, let me know. In the meantime, we do expect to get it updated in the next couple of weeks or so. But feedback about features we're misrepresented or which need to be added are ALWAYS welcome!
Lori
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group (707) 763-6869 // Lori.Ayre@galecia.com Availability: http://doodle.com/loriayre
<Lori.Ayre@galecia.com>Specializing in software solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Thu, Jul 3, 2014 at 1:39 PM, Nicole Engard <nengard@gmail.com> wrote:
I'm with Hugo and Chris - in that it's not really a useful tool, but I worry that people will see it and say oh Koha (or Evergreen) can't do XYZ and so isn't as good as Proprietary System ABC. Just thought you should all know it's out there so you can educate people accordingly - I know I will.
Nicole _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
For someone trying to make up their mind choosing between Evergreen and Koha the website would send them to Evergreen. Just because you are a Koha true believer (this is the Koha listserv!) doesn't mean that everyone else will choose Koha. There is nothing in the comparison to indicate version nor how old it it. The comparison should be correct, accurate, and up to date. my $0.02 Steve sowder@andrews.edu On 7/3/2014 4:39 PM, Nicole Engard wrote:
I'm with Hugo and Chris - in that it's not really a useful tool, but I worry that people will see it and say oh Koha (or Evergreen) can't do XYZ and so isn't as good as Proprietary System ABC. Just thought you should all know it's out there so you can educate people accordingly - I know I will.
Nicole _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Hi Steve, Diana will be responding in more detail but the home page of the site lists the versions being compared. We are a bit behind but we do try to keep it as current as possible. I'm not sure who you are responding to when you make your "true believer" comment but I'm quite agnostic as to Koha and Evergreen and just generally interested in helping people see that both are extremely fully featured. So, the site was created to fulfill that purpose more than to point them away from either Koha or Evergreen. And, if you would like to help us correct any mistakes or add information that you feel is lacking, we'd love to have your help. Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group (707) 763-6869 // Lori.Ayre@galecia.com Availability: http://doodle.com/loriayre <Lori.Ayre@galecia.com>Specializing in software solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Fri, Jul 4, 2014 at 5:27 AM, Steve Sowder <sowder@andrews.edu> wrote:
For someone trying to make up their mind choosing between Evergreen and Koha the website would send them to Evergreen.
Just because you are a Koha true believer (this is the Koha listserv!) doesn't mean that everyone else will choose Koha.
There is nothing in the comparison to indicate version nor how old it it.
The comparison should be correct, accurate, and up to date.
my $0.02
Steve sowder@andrews.edu
On 7/3/2014 4:39 PM, Nicole Engard wrote:
I'm with Hugo and Chris - in that it's not really a useful tool, but I worry that people will see it and say oh Koha (or Evergreen) can't do XYZ and so isn't as good as Proprietary System ABC. Just thought you should all know it's out there so you can educate people accordingly - I know I will.
Nicole _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Lori,
Diana will be responding in more detail but the home page of the site lists the versions being compared. We are a bit behind but we do try to keep it as current as possible.
Perhaps you might mitigate some of the concerns by noting explicitly that "The features are updated through Koha version 3.10 (released November 2012; current Koha version: 3.16) and Evergreen version 2.4 (released May 2013; current Evergreen version: 2.6). More recent releases may include some features not reflected on this site" or something along those lines? Updated appropriately to reflect actual versions. I guess it should say Koha 3.14, and maybe Evergreen 2.5 (per Diana's e-mail)? Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/
Thanks for the suggestion, Jared. We can do that. -Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group (707) 763-6869 // Lori.Ayre@galecia.com Availability: http://doodle.com/loriayre <Lori.Ayre@galecia.com>Specializing in software solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Mon, Jul 7, 2014 at 5:34 PM, Jared Camins-Esakov < jcamins@cpbibliography.com> wrote:
Lori,
Diana will be responding in more detail but the home page of the site lists the versions being compared. We are a bit behind but we do try to keep it as current as possible.
Perhaps you might mitigate some of the concerns by noting explicitly that "The features are updated through Koha version 3.10 (released November 2012; current Koha version: 3.16) and Evergreen version 2.4 (released May 2013; current Evergreen version: 2.6). More recent releases may include some features not reflected on this site" or something along those lines? Updated appropriately to reflect actual versions. I guess it should say Koha 3.14, and maybe Evergreen 2.5 (per Diana's e-mail)?
Regards, Jared
-- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/
Hi everyone, I think this is a valuable and helpful tool for librarians and sales departments asweel, so my 2 cents are: +1 and keep up the good work! :) Thanks, Fabio 2014-07-08 2:34 GMT+02:00 Jared Camins-Esakov <jcamins@cpbibliography.com>:
Lori,
Diana will be responding in more detail but the home page of the site lists the versions being compared. We are a bit behind but we do try to keep it as current as possible.
Perhaps you might mitigate some of the concerns by noting explicitly that "The features are updated through Koha version 3.10 (released November 2012; current Koha version: 3.16) and Evergreen version 2.4 (released May 2013; current Evergreen version: 2.6). More recent releases may include some features not reflected on this site" or something along those lines? Updated appropriately to reflect actual versions. I guess it should say Koha 3.14, and maybe Evergreen 2.5 (per Diana's e-mail)?
Regards, Jared
-- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/ _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
On 8/07/2014 11:02 pm, "Fabio Tiana" <fabio.tian@gmail.com> wrote:
Hi everyone,
I think this is a valuable and helpful tool for librarians and sales departments asweel, so my 2 cents are: +1 and keep up the good work! :)
Cool, in that case, thank you for volunteering to keep it up to date. Chris
Thanks, Fabio
2014-07-08 2:34 GMT+02:00 Jared Camins-Esakov <jcamins@cpbibliography.com :
Lori,
Diana will be responding in more detail but the home page of the site lists the versions being compared. We are a bit behind but we do try to keep it as current as possible.
Perhaps you might mitigate some of the concerns by noting explicitly that "The features are updated through Koha version 3.10 (released November 2012; current Koha version: 3.16) and Evergreen version 2.4 (released May 2013; current Evergreen version: 2.6). More recent releases may include some features not reflected on this site" or something along those lines? Updated appropriately to reflect actual versions. I guess it should say Koha 3.14, and maybe Evergreen 2.5 (per Diana's e-mail)?
Regards, Jared
-- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/ _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
On Thu, Jul 3, 2014 at 3:22 PM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
I'm actually pretty ambivalent about it. I don't see pitching Koha vs Evergreen is helpful. Either of them are always going to be better than any proprietary system. Simply because they are not proprietary.
I don't trust comparison lists. Besides often being outright incorrect and populated by folks who don't know all the systems equally well, I feel like you risk comparing apples to oranges while calling both bananas, with the fruit being airborne to boot. And if you get so fine grained that there isn't much ambiguity for what a bullet point actually means, then you can still miss the forest for the trees, while providing a misleading sampling of specific types of trees. I would rather see the software in action and compare on that basis, for a given need. You'll pick up a lot of information missing from a bullet point--for example, how usable a given feature actually is. And, hey, with Koha and Evergreen, at least, there is nothing stopping you from checking these things out. I generally think that all software has strengths and weaknesses, and for non-trivial software there is no such thing as being “feature complete”. A given application has a set of features that is either aligned with the needs of the people actually using the software or not, and for free and open source software, these feature sets are very malleable. If folks feel compelled to create these things (and I think the urge to maintain them is much weaker than the urge to create them), I think they should provide the benefits for each feature, to help provide more context. Incidentally, EG 2.4 has a security-update only status; 2.5 and 2.6 are the latest stable series. -- Jason Etheridge | Support Manager | Equinox Software, Inc. / The Open Source Experts | phone: 1-877-OPEN-ILS (673-6457) | email: jason@esilibrary.com | web: http://www.esilibrary.com
participants (14)
-
Chris Cormack -
Chris Cormack -
Diana Spaulding -
Eric Lease Morgan -
Fabio Tiana -
Hugo Agud -
Jared Camins-Esakov -
Jason Etheridge -
Lori Bowen Ayre -
Magnus Enger -
Nicole Engard -
Steve Sowder -
Tomas Cohen Arazi -
Zeno Tajoli