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

Testers wanted: New OPAC theme based on Bootstrap
by Owen Leonard 03 Jul '13

03 Jul '13

As many of you know, I have been working on a new theme for the OPAC based on the Bootstrap framework. The design is based primarily on CCSR. My goal is to have a theme that feels more modern, is fully-responsive, and which is maintains all the functionality of the current prog theme. I have a branch up on Gitorious, and I would love to get some feedback: http://gitorious.org/koha-dev/koha-dev The branch is called "bootstrap-opac." Select the "bootstrap" theme once you have it checked out. The theme has come a long way since I last posted screenshots, with lots of work on the responsive aspect of it. Not everything is perfect, but I think it's in a good state to get some other eyes on it. Thanks, Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

1 0

QA: Passed QA queue
by Marcel de Rooy 03 Jul '13

03 Jul '13

Hi Galen, Saw this note from Paul on bug 7167. Probably, your answer may be of interest to more people. We can all see 40 patches in that queue, but we do not know your strategy in handling them (apart from the fact that it is different from that of former RMs). But I could have missed something :) Thanks! Marcel ________________________________________ Van: bugzilla-daemon(a)bugs.koha-community.org [bugzilla-daemon(a)bugs.koha-community.org] Verzonden: dinsdag 2 juli 2013 11:48 Aan: Marcel de Rooy Onderwerp: [Bug 7167] updatedatabase improvements http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167 --- Comment #244 from Paul Poulain <paul.poulain(a)biblibre.com> --- Galen, did you forget this patch ? Any other comment ? -- You are receiving this mail because: You are on the CC list for the bug.

4 5

3.14 RM update #1 posted
by Galen Charlton 03 Jul '13

03 Jul '13

Hi, I've posted my first formal update to the Koha community at: http://koha-community.org/koha-3-14-release-managers-update-1/ I won't copy and paste the whole thing here, but if there is anything that might make future updates more useful, please let me know. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

1 0

Linux server with some spare cpu cycles?
by Chris Cormack 03 Jul '13

03 Jul '13

Hi All As you know we run jenkins for our integration testing, what you might not know is a lot of the jobs used to run on a my server at home as a node. This server is dead, and the disks are on my desk, so this is a call for anyone who has a server that they wouldnt mind letting jenkins use as a node. Basically it just needs ssh access, and java on the machine, it installs pretty much everything else. Any offers? Chris

2 1

SQL files and transaltion
by Zeno Tajoli 02 Jul '13

02 Jul '13

Hi to all, I now that there bugs in develop about a new method to translate MySQL setup and MARC21/Unimarc sql definitions. But, for paid user, i need to create a full italian MySQl setup for 3.12. And I also need to create a full italian MARC21 sql configuration. So, in you opinion what is the best option for Koha comunity ? My plan is: a)I prepare and send patches to translate the present MySQL setup in master and 3.12 but not for MARC21 translation. I think to use two different bug number, one for master update and an other for 3.12 update. Is it OK ? b)About MARC21 translation, I wait and I help in testing the code. I think that the new translation workflow for MARC21 will be present in 3.14. But I can change my plan. 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 2

Old bugs to check
by MJ Ray 01 Jul '13

01 Jul '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. Please leave your reply on the bug web page - I might not see replies to this mail. Ideally, tell irc.oftc.net #koha know that you're looking at a bug. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6456 Display of barcode in search result in staff client http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6122 Catalogue reports exclude biblio without item http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6624 Allow Koha to use the new read API from OpenLibrary http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6301 super librarians can't export bib records from all libraries if indybranches on http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6421 ability to have different opac styles for different libraries 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=5535 users tags not appearing until approved http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5404 C4::Koha::subfield_is_koha_internal_p no longer serves a purpose http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5594 default sort order for items on bib records http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2389 overdue_notices.pl needs a test mode http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5784 link to acq from budgets & funds http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5273 Publication Details for serial subscriptions not showing when in item record edit http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5985 Incorrect date in budgets and failed to edit funds children http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5986 Inconsistent handling of patron deletion permission http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3162 Authority subfileds definitions and Show/Show Collapsed/Hide option http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5920 remove html from downloaded reports http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6605 Store Patron Reading History separate from issues/old_issues http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5576 Access Koha via SSL http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6223 Patron categories should have a default set of permissions -- 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

June 2013 Koha Community Newsletter has been published
by Daniel Grobani 28 Jun '13

28 Jun '13

Hi, The June 2013 edition of the Koha Community Newsletter has been posted to http://koha-community.org/koha-community-newsletter-june-2013/. Cheers, Daniel Grobani Koha Community Newsletter Editor

1 0

RFC: Convergence
by Tomas Cohen Arazi 28 Jun '13

28 Jun '13

I've been thinking and sharing with some an idea I want to share with all of you. Since I stepped into Koha's world I've been focused (sometimes obsessively, I should admit) on the user POV. Specifically on the ways to deploy, maintain and finally use koha. We are now encouraging people to use the packages, and the way of using/deploying Koha has been slowly diverging from the tarball/git and packages setup. Also, the QA process itself takes both approaches appart. Think of the tarball installing DOM as default and packages not even supporting it as an example of what I mean. Think of memcached support, and so on. Once something is pushed, there has to be a 'packages version' for that: twice the work for everyone! We have reached a point at which we have a really nice set of daily maintainance tools: the koha-* scripts, and a sound install schema that supports multiple instances. Or a single default one if we built a 'koha' package that automates its creation, which I think is WIP right now. My proposal is that koha-* commands shouldn't be Debian (.deb) specific. And make the install schema used for packages the default/standard on git/tarball install. The same should happen to multiple instances setups. Both the users and devs should benefit from such a move. Thanks for your constructive comments on the subject! Regards To+ P.S. I belive this is a mid/long term discussion, I'm no way trying to make any sudden move. I just belive this is the way to have the time for a needed planification.

3 5

zebra / adding a search
by Samuel Desseaux 27 Jun '13

27 Jun '13

Hi, My colleagues would like to make some searchs based on the following field (940$a). How can i add it in Zebra and can i add this search in the search options (with a jquery for example)? Many thanks Samuel

1 0

QA: Language material in install/mysql/data
by Marcel de Rooy 26 Jun '13

26 Jun '13

Hi QA team, TM and RM, and other devs: A question on patches dealing with language dependent files in subdirs of installer/data/mysql, including sample notices, frameworks and lots of smaller stuff. With 9 language folders here, it seems to me that we should not demand developers to edit files in all these subdirectories too. Note also that lots of things there need to be translated too. Currently, there are already lots of differences between those language folders; in some language folders system prefs e.g. get specific values. And I suspect that some are being maintained more actively than others. A good improvement recently was the approach for systempreferences. They are inserted with the general sysprefs.sql in the root folder, and optionally updated by a translation in the language folder. So the pref comes always in, translation depending on others. (I think we should extend that approach to the other files now: insert in English, only update translatable things in the other languages. Example: only update name, title and content for a notice, only liblibrarian and libopac for frameworks, etc. ) For some folders there are already 'informal' maintainers. Couldn't we just formalize that someone can step forward to maintain such a folder and let devs just propose changes to the general files and/or the en-folder ? In QA we would no longer allow a patch to make changes in the other languages. Thanks for considering this. Marcel PS I wrote a patch myself recently with a sample notice (only for English). I do not like to add this English in all the language files. I was looking now at bug 9921 too; I think it should not touch all these frameworks. Lots of other examples can easily be found on BZ.

3 3