- Koha-devel - lists.koha-community.org

about records in koha pro
by Samuel Desseaux 24 Jan '13

24 Jan '13

Hi, I've a question of my colleagues. In the opac, when i'm looking for something, i've the results and when i choose one of the results, i can add a link to come back to the results and another link to the search example: i make a research and it gives the results http://koha.ecp.fr:8080/cgi-bin/koha/catalogue/search.pl?q=eau I choose one of the result and there, i 'd be able to see the next record which is in the list of results. Is it possible? I hope that you will understand my request. Best regards, samuel

2 1

install all locales to install Koha::Contrib::Tamil
by Zeno Tajoli 24 Jan '13

24 Jan '13

Hi to all, I'm starting to install Koha on a Debina squeeze amd64. I work from the net-CD so a minimal systen. I want to install Koha::Contrib::Tamil to use background indexing. I see that I need to install all locales to install it with CPAN. I think the problem is in the module Locale::TextDomain. In fact is not a problem, it is quite easy to do with 'sudo dpkg-reconfigure locales' [first option of first menu]. I think this is a useful tip for all. I will update http://wiki.koha-community.org/wiki/Background_indexing_with_Zebra Bye Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli(a)cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate

2 3

Re: [Koha-devel] koha-zebra-daemon not starting
by Paul 24 Jan '13

24 Jan '13

I've tried to keep this to a minimum, there is a 'conclusion' further down: At 11:47 AM 8/20/2012 -0300, Tomas and Barry wrote: >On Sun, Aug 19, 2012 at 4:36 PM, Paul <paul.a(a)aandc.org> wrote: > > Koha 3.8.3 on Ubuntu 12.04 LTS server (new install, full upgrade) >[snip] > > But neither OPAC nor staff search functions are operational. > > > > The only anomaly that I've found so far is that > > /etc/init.d/koha-zebra-daemon when run from the command line reports > failure > > at line 73 (and does not create any error logs), but ps aux reports the > > daemon as running (well, "S+" -- sleep forground.) > > > > Anyone got any thoughts please? > >You need to answer what method r u using for install. Pls see my earlier email [Mon, 20 Aug 2012 09:48:19 -0400] >If using >tarball, then you might be running the zebra daemon using de 'koha' >user and 'koha' group. Do they exist? If this was the case, then this >should create the missing dir: > >mkdir -p /var/lock/koha/zebradb/biblios/ ; chown -R koha:koha >/var/lock/koha/zebradb/ Yes - tarball, but the dir was already (correctly) there: paul@server:/var/lock/koha/zebradb$ ls -l total 0 drwxr-xr-x 2 koha koha 40 Aug 20 11:33 authorities drwxr-xr-x 2 koha koha 40 Aug 20 11:33 biblios >Also (just in case): >chown -R koha:koha /var/log/koha Again, correctly there: paul@server:/var/log$ ls -l | grep koha drwxr-xr-x 2 koha koha 4096 Aug 19 11:19 koha >Also, every time you run rebuild_zebra.pl you should do it like: > >su - koha -c "KOHA_CONF=/etc/koha/koha-conf.xml >PERL5LIB=/usr/share/koha/lib >/usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -r -v -x" What's the '-c'? (I don't think I've ever used this construct) and I don't think there's any difference, but I 'su koha' first, then 'cd usr/share/koha', then KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -a -r -v and KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -b -r -v -x and Barry Cannon wrote: >Shouldn't running "zebrasrv -f /etc/koha/koha-conf.xml" (or whatever your >path is) as the index owner give you a good indication of what is going on >(it should at least get you pointed in the right direction as it should >dump out the error to console) Interesting !!! or ;=} -- I tried that: koha@server:/$ zebrasrv -f /etc/koha/koha-conf.xml 11:51:06-20/08 [log] zebra_start 2.0.44 419ad759807269fdfa379799a051ed3a551c6541 11:51:06-20/08 [log] config /etc/koha/zebradb/zebra-biblios-dom.cfg 11:51:06-20/08 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-xml.so [snip more filters for zebra-biblios-dom and zebra-authorities-dom 11:51:06-20/08 [server] Adding dynamic listener on unix:/var/run/koha/zebradb/bibliosocket id=1 11:51:06-20/08 [server] Adding dynamic listener on unix:/var/run/koha/zebradb/authoritysocket id=2 at which point that terminal just hangs on an ongoing op, but shows that the sockets were not previously opened. So, re-indexing again: for authorities: 25901................................ Records exported: 25933 ==================== REINDEXING zebra ==================== skipping biblios ==================== CLEANING ==================== and for biblios: 37301...........................................................................37401.................... Records exported: 37417 ==================== REINDEXING zebra ==================== 12:04:12-20/08 zebraidx(2841) [warn] Unknown register type: ==================== CLEANING ==================== Which corresponds to the ps aux | grep koha during the re-indexing: koha 2738 0.0 0.1 119084 4212 pts/2 S+ 12:01 0:00 su - koha -c KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -r -v -x koha 2747 73.8 1.4 259028 56272 pts/2 S+ 12:01 2:07 /usr/bin/perl /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -r -v -x koha 2841 96.1 1.6 233556 64240 pts/2 Rl+ 12:04 0:27 zebraidx -c /etc/koha/zebradb/zebra-biblios-dom.cfg -v none,fatal,warn -g marcxml -d biblios update /tmp/q2UPWJgDrk/biblio and now we've got the search in OPAC and staff-admin finding the 37301 biblios. And I still don't know what the "[warn] Unknown register type: " might mean. Some hangover from 3.6.1 to 3.8.3? BUT ... the incremental cron (shows up in /var/log/syslog as working every 1 minute), does _NOT_ add new records. Conclusion: I'll keep going at this (half an hour here and there, it's our "tourist season", busiest time of the year) but somewhere, can't remember, there's something about Ubuntu 12.04 not renewing sockets, .LOKs, etc on reboot. Maybe I'm way off track, but it's the best avenue I have at the moment. Thoughts, please? Best - Paul

