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

Social library
by Uy 23 Jun '12

23 Jun '12

Hi everyone! I have worked with Koha for 4 month. I am not a programer, i just know php mysql and html. Love koha and i want to share some ideas with you guys. Hope that some developer get the same ideas and will make it come true. We know now facebook is really famous, and how do you think about the social library? I think, if we have a social library, the patrons will be interested more and more with our library. Let me give you example in my opinion: A patron join into OPAC site, and they will see that in 5 days from his last checkout, how many his friends came to library, what kinds of books they borrowed? It looks like a small wall on facebook. Now i can see that the OPAC when an user login in KOHA is quite sad, i mean there is a very little thing, which can make them stay on our library'site longer! I know that we are working with a library managment system, i can't dream more and more, but i think our student really love it. Thanks for reading, and i love to receive your reply. Kindest Regards! Nguyen Quoc Uy

3 2

Model for wiki JQuery_Library
by Stefano Bargioni 22 Jun '12

22 Jun '12

In http://wiki.koha-community.org/wiki/JQuery_Library#JQuery_Title the proposed model for contributed scripts is Developer: Name of JQuery developer Purpose: Purpose of the JQuery Status: Completed / In progress Intranet or OPAC?: Version: (The version you are using this with, or Any, if applicable) I'd like to suggest some modifications: Developer: Name of JQuery developer Creation Date: the date you entered the script (YYYY-MM-DD) Purpose: Purpose of the JQuery script Status: Completed / In progress Intranet or OPAC?: Version: (The Koha version you are using this with, or Any, if applicable) Thanks. Stefano __________________________________________________ Il tuo 5x1000 al Patronato di San Girolamo della Carita' e' un gesto semplice ma di grande valore. Una tua firma aiutera' i sacerdoti ad essere piu' vicini alle esigenze di tutti noi. Aiutaci a formare sacerdoti e seminaristi provenienti dai 5 continenti indicando nella dichiarazione dei redditi il codice fiscale 97023980580.

2 1

Koha 3.8.2 Released
by Chris Cormack 22 Jun '12

22 Jun '12

The Koha community is proud to release Koha version 3.8.2. This is a bugfix release, and contains a large number of fixes. You can obtain Koha 3.8.2 from the http://download.koha-community.org site. Debian packages will be available from the http://debian.koha-community.org shortly also. Please read the release notes below for more information RELEASE NOTES FOR KOHA 3.8.2 21 Jun 2012 ======================================================================== Koha is the first free and open source software library automation package (ILS). Development is sponsored by libraries of varying types and sizes, volunteers, and support companies from around the world. The website for the Koha project is http://koha-community.org/ Koha 3.8.2 can be downloaded from: http://download.koha-community.org/koha-3.08.02.tar.gz Installation instructions can be found: in the INSTALL files that come in the tarball Koha 3.8.2 is a bugfix/maintenance release. Highlights of 3.8.2 ====================== 8140 blocker Error when exporting label xml 8247 blocker adding basket doesn't save basket name, internal or vendor note 7329 critical The "undo import into catalog" command deletes items onloan without checking 8056 critical CircAutoPrintQuickSlip set to clear doesn't work 8062 critical Cart email broken for non english templates 8135 critical Services Directory and itemrecorddisplay.pl File Missing After Install 8144 critical 775 tag in the MARC record causes display issue 5327 major Unit tests required for all C4 modules 7112 major Having two prices in 020$c causes basket creation to fail from staged marc import 8057 major Error when adding a patron with email address 8082 major The: IssuingInProcess configuration setting is working in reverse. 8145 major opac-tags.pl fails when DEBUG is set 8182 major Problem with overdue fine calculations after upgrade 8201 major can't change receive date Bugs fixed in 3.8.2 ====================== 3638 normal Status of hold not changed when item checked in via SIP2 Interface 4330 normal Copyright statements out of date 4838 normal Repeated authority headings break biblio record data entry form 5795 normal Missing ReservesControlBranch system pref in database installer 6858 normal Adds staticfines.pl for static fines processing 7127 normal Templates must be valid XHTML 7178 normal Improve order item creation 7586 normal Search: Language restriction does NOT show expected results (no items shown) 7599 normal Cart JavaScript contains untranslatable English strings 7810 normal C4/Auth.pm - on plack restart session is undefined 7872 normal C4::Items should use C4::Koha methods instead of duplicating SQL queries 7951 normal Suspending holds needs a system preference 7952 normal PDF::Reuse under plack writes to console STDOUT instead to browser 7961 normal Local cover images should support CSV link files 8005 normal Lost item is not anonymized when checked in 8111 normal Language chooser display problem in self-checkout 8116 normal z3950 empty search causes silent warning in koha-error_log 8124 normal Hide option to download results of items with no checkouts report 8129 normal quick slips issuing does not work 8136 normal Changes the expected lenght of 100$a in rebuild_zebra.pl 8160 normal Link to cataloging appears for users without cataloging permission 8161 normal Cataloging home page should be accessible to users with permission to edit catalog or edit items 8171 normal Improper escaping of quotes during z39.50 queries leads to broken html 8176 normal $sqlwhere is undefined in C4::Serials in GetSubscriptions 8184 normal Duplicate budget page lacks heading and breadcrumbs 8197 normal Software error when you have cleaned cookies in your browser and try to past the url to opac-topissues.pl 8226 normal 'OpacFooter' markup/css improvements 5312 minor XHTML correction in authority summary 6141 minor html glitches causing problems to translator 7815 minor Order pickup library list by name rather than by code 7948 minor Printing transfer slip loses barcode field focus 8009 minor Item descriptive data not populated on pay.pl 8014 minor On the patron entry form hide "restricted until" field if "Restricted: No" is checked 8040 minor a menu misnamed in budgets 8119 minor Show hint when disabling active currency checkbox 8122 minor Add a link to new library group creation from empty groups message 8139 minor Fix the CSS for the recent comments to prevent leftmenu overlapping it. 8150 minor Patron circulation history has a fossil navagation bar 8166 minor Adding new currencies & exchange rates if not fill any field it save blank record 8195 minor The selected link in include menus must be bold 8217 minor Focus on search box in Detail page (staff search) 3521 trivial Items table in catalogue/detail.pl and cataloguing/additem.pl is sorted nonsensically 6267 trivial custom http user-agent in check-url.pl (fix for books.google.com 401 error) 7368 trivial General staff client typo omnibus 8222 trivial The zip code field is mandatory by default 6684 enhancement koha-remove should check the number of arguments it gets 7444 enhancement Use T::T date plugin to display dates omnibus 7788 enhancement Tiny problems with calling GetShelf 7847 enhancement OPAC search dies with plack 7926 enhancement Acq search results show empty parenthesis for orders without basket group 7941 enhancement Fix version numbers in modules and set up a system to keep them up to date 8080 enhancement login and password is pre-filled by the browser when creating a new patron 8107 enhancement Disabled buttons not distinguishable from enabled buttons. 8138 enhancement Add 773$t field to xslt 8178 enhancement circ/circulation.pl under plack duplicates checkout rows New system preferences in 3.8.2 ================================= * ReservesControlBranch * SuspendHoldsIntranet * SuspendHoldsOpac System requirements ====================== Changes since 3.6: * No new system requirements Documentation ====================== As of Koha 3.2, the Koha manual is now maintained in DocBook. The home page for Koha documentation is http://koha-community.org/documentation/ As of the date of these release notes, only the English version of the Koha manual is available: http://manual.koha-community.org/3.8/en/ The Git repository for the Koha manual can be found at http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Translations ====================== Complete or near-complete translations of the OPAC and staff interface are available in this release for the following languages: the following languages: * Chinese -Taiwan- (100%, OPAC 100%) * German (100%, OPAC 100%) * Italian (100%, OPAC 100%) * French (99%, OPAC 100%) * Portuguese (Brazil) (90%, OPAC 100%) * Spanish (87%, OPAC 100%) * English -nz- (78%, OPAC 100%) * Arabic (76%, OPAC 100%) * Danish (75%, OPAC 100%) * Greek (69%, OPAC 100%) * French -canada- (68%, OPAC 70%) * Armenian (68%, OPAC 100%) * Norwegian (67%, OPAC 100%) Partial translations are available for various other languages. The Koha team welcomes additional translations; please see http://wiki.koha-community.org/wiki/Translating_Koha for information about translating Koha, and join the koha-translate list to volunteer: http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate The most up-to-date translations can be found at: http://translate.koha-community.org/ Release Team ====================== The release team for Koha 3.8 is Release Manager: Paul Poulain <paul.poulain(a)biblibre.com> Documentation Manager: Nicole C Engard <nengard(a)gmail.com> Translation Manager: FrÃ©dÃ©ric Demians <frederic(a)tamil.fr> QA Manager: Ian Walls <koha.sekjal(a)gmail.com> QA team: Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl>, Jonathan Druart <jonathan.druart(a)biblibre.com> Bug Wranglers: Katrin Fischer, Magnus Enger Release Maintainer (3.4.x): Chris Nighswonger <cnighswonger(a)foundations.edu> Release Maintainer (3.6.x): Jared Camins-Esakov <jcamins(a)cpbibliography.com> Release Maintainer (3.8.x): Chris Cormack <chrisc(a)catalyst.net.nz> Credits ====================== We thank the following individuals who contributed patches to Koha 3.8.2. 1 D Ruth Bavousett 1 Jared Camins-Esakov 4 Colin Campbell 20 Chris Cormack 4 Christophe Croullebois 1 StÃ©phane Delaune 4 FrÃ©dÃ©ric Demians 4 Jonathan Druart 3 Katrin Fischer 2 Amit Gupta 10 Kyle M Hall 2 Mason James 2 Srdjan Jankovic 1 Piotr Kowalski 12 Owen Leonard 2 Julian Maurice 1 Matthias Meusburger 3 Sophie Meynieux 7 Dobrica Pavlinusic 6 Paul Poulain 1 Liz Rea 3 Marcel de Rooy 1 Fridolyn SOMERS 1 Adrien Saurat 2 Robin Sheat 1 Simon Story 1 Marc Veron 1 Ian Walls We regret any omissions. If a contributor has been inadvertantly missed, please send a patch against these release notes to koha-patches(a)lists.koha-community.org. Revision control notes ====================== The Koha project uses Git for version control. The current development version of Koha can be retrieved by checking out the master branch of git://git.koha-community.org/koha.git The branch for Koha 3.8.x (i.e., this version of Koha and future bugfix releases) is 3.8.x. The next major feature release of Koha will be Koha 3.10.0. Bugs and feature requests ====================== Bug reports and feature requests can be filed at the Koha bug tracker at http://bugs.koha-community.org/ Ehara taku toa i te toa takitahi, engari he toa takitini

2 1

New Koha repository for 3.6 series
by Robin Sheat 21 Jun '12

21 Jun '12

People who are on the debian packages have just had the option of sitting on the real bleeding edge by running packages from master, or just a bit back from it by running the newest stable series (currently 3.8.) This isn't what everyone wants to do however, some people like to be a bit more conservative. For those people, there is now a section of the Koha Debian repository called "oldstable." It will track the koha releases that are stable and supported, but a series behind the most current one. Documentation for how to access it is here: http://wiki.koha-community.org/wiki/Koha_3.8_on_Debian_Squeeze It will keep up with the current supported release, so when 3.10.0 comes out, it will jump to 3.8.6 (or whatever is out at the time.) If you have any issues or questions, please post them here, or report them on bugzilla: http://bugs.koha-community.org/bugzilla3/ -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D

1 0

1 day left to translate for 3.8.2
by Chris Cormack 21 Jun '12

21 Jun '12

Hi all I plan to release 3.8.2 tomorrow nz time, which should give you all about 1 more day to translate as much as you can. Frederic would you be able to send a pull request for the new .po files at the end of your business day tomorrow? Thanks very much Chris

2 1

Acauisition in Koha 3.8.1: Problems
by Partha Mukhopadhyay 21 Jun '12

21 Jun '12

1 0

urgent call for testing!
by Melia Meggs 20 Jun '12

20 Jun '12

Hi Koha developers! We have hundreds of libraries running 3.8.1, and we've come across several show-stopper bugs that are really causing problems for these libraries right now. Here are the major problems that we've come across so far: 1. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8253 All fines are doubling in 3.8.1. 2. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8267 No overdue notices are going out. 3. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8110 Calendar is not honoring closed days. We have submitted patches for all of these problems, and we are making an urgent call for testing to help us get these fixes into 3.8.2 in the next two days if at all possible. Please help us with testing/QA if you can!! Thanks, Melia P.S. Also hearing lots of complaints about this one. It not a show-stopper but is signed off and needs QA as well: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8043 -- Melia Meggs Chief Operations Officer ByWater Solutions bywatersolutions.com *Visit Us At ALA Booth #323*

6 6

Bug 7167 New updatedatabase
by Marcel de Rooy 16 Jun '12

16 Jun '12

Hi all, Patch 7167 has been signed off. I have pasted my QA comment here below to get some feedback from you. Note that this patch will impact your future updates ! My comments are not strictly technical, but also on a functional level. Due to the nature of this patch, I think that I should. Before Paul or Jonathan moves on, you may have some comments. Do you agree with me, or why not? Etc. Thanks a lot.. Marcel QA comment: Larger patch with greater impact. Good work! Code generally looks good. Nice idea. Will make testing patches with dbrevs easier. Because of the impact of this patch, I think that we still need some adjustments before it passes qa. The points below may look like a lot of work, but will not need that much code changes. I believe that it can be done within some hours. (Please note that I would really LIKE to see this feature be pushed soon!) I change status to In Discussion and will ask for input from the dev list. Before you change the patch, it would be good to have some additional community consensus about it (when given). My main (functional) point is actually: make a distinction between numbered dbrevs (from master) and unnumbered dbrevs (from test patches or custom development). An upgrade should always run the numbered dbrevs in linear order. The unnumbered ones can be executed in any order from the new update form if you are in dev mode. This makes a wiki with picking dbrev numbers unneeded. The RM still takes care of the numbering (rename a file). A developer just adds a file without dbrev number in a new patch, perhaps referrring to a bug report. There will be no gaps in the numbering scheme. About lists the correct official Koha version and the applied 'custom' dbrevs. YAML: As I understand, the idea was initially to have dbrevs in a yaml file. In the current implementation, only the version dir is in that file. Additionally, you do not use the dirload, only the fileload. For simplicity, I recommend to remove the YAML file and associated code. The versions directory can be hardcoded in my opinion within the install/data.. region. I would suggest to rename it to dbrev or something similar, and have numbered version subdirectories within it. Example: This will eventually lead to dirs and files like dbrevs/3.09/3.09.00.001.sql or dbrevs/3.10/3.10.02.003.pl, etc. Development mode: Currently, you rely on $ENV{DEBUG} from koha-httpd file. I would turn this into a systempref. It is easier for developers to toggle it (compared to restarting httpd service). Skeleton: I see it in a regex as well as some code inserting into foo. Assume that it was used in testing. Please remove it. In actual use, you will find enough examples to find your way. Or just put some comments into a readme file. Mainpage: Some code was removed from Auth.pm. The version check is now in mainpage.pl itself. I would rather have that check in an appropriate module. It was in Auth.pm. You could leave it there? I think we should let the version check stay within the scope of the checkauth call included in the get_user_and_template call. (See also comment on Auth.pm below). Authorization (Auth.pm): I agree that if a user already logged in, it is not needed to check the version every time. The ("new") initial check in checkauth if the db contains a version, is fine. The former moment of the "complete" version check was too early. I think we should leave it in checkauth, but do it at a later moment: If we start a new session and we verified the password, then we should do the extended version check (database versus kohaversion.pl). That is close to line 748 in the adjusted Auth.pm (depending on the value of $return). This will prevent Koha from checking it every time, but only for a new session. If the version check fails at that moment, we should redirect to installer step 3 (updatestructure). Note that there is some problem in current code, that forces me to login twice when there is an update available. (It redirects to admin/updatedatabase, but I must relogin again.) Please correct. Probably you should only pass the $cookie in your redirect call too. Like: print $query->redirect(-uri=>"/cgi-bin/koha/admin/updatedatabase.pl",-cookie=>$cookie); Upgrading: When coming from an older version (before 3.9.0.x), you should run the old updatedatabase and after that you should run the new dbrevs in the dbrev directories. This is currently done in two passes. First it runs the old update. You think that it is ready. When you login, you are prompted to the new update form. It should not be too difficult to merge this into one pass (less confusing). Please adjust install.pl for that: You should check if it is still needed to call the old update before running the new one (for numbered dbrevs only). Update form: Since numbered dbrevs are run via installer, only allow executing unnumbered dbrevs here (in dev mode). In normal mode, you can only browse history here. (I would suggest to not even show the unnumbered dbrevs if you are in normal mode.) File structure: As mentioned above, make directories for a Koha release. Getting all updates means fetching the updates from a few directories. This makes the feature more future-proof. Stable version: The md5 test will be of good use here! If we backport this to 3.8.X, we could already check what updates we already have run from 3.9 folder with the md5 checksum. When upgrading from 3.8 to 3.10, some dbrevs are new, others will be incorporated already. So this remark only serves the purpose of discussing "Should we also get this into stable already (within reasonable time)?". admin/updatedatabase.pl: Line 33 adds a fixme to new code: Add a new flag? Commit message: please make it up-to-date. E.g. section on installdir.

6 6

Call for News for the June Newsletter (especially re KohaCon12!)
by Daniel Grobani 15 Jun '12

15 Jun '12

Dear Koha Kommunitarians, I'm harvesting news for the June newsletter. Please send me by the 25th anything you think your fellow community members might like to know about. I'm particularly interested in accounts of happenings at KohaCon12. "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

using CHI directly to use all of it's advantages
by Dobrica Pavlinusic 15 Jun '12

15 Jun '12

As some of you allready know, Jonathan Swartz had presentation about CHI: Universal caching for Perl at YAPC::NA. Video recording is available at: http://ics.webcast.uwex.edu/mediasite/Viewer/?peid=b503ecb42c18452a9f4a95b7… It got me thinking about our new Koha::Cache layer. For a start, I would love to use CHI directly and make it required depenency for Koha since it has following features which we already use: - memcached back-end - making our own memcache implementation obsolete - fastmmap back-end - ditto - DBI cache - making mysql query cache problem solvable way than DBD::Goper suggestion from http://wiki.koha-community.org/wiki/Performance#MySQL_tuning - memoize - very nice syntax: my $customer2 = $cache->compute($name2, "10 minutes", sub { get_customer_from_db($name2) }); Which I would prefer to our existing Koha::Cache API. It would also save us quite a bit of code. CHI has powerfull statistics which basically obsolete my idea of writing statistics gathering code through Koha. I would love to have this in next release, since this is more-or-less my last major gripe with current Koha code (short-term goal[1]), so if I would love to hear feedback. 1: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7177 My more long-term goal is to know more about Koha's data-access patterns (you are again advised to examine performance wiki page if you haven't up to this point). In most simple sense, only think which is big unknown is wheater we can find sane key namespace schema which will allow us to good-enough cache invalidation scheme. I strongly think that time-outs are useful just for OPAC, not for intranet use! It seems to me that CHI redis back-end (which can introspect keyspace with keys *) and my "weekly push master in production because of plack" approach might bring us to better understanding how our Model layer might look like, allmost like reverse engeeniring existing code access patterns which has proven to bring a lot of low-hanging fruits so far. Only disadvantage I can think of is that CHI isn't packaged in stable Debian but it is in wheezy so Robin would not need to package it forever, just for little while :-) -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

5 6