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

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

OPAC themes
by Owen Leonard 09 Oct '12

09 Oct '12

The new CCSR theme which will be included in 3.10 demonstrates how a theme can be made responsive, so that the design and layout of a page can change depending on the device width. I think the "default" Koha OPAC should use this technique too. Making this kind of change gives us the opportunity to make other changes too, and I'd love to hear from others about what changes those might be, whether they be ideas about the design, layout, or structure. Some ideas off the top of my head: - Use the Bootstrap framework both for the responsive CSS grid and for the interface widgets (buttons, menus, etc)--but not be slavish to the default Bootstrap design. - Use consistent indentation rules on all templates - Move JavaScript to the bottom of the page (recommended for efficiency) - Address the needs of people who want to do customization via CSS and JavaScript. To that end I'd love to hear from the people who are doing customizations for libraries about their paint points--what aspects of the OPAC are difficult to change. I'd like to start working on this, but I think to do it right I think we need some shared goals. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

9 14

Javascript Properties in Basket.js
by David Cook 09 Oct '12

09 Oct '12

In several functions (such as writeCookie function) in Basket.js (both for the OPAC and the Intranet), the cookie is handled by using "parent.opener.document.cookie" or "parent.document.cookie". Does anyone know why we need to include the parent and opener properties? In the case of opener, I can see that the idea is that we're trying to reference the main browser window from the pop-up window. However, this doesn't seem necessary. From my tests, "document.cookie" does the trick just fine without any reference. Note: The reason for trying "document.cookie" on its own is because "parent.opener.document.cookie" and "parent.document.cookie" don't work when embedding the OPAC in an iframe on a separate domain. As for the "parent" property, this seems completely unnecessary. In the case of "parent.document.cookie", the script should be running from the main browser window. In the case of "parent.opener.document.cookie", the "opener" property would be referencing the main browser window from the pop-up, so there would be no need for parent. Tests show that "document.cookie" works fine for adding and removing items from the cart. However, we wanted to check to see if anyone knew why "parent/parent.opener" had to stay or if this would create other issues. -David Cook

1 0

Default search options in the OPAC
by Owen Leonard 08 Oct '12

08 Oct '12

We've now got two patches pending which seek to add more options to the default OPAC search, the masthead search bar which currently includes options for Library catalog, title, author, subject, ISBN, series, and call number: Add "Phrase" Searching to OPAC Search http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8778 Add accesssion [barcode] number to the drop down list in OPAC Search http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8302 I'll say right out that I'm opposed to these changes, but I want to bring it up here on the list so we can discuss. I think the default search options which appear in this space need to be limited and simple. I come from the point of view of public libraries, so my goal is to make it easy for someone to walk up to the OPAC and start searching. In my opinion these options should be available only on the advanced search page. My concern is that when we add some of these more complex options we're catering not to the public but to librarians using the OPAC, and I think those librarians' needs are not our primary focus in this interface. I also think that our search system needs to be so good that keyword + relevance wins over specific searches like "title phrase." That said, I'm aware that the public library is only one of many types of libraries, and that other libraries have different needs. Are these needs varied enough that we need to build an interface in the staff client for selecting which search options are shown in the OPAC? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

8 15

Koha doubt
by PRASANTH M.P. 08 Oct '12

08 Oct '12

Dear All, Please check any way to include subscription fee details in circulation rules.I am public library librarian in our library affiliated with kerala state library council ,council rules every library must collect subscription fees from members,but in koha no filed to enter the subscription fees.Please solve the issue. Regards Prasanth M.P. Ph:09961858865

1 0