6 17

Re: [Koha-devel] Bug 8641
by Archives and Collections Society 24 Jan '13

24 Jan '13

At 06:48 PM 1/22/2013 -0500, Jared Camins-Esakov wrote: >Paul, >This bug was signed off a few weeks ago, and is designed to produce a >"warning" in the "About" page covering staff use of Koha (not sure if this >covers all flag settings down from superlibrarian or if it applies to 3.8. >as well as 3.10?) logging in as either "root", "admin (mysql) account" or >"database administrative user." >I seem to remember (but could be wrong) that after a new 3.8 install, Koha >created a "new user", number 0, which was problematic and as far as I can >tell exhibited the signs that the warning covers (I have tried to read all >details in bugs 8641, 8262 and 9008 plus some references to IRC.) >You are. User "0" is the database administrative user. Do not use it for >anything other than initial installation and upgrades. Ever. Thanks Jared. I'm glad that my memory didn't fail me :) and that I never use it. But I'm still interested in the "warning" - particularly as you mention that it should be used for upgrades. As far as I can see (using getent passwd | cut -d : -f 1 | xargs groups) there is no problem with *system* security. Also, User "0" does not appear in the MySql 'borrowers' table. So why is it possible to log in with the "warned against" credentials? How should it be used during upgrades? It also is possible to create a superlibrarian with User "koha" credentials; limited testing in my sandbox has not [yet!] shown any side effects, except that User "0" can no longer log in (demonstrated by the fact that "Library" is set.) Best - Paul

5 5

Re: [Koha-devel] Bug 8641
by Paul 23 Jan '13

23 Jan '13

At 06:48 PM 1/22/2013 -0500, Jared Camins-Esakov wrote: >Paul, >This bug was signed off a few weeks ago, and is designed to produce a >"warning" in the "About" page covering staff use of Koha (not sure if this >covers all flag settings down from superlibrarian or if it applies to 3.8. >as well as 3.10?) logging in as either "root", "admin (mysql) account" or >"database administrative user." >I seem to remember (but could be wrong) that after a new 3.8 install, Koha >created a "new user", number 0, which was problematic and as far as I can >tell exhibited the signs that the warning covers (I have tried to read all >details in bugs 8641, 8262 and 9008 plus some references to IRC.) >You are. User "0" is the database administrative user. Do not use it for >anything other than initial installation and upgrades. Ever. Thanks Jared. I'm glad that my memory didn't fail me :) and that I never use it. But I'm still interested in the "warning" - particularly as you mention that it should be used for upgrades. As far as I can see (using getent passwd | cut -d : -f 1 | xargs groups) there is no problem with *system* security. Also, User "0" does not appear in the MySql 'borrowers' table. So why is it possible to log in with the "warned against" credentials? How should it be used during upgrades? It also is possible to create a superlibrarian with User "koha" credentials; limited testing in my sandbox has not [yet!] shown any side effects, except that User "0" can no longer log in (demonstrated by the fact that "Library" is set.) Best - Paul _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

1 0

RM vacation
by Jared Camins-Esakov 23 Jan '13

23 Jan '13

Good morning. I just wanted to let folks know that the RM will be on vacation starting this Friday, January 25, until Monday, February 4. I anticipate no crises in my absence, and will probably check my e-mail, but the amount of time I spend on testing and pushing will be greatly curtailed. Also, I'll be in California, so if I'm around, it will be four hours later than is my wont. Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

1 0

Bug 8641
by Paul 23 Jan '13

23 Jan '13

This bug was signed off a few weeks ago, and is designed to produce a "warning" in the "About" page covering staff use of Koha (not sure if this covers all flag settings down from superlibrarian or if it applies to 3.8. as well as 3.10?) logging in as either "root", "admin (mysql) account" or "database administrative user." I seem to remember (but could be wrong) that after a new 3.8 install, Koha created a "new user", number 0, which was problematic and as far as I can tell exhibited the signs that the warning covers (I have tried to read all details in bugs 8641, 8262 and 9008 plus some references to IRC.) Maybe I'm paranoid, but could someone please clarify how far any problems might extend. If someone sets up a *new* Koha superlibrarian account using the same name/password as system (sudo) user and/or with all MySql privileges, permission tables should not interfere with one another, or overlap, even when identical user/pw combinations are used. Surely this would only apply if staff-user is "koha" or whatever other name was explicitly granted MySql privileges during/immediately after Koha installation. Am I mistaken? Thanks and best regards, Paul

2 1

Old bugs to check
by MJ Ray 22 Jan '13

22 Jan '13

Would you check some of these rather old bugs to suggest what to do, please? Maybe some can be RESOLVED FIXED by now or need a question. Ideally, tell irc.oftc.net #koha know that you're looking at a bug. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5672 Search History Should have RSS Feeds http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2960 Cyrillic Z39-50 servers (bad encoding results) http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5169 name/rename label batches http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2645 Put Total Due at top of Fines page/seperate paid from unpaid http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5472 Build script needs updating for 3.2.1 release http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3200 missing quotes in rebuild_unimarc_100.pl http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5789 Fines don't work when items have null homebranch http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5501 why is there a 'do not notify' option? http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4125 Bulkmarcimport.pl script has changed a lot without beeing documented http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4874 debian/scripts/koha-* should use Koha instance DB credentials http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3343 duplicate subfields in authority http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5024 Debian packages don't include YUI plugins http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4855 Tools/Export does not tell browser file size http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3147 call to ModZebra in DelAuthority fails (fatal error) if record previously deleted but still exists in index http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5340 bulk subscription renewal http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5721 marc import summary should be filtered or customizable http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5270 007 variable control builder/Specific Material Designation http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3111 Opac lists all ITYPES as same, when database lists different. Other OPAC issues. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5538 would be nice to search both collection code and item type -- Email robot driven by MJ Ray (slef), member of www.software.coop, http://koha-community.org supporter, web and library systems developer. Available for hire (including development) at http://www.software.coop/

1 0

Contents of more_subfields_xml
by Paul 22 Jan '13

22 Jan '13

I have recently done some "house-keeping" looking for consistency in the MySQL db (5.5.24 in 3.8.5), and while some tidying up has been straight-forward I am having problems with more_subfields_xml in items. Only about 90% of 'items' have any xml attached to them. Within those that do have an xml entry, only the following subfields appear: <subfield code="f"> entries < 1% <subfield code="i"> entries ~ 20% <subfield code="k"> entries ~ 1.5% <subfield code="x"> entries ~ 95% and they are mostly filled with random values from 2xx, 6xx and 9xx, although the 'code="x"' values appear to be valid from the 952$x. code="f" contains values from 952$v; code="i" has some 952$i valid entries but mostly 650$a,x,y,z; code="k" has random authors, titles, etc - and I can't find where we might use 952$k in our frameworks. Can someone please tell me how these blobs are mapped/created and used by koha? Our odd-ball results/entries don't appear to be having much, if any, influence on cataloguing and search functions. Also, if there is any way to "rebuild" more_subfields_xml -- it's way too big a problem to manage manually. Many thanks - Paul P.S. For completeness, after de-duping all the entries obtained from " SELECT more_subfields_xml FROM items; " (249,636 text lines), the only data left (apart from the subfields above) are "empty containers" using: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/MARC21/slim"> xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd" <?xml version="1.0" encoding="UTF-8"?> <collection </collection> <datafield tag="999" ind1=" " ind2=" "> </datafield> <leader> a </leader> <record> </record>

2 1

About installation in OpenSuse 12.x
by John Herz 22 Jan '13

22 Jan '13

Hello: I am looking for instalation instruction in OpenSuse 12.x if any have some experience, in the wiki only show without zebra configuring :( thank you

2 1