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

Bug 8665, files, git ...
by Paul 14 Oct '12

14 Oct '12

Good morning all, Probably a very naive question; I would like to try the proposed solution (Bug 8665) and can find the "diff", but when I try and navigate "git", the relevant section (if I have navigated successfully which is dubious as I'm new to "git") <https://github.com/Koha-Community/Koha/tree/master/etc/zebradb/marc_defs/ma…>, the master appears to stop at Bug 7475. Is there anywhere to find "ready edited" files, rather than copy/paste lines from the diff? Many thanks -- Paul

3 3

1st patch in bugzilla
by Mathieu Saby 13 Oct '12

13 Oct '12

Hi I've made my first bug report and my first patch in bugzilla. Even if you don't plan to test it, could you just take a look and tell me if there is something *formally *wrong with my bug and my patch ? I'm just a librairian, so I hope I've understood the process... http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8916 Should I write a mail with my patch to koha-patches(a)lists.koha-community.org now ? Kind regards, M. Saby Rennes 2 university -- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

1 0

patron card PDF - without making a batch - v3.08?
by Waqar Azeem 12 Oct '12

12 Oct '12

Can koha admin generate patron-card without making a batch (Tools › Patron card creator)? I was looking for a feature that administrator can generate the patron-card directly from Patron detail page. During my code browsing I found two files 'print.pl' and 'create-pdf.pl' in 'patroncards' folder. Good thing was there was already a GET parameter 'borrower_number' (@borrower_numbers) that seem to be used to generate the PDF for a list of borrower. So, I think there is/was a feature from where i could chose a list of patrons without making a Batch. This code also seem to have a bug! I didn't find any online browse-able code therefore a snip-it from create-pdf.pl is here: grep { push(@{$items}, {*item_number* => $_}); } @borrower_numbers; 'item_number' itself is not used anywhere. 'browser_number' is used to retrieved this data. foreach my $item (@{$items}) { if ($item) { my $borrower_number = $item->{'*borrower_number*'}; When I replaced second with the first one, it stared to generate the pdf local URL to test: http://waqar/cgi-bin/koha/patroncards/print.pl?borrower_number=19 -- Thanks & Best Regards, Waqar Azeem

2 1

001 in 3.8.x
by Paul 12 Oct '12

12 Oct '12

We are - perhaps erroneously - coming to the conclusion that a part (major? minor?) of our "authorities" and possibly "other" problems in 3.8.4/5 is due to field 001. Error messages such as "Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/AuthoritiesMarc.pm line 335" lead to 'my $authid=$authrecord->field('001')->data();' Philosophically - again perhaps erroneously - the definition of 001 does not require absolute uniqueness, but, taken in conjunction with 003 they should be [1]. We (unfortunately and for whatever reasons) have several hundred "duplicates" all with our 003 CaOPIACS attached. Our cataloguers are having a lengthy discussion about "our" responsibility, "original agency", "transcribing agency", "modifying agency" without any firm conclusion. So I'm left with the IT side of things ;={ Without major risk to the sql db, I am looking for a way to correct these, but will probably end up "editing" using the Koha interface -- but I am running into trouble and would appreciate some advice. We can't ask the cataloguers to "remember" the last number used, so in 3.6.1 I wrote a "plugin" called by field 001 from addbiblio based (extremely closely) on callnumber.pl that served us well. The only relevant changed line is: my $dbh = C4::Context->dbh; # If the textbox is empty, we return a simple incremented callnumber if ( $code eq "" ) { # my $sth = $dbh->prepare("SELECT MAX(CAST(itemcallnumber AS SIGNED)) FROM items"); ################# # replaced with # ################# my $sth = $dbh->prepare("SELECT MAX(CAST(TRIM(EXTRACTVALUE(marcxml,'//controlfield[\@tag=\"001\"]')) AS UNSIGNED)) from biblioitems where EXTRACTVALUE(marcxml,'//controlfield[\@tag=\"003\"]') = 'CaOPIACS'"); $sth->execute; if ( my $max = $sth->fetchrow ) { $template->param( return => $max+1, ); } It works well *if* the cataloguer (after clicking on the 003 to bring it to our framework default, books, fastadd, etc of 'CaOPIACS') remembers to delete the 001 and click on the icon. Could this be automated? i.e. IF {003 has changed} THEN {blank out 001} END IF (note I have made 001 mandatory, so records will not save with a blank entry.) I am just not savvy enough with the intracicies of perl to mysql to template, etc, coding. Or maybe a js guru could find something for addbiblio.js which seems to be empty...? Also (my dream to avoid manually editing hundreds of records), could any of you possibly come up with some mysql code to replace duplicates (I can define the starting number for replacement values). Or, maybe, (I'm sure there must have been a good reason not to use biblionumber for indexing zebra) just replace duplicate 001s with biblionumber (in my case, not necessarily true for anyone else, all out biblionumbers are less than 7 digits, and our 001s (and as far as I can see other major libraries via Z39.50) are at least 8 digits Many thanks and best regards, Paul Note [1]: from LoC <http://www.loc.gov/marc/bibliographic/bd001.html> 001 - Control Number (NR) MARC 21 Bibliographic - Full FIELD DEFINITION AND SCOPE Contains the control number assigned by the organization creating, using, or distributing the record. For interchange purposes, documentation of the structure of the control number and input conventions should be provided to exchange partners by the organization initiating the interchange. The MARC code identifying whose system control number is present in field 001 is contained in field 003 (Control Number Identifier).

2 1

CAS authentification
by Samuel Desseaux 11 Oct '12

11 Oct '12

Hi, We plan to use our CAS in order to access to the intranet and , for the user, to his account. I work with mod-proxy on apache and my questions are about configuration. I've created 3 files in /apache2/conf.d 1) cas.conf > <Proxy *> > Order Allow,Deny > Allow from All > AuthName "Acces Intranet" > AuthType CAS > Require valid-user ************************ > </Proxy> > Can i duplicate this block for the opac in the same file? 2)proxy_opac.conf > ProxyRequests On > ProxyPass /cgi-bin/koha/ ! > ProxyPass /cgi-bin/koha/ http://localhost:80/cgi-bin/opac/opac-user.pl > ProxyPassReverse /cgi-bin/koha/ > http://localhost:80/cgi-bin/opac/opac-user.pl > ProxyPreserveHost On I've some doubt on the writing because i've the following error HTTP Status 404 *type* Status report *message* _/cgi-bin/koha/opac-user.pl_ *description* _The requested resource (/cgi-bin/koha/opac-user.pl) is not available._ 3)proxy_intranet.conf > ProxyRequests On > ProxyPass /cgi-bin/koha ! > ProxyPass /cgi-bin/koha http://localhost:8080/cgi-bin/koha/mainpage.pl > ProxyPassReverse /cgi-bin/koha > http://localhost:8080/cgi-bin/koha/mainpage.pl > ProxyPreserveHost On Best regards samuel

1 1

Call for News for the October Newsletter
by Daniel Grobani 10 Oct '12

10 Oct '12

Dear Koha Kommunitarians, I'm harvesting news for this month's newsletter. Please send me by the 20th anything you think your fellow community members might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two for the gossip/society column about what you're currently working on. And if you know of a go-live not announced on the list, please be sure to let me know about it. Thanks, Daniel Grobani

1 0

Authorities / cron
by Paul 10 Oct '12

10 Oct '12

Happy Thanksgiving Day to Canadians and good evening to you all; Logging the zebra incrementals, Ubuntu 12.04 seems to be a tad touchy on this subject, so I'm now using user=koha crontab -e for this. I had problems with functionality of recommended envars and had highcoughs for a "user" cron if 'koha' appeared on the exec line: * * * * * koha $KOHA_PATH/bin/migration_tools/rebuild_zebra.pl / ^^^^ -a -b -z -v >> /tmp/cron_koha.log koha@nelson:/tmp$ cat cron_koha.log /bin/sh: 1: koha: not found) but the following gave results: koha@nelson:$ crontab -l KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib * * * * * /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -a -b -z -v >> /tmp/cron_koha.log 2>&1 Question: to tidy up the [warn]s -- does anyone please have any pointers? Here's an extract: Zebra configuration information ================================ Zebra biblio directory = /var/lib/koha/zebradb/biblios Zebra authorities directory = /var/lib/koha/zebradb/authorities Koha directory = /usr/share/koha/intranet/cgi-bin BIBLIONUMBER in : 999$c BIBLIOITEMNUMBER in : 999$d ================================ ==================== exporting authority ==================== Records exported: 0 1. {what is this? not line wrap? Just the first of many lines?} Records exported: 4 ==================== REINDEXING zebra ==================== ==================== exporting biblio ==================== Records exported: 0 1.................. {same? {what is this? not line wrap? Just the first of many lines?}} Records exported: 38 ==================== REINDEXING zebra ==================== 18:13:02-08/10 zebraidx(5501) [warn] Missing attribute 'type' in attribute info 18:13:02-08/10 zebraidx(5501) [warn] Missing attribute 'type' in attribute info 18:13:02-08/10 zebraidx(5501) [warn] Unknown register type: ==================== CLEANING ==================== Thanks and best regards -- Paul

3 3

Ubuntu Koha pakage
by juan hernandez 10 Oct '12

10 Oct '12

is there any Koha-pakage.deb for installing?

3 2

Roles for Koha 3.12
by Mirko 09 Oct '12

09 Oct '12

Dear community, with the start of the release cycle on October 22, work on Koha 3.12 will officially begin. As most of you probably know, there are several roles to be assigned per release and it is time to do that for Koha 3.12. There are some proposals for most of the roles already, they can be found on the Wiki (link below). As of now, we are especially looking forward to proposals for * Quality Assurance (QA) Manager * Release Maintainer for 3.6.x * Meeting chair and we would also like to encourage you to consider volunteering for any other position that sounds attractive and feasible to you. Some positions can and should be filled with more than one person, others positions can also use assistants. It is a nice opportunity to learn more about Koha, help with the development of your favourite free software library system and work together with very friendly people. Please add yourself to the Wiki if you think you would be able to help with any of the positions, feel free to add a proposal that may include everything from information about yourself to your visions for Koha. There will be an IRC meeting (mostly) dedicated to voting for all of these roles. This meeting will be held on october 10, 10+00 UTC. That's right, 10.10., 10 UTC. Even if you won't apply for a role yourself please consider reading the proposals and voting to show your support for the Koha volunteers. For more information about roles and proposals, please visit http://wiki.koha-community.org/wiki/Roles_for_3.12 Information about the IRC meeting: http://wiki.koha-community.org/wiki/General_IRC_meeting,_10_October_2012 Have a nice day, Mirko

1 1

Re: [Koha-devel] [Koha] Current, Simple-to-install, Installed LiveCDs/LiveDVDs are okay ( was Re: Avoid LiveCDs/LiveDVDs)
by Paul 09 Oct '12

09 Oct '12

Moving this to devel rather than users (apologies if anyone feels this should remain in general circulation.) At 05:41 PM 10/6/2012 +0800, Mark Tompsett wrote: [snip] >If it installs easily to a hard drive and let's them have a >packages-based, ... Mark - could you please explain your fixation with "packages-based"? (by which I *think* you mean .deb files -- please correct me if I'm mistaken.) I've been using "packages" for fifty years; they used to come in the post -- a cardboard box of punched cards -- then [t]ape [ar]chives hence 'tar' -- then standardized in the 1980s by IEEE/POSIX. They permit good transmission, particularly with modern compression and checksum techniques, of directory structure, permissions, linking, etc. They're usable in all *nix environments, not just the Debian family, but RHEL, AIX, Solaris, SuSE, BSD ... (even my old favourite Slackware.) A .tar is somewhat universal; .deb, .rpm, are o/s specific. Why limit the scope? Why not concentrate on the best possible quality of an ubiquitous .tar? >that is a good thing for non-technical people with a production environment. Please, how many "production environments" are run by "non-technical people"? (or at least without access to "technical" people?) Is Koha destined for amateurs only? Even my local, rural, very small, public library uses the municipal IT department personnel (they're on SirsiDynix.) [snip] >Chris Cormack wrote: >>Doing 2 LiveCD releases every month is a reasonable amount >>of work so I applaud them for wanting to. > >I agree monthly would be perfect, but even every 6 months (in line with >the new releases 3.10.0, 3.12.0, etc.) would be sufficient (not perfect, >but sufficient). Recognizing that I'm wandering from "live CDs", a Koha LTS should be the goal -- with security updates -- for a two year cycle in a production environment. I, and colleagues from other libraries, don't have policy, budgets or the inclination to play "new releases" every month, probably not even every six months; that's OK for video games, but not when your IT department is responsible for records in the hundreds of thousands (or many millions via Z39.xx standards.) On the other hand, enhancements are a marvelous idea, leading up to a "next LTS", and those of us who have time and the facilities should be encouraged. Such releases can be labeled "latest|whatever", but not "stable." [snip] >Though, current and previous stable releases on a monthly basis are >probably best. Hopefully this clarifies everything from my perspective. :) My knowledge of upgrade 3.6.x. to 3.8.x (12 month period) is a testament as to why an LTS, with more complete QA (or at least full documentation) should be on Koha's horizon (and to pre-empt comments concerning why I should search git and bugs and wiki and INSTALL (all variants deb, ubuntu, bland) and community and devel and users and download and ... I'm sure you understand.) Thanks and best regards - Paul

4 3