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

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

HOw Koha does it works?
by john23 05 Oct '12

05 Oct '12

well its a general question but, I would like to know how is integrated with zebra?, how make the searches and search in the tables? how insert each item in the catalog module? I hope someone could answer.... greettings -- View this message in context: http://koha.1045719.n5.nabble.com/HOw-Koha-does-it-works-tp5728918.html Sent from the Koha-devel mailing list archive at Nabble.com.

2 1

Is Manage Patron Image is missing in version 3.08?
by Waqar Azeem 05 Oct '12

05 Oct '12

I am trying to replace my v3.04 to v3.08 Patron image upload (Manage Patron Image) is missing from the main Patron page. http://i.imgur.com/l5oK6.png Do i need to enable some configuration or it simply have been removed? Uploading image for an individual is quite cumbersome from: Tools › Upload patron images -- Thanks & Best Regards, Waqar Azeem

2 2

Koha packages for master
by Robin Sheat 04 Oct '12

04 Oct '12

The packages for master have been lagging for some time now, as dependencies were introduced that didn't have packages. This evening I started to fix this, however ran in to a problem: Data::Pagination has no copyright information, therefore it's dubious as to whether we should be using it, and I'm reluctant to distribute it. I've asked for clarification on this: https://rt.cpan.org/Public/Bug/Display.html?id=80000 however it means that packages for master will have to wait a while, until this is sorted. We should be more careful about our dependencies and whether we're allowed to distribute them. (Note: I'm 99.99% certain it'll be fine, it's just that only the author can really make that call for sure.) -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D

2 3

A new open source project on Drupal related to sigb (and so koha)
by Claire Hernandez 04 Oct '12

04 Oct '12

Hello, I am pleased to announce that we contributed a new drupal module called opac: http://drupal.org/project/opac Announcement is here: http://drupal.biblibre.com/en/blog/entry/biblibre-contributes-the-drupal-op… evolves a lot but you can begin to test it and give us feedbacks :) The first sigb we connected is, of course, koha. It is an other way to provide opac and others things around, it is and independant full project related to whatever sigb you want. I would like to introduce a difficulty we encounted: we wanted to build on top of Ils-di but not everything can be done with it (and we found some bugs). We wonder how to expose koha services to build a significant drupal site. Ncip2 is not sufficient for us, so we've made a choice. For the moment, we are building a Koha::REST interface. The project is published http://git.biblibre.com/?p=koha-restful;a=summary but not yet submitted to the community. You can have a look and tell us what you think. If you want to send us patches, please do it, if you prefer I could clone it in github but the risk is that the project wont be up to date everyday. Regards, Claire.

5 5

dselect non-funcitonal on Ubuntu
by Tomas Cohen Arazi 04 Oct '12

04 Oct '12

This simple test probes dselect is currently broken on Ubuntu amd64 12.04/10.04 (as root): $ echo "apache2 install" | dpkg --set-selections $ dselect install Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: gcc-4.6-base:i386 libasn1-8-heimdal:i386 libc6:i386 libcap2:i386 libcomerr2:i386 libdb5.1:i386 libexpat1:i386 libgcc1:i386 libgcrypt11:i386 libgnutls26:i386 libgpg-error0:i386 libgssapi3-heimdal:i386 libhcrypto4-heimdal:i386 libheimbase1-heimdal:i386 libheimntlm0-heimdal:i386 libhx509-5-heimdal:i386 libkrb5-26-heimdal:i386 libldap-2.4-2:i386 libp11-kit0:i386 libpcre3:i386 libroken18-heimdal:i386 libsasl2-2:i386 libsasl2-modules:i386 libsqlite3-0:i386 libssl1.0.0:i386 libtasn1-3:i386 libuuid1:i386 libwind0-heimdal:i386 zlib1g:i386 0 upgraded, 29 newly installed, 0 to remove and 0 not upgraded. Need to get 8,500 kB of archives. After this operation, 22.2 MB of additional disk space will be used. Do you want to continue [Y/n]? So I propose the removal of dselect usage from the docs and use of simple apt-get commands (perhaps providing a convenient script). Regards To+

9 27

Re: [Koha-devel] Cataloguing authorities 3.6/3.8
by Paul 02 Oct '12

02 Oct '12

At 10:22 AM 10/1/2012 +1300, Robin Sheat wrote: >Paul schreef op za 29-09-2012 om 17:54 [-0400]: > > 17:32:00-29/09 zebraidx(2632) [warn] isamb: Inconsistent register (2) > > zebraidx: isamb.c:1102: insert_leaf: Assertion `*lookahead_mode' > > failed. > > 17:32:00-29/09 zebraidx(2637) [warn] previous transaction didn't reach > > commit > > > > that are "novel." > > > > Any suggestions, thoughts? > >Those errors are really annoying. > >Have a look to see if there's something funny about the MARC for biblio >17765. Especially missing 999$c and $d (I think.) I've been following up on on Robin's suggestion looking for "something funny" in our records that might explain current indexing (or at least reassure me that it's not a db rather than system error) and wrote a script to verify our inhouse barcodes: mysql> select items.barcode, items.biblionumber, biblio.title, biblio.author, items.itemcallnumber from items join biblio on (items.biblionumber = biblio.biblionumber) where items.barcode NOT REGEXP '^[[:digit:]]{1}[[:alnum:]]{4}[[:digit:]]{8}$'; +------------------+--------------+----------------------+-------------------------+----------------+ | barcode | biblionumber | title | author | itemcallnumber | +------------------+--------------+----------------------+-------------------------+----------------+ | 1AERO9107_221230 | 16603 | Heroes of the air, | Fraser, Chelsea Curtis, | AERO-FRAS-1 | | 1AERO111564 | 17408 | Fights and flights / | Samson, Charles Rumney, | AERO-SAMS-1 | +------------------+--------------+----------------------+-------------------------+----------------+ 2 rows in set (0.02 sec) However, these are totally unfindable in Koha (by barcode, biblionumber, callnumber, etc) via any type of search (normal, advanced etc) [N.B. we have these two items under a different biblio, call, barcode, all valid and searchable.] But, I can use 'Tools ==> Export bibliographic and holdings' and produce what appear to be perfectly valid Marc21 records Could these 2 be (I'm wildly guessing) the reason for the "[warn] isamb: Inconsistent register (2)"? Does anyone have a ready made method to delete a complete record in Mysql? They're unwanted elements -- but how to remove them? tnx and br -- paul

2 1