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

How to get CAS based Single Sign On working?
by Koustubha Kale 25 May '15

25 May '15

Hi All, I have a situation where we have a main website based on Joomla. This Joomla site uses CAS to authenticate users. We would like users ( who have already logged in to the Joomla site via CAS) to be able to follow a link to Koha site and be logged in automatically ( e.g. Single Sign On ). I have got simple CAS ( not proxy CAS ) working with Koha ( version 3.2.6 ) using the same CAS server as used by Joomla site. Still when I login to Joomla site with CAS, and then go to Koha and click on login and follow the CAS login link, I am asked to fill up CAS login information again. How can this be avoided by using CAS SSO? I have read through http://wiki.koha-community.org/wiki/SSO_CAS_improvements and am confused by the statement "Note: simple sso cas support (no proxy) has been done already by biblibre, is in testing and should be released in Koha 3.2" in there. Does this statement mean that SSO is possible with simple CAS? If yes how to set it up? If not, I have also read through bugs 6012, 5630 and the CAS Proxy examples. Frankly I haven't been able to figure out how I can achieve the above required functionality based on all the reading. Any help is much appreciated.. Another related query is, Is it possible to automatically create users in Koha once they have authenticated with CAS? Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

3 3

koha-3.00.00 make fails
by Rick Welykochy 28 Dec '13

28 Dec '13

Hi all, I have downloaded http://download.koha.org/koha-3.00.00.tar.gz and began installing it on Debian/etch (in a Linux vserver environment). 0. FINE: cd koha-3.00.00 1. FINE: perl Makefile.PL 2. FAIL: make : : : Manifying blib/man3/C4::UploadedFile.3pm Manifying blib/man3/C4::BackgroundJob.3pm Manifying blib/man3/opac::opac-dictionary.3pm Manifying blib/man3/serials::member-search.3pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" fix-perl-path.PL blib /usr/bin/perl "-Iblib/arch" "-Iblib/lib" rewrite-config.PL blib/KOHA_CONF_DIR/koha-conf.xml Bad arg length for Socket::inet_ntoa, length is 0, should be 4 at rewrite-config.PL line 67. make: *** [blib/KOHA_CONF_DIR/koha-conf.xml] Error 255 Any ideas what went wrong and how to fix? Aside: there were a couple of other problems with this "out of the box" debian based install of Koha 3.0 which had to be fixed along the way, e.g. seven missing perl modules and libgd not found. I'll report on the entire process from unpacking to a running Koha/3.00.00 once I get to the end. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

4 5

"Damaged" values
by Paul 09 Jan '13

09 Jan '13

In our "Authorized values" > "Damaged", we have added a term "Normal wear" to the Koha defaults 0, 1 and 2: 0 Not damaged Not damaged 1 Damaged Some damage noted 2 Unknown Condition not stated 3 Normal wear Normal wear However, in both staff interface and OPAC, "normal wear" items are appearing as damaged I assume (maybe incorrectly) that the value of "damaged" is read by detail.pl starting line 196: if ($item->{damaged}) { $item->{itemdamagedloop} = GetAuthorisedValues($authvalcode_items_damaged, $item->{damaged}) if $authvalcode_items_damaged; } and then passed to detail.tt start line 310: [% IF ( itemloo.damaged ) %] [% IF ( itemloo.itemdamagedloop ) %] [% FOREACH itemdamagedloo IN itemloo.itemdamagedloop %] [% IF ( itemdamagedloo.selected ) %] <span class="dmg">[% itemdamagedloo.lib %]</span> [% END %] [% END %] [% ELSE %] <span class="dmg">Damaged</span> [% END %] [% END %] I have no experience with this type of 'loo' and 'loop' coding, but it seems to me that "normal wear" is not being picked up, and therefore the ELSE default "Damaged" is being used. Could some kind person please point me to the logic of these loops? Either a brief explanation here (preferred) or a pointer to a tutorial (I have googled with no success.) Or is there something more intrinsic|relevant to the use of authorized values for "damaged"? Bugs [3637] and 5797 may be germane. Many thanks, Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://UltraMarine.ca>, <http://AandC.org> and <http://MarDoc.ca>

2 2

Re: [Koha-devel] combining and minification of javascript and css
by Paul 26 Sep '12

26 Sep '12

At 08:36 PM 4/7/2012 -0400, Chris Nighswonger wrote: >On Sat, Apr 7, 2012 at 6:02 PM, Dobrica Pavlinusic <dpavlin(a)rot13.org> wrote: >I would like to address this one as part of performance work. >[snip] >Minification alone doesn't buy us much: > >OPAC search: >minify js 334974 -> 311553 93.01% >minify css 148277 -> 133128 89.78% > >intranet search: >minify js 382102 -> 362172 94.78% >minify css 134754 -> 123771 91.85% > >But combining JS and CSS files together saves us round-trips to server: > >OPAC 32 -> 20 requests >intranet 27 -> 13 requests Has anyone tried using "page speed v1.12" (the google add-on to bugzilla) which although designed for chrome will work with firefox? Google seem to be quite keen on the 'minify' principle (see <http://code.google.com/p/minify/>.) It has started pushing me towards looking at various combinations of 'minify' (in itself not a great saver, as stated above, as it seems just to remove white space and comments then unify logic on a single line basis), 'combination' (which might have limits with the variety of somewhat older browsers) and x-cache which has advantages, but only in a stable environment -- try changing a favicon ;={ First thoughts from my end seem to point towards combining (css files separately from js at this point in time) into what's needed to display the page ("instant gui gratification") and what can be slightly delayed ("page functions") and getting the download server==>client in the correct order. Best - Paul

3 2

Koha 3.8.0 Released
by Chris Cormack 07 Aug '12

07 Aug '12

The Koha release team is happy to announce the release of Koha 3.8.0, the third major release since we shifted to time based releases. The release team would like to thank everyone involved in this release for making it possible. Koha 3.8.0 contains over 130 enhancements with over 1000 changesets from 71 developers. Please read the release notes below the fold for more information. Koha 3.8.0 can be downloaded from download.koha-community.org or directly at http://download.koha-community.org/koha-3.8.0.tar.gz Chris Release Notes ================== 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.0 can be downloaded from: http://download.koha-community.org/koha-3.8.0.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation OR in the INSTALL files that come in the tarball Koha 3.8.0 is a major feature release, that comes with a lot of new features, and many tweaks to improve performance. Those tweaks are usually not activated by default when you install Koha. If you're upgrading, they are not activated. Go the the "PERFORMANCE" chapter to see all of those improvements, and how to activate them. NEW FEATURES ========== There are 130+ enhancements in Koha 3.8. Some of them are minor, some are major. The list is given below. The number in () is the bugzilla number ( http://bugs.koha-community.org) The "IMPORTANT" flag before an enhancement description means it's a totally new feature, or a major improvement of an existing one, or a change that you should be warned, because you'll spot it in your daily use of Koha CATALOGUE and CATALOGUING * IMPORTANT Add ability to take book cover images from local img db (1633) This feature let you attach images to bibliographic records, that can be cover images or any kind of image * Delete biblios if deleting all their items in batch deletion (6027) When you do batch deletion, you can check a checkbox to automatically delete biblios that have no more items attached. The previous behaviour is still there (do not delete the biblio), and the checkbox not checked by default * Choose framework on Merge (6210) When you merge 2 bibliographic records, you can choose the framework of the merged record * Attach/move items - adding option "try again" after success or wrong barcode (6323) * Enhanced Workflow for adding analytical records (6831) In cataloguing after searching for the parent record the new tool bar option 'add child' takes you into the addbiblio screen but with the Host Item Tag already populated with data derived from the parent record * Adding invoice number and vendor name to the moredetail page (7235) When a biblio is created through an acquisition order, the vendor name and invoice number is displayed, and linked to the order * In the items table, make items.materials of type text, and show its contents at circulation (7278) The note in the item field mapped to items.materials will show up in a message box when checking the item in or out. * New call number allocation plugin (7458) When you activate this new plugin (callnumber-KU), the callnumber has the following behaviour: FREN 0 (then click on ...) - FREN 0000 is returned FREN 0 (then click on ...) - FREN 0001 is returned (the first unused value beginning with this prefix) FREN 01 (then click on ...) - FREN 0100 is returned FEAT AM (then click on ...) - FEAT AM01 is returned FEAT AM (then click on ...) - FEAT AM02 is returned * Create index for items.itemcallnumber (7509) This index speed up a lot the shelves browsing feature * OCLC Connexion Gateway, including extension svc/import_bib (7613) * Add auto-completion on auth_finder (7400) * 5 icons have been added to bridge itemtype icon theme (7373) * A minor change in the “GetMarcAuthors” function of C4/Biblio.pm would allow differentiate the type of authors in the templates (4376) * Add search links in detail pages (6120) * IMPORTANT Authority matching improvements (7284) Implemented new C4::Linker functionality to make it possible to easily add custom authority linker algorithms. Currently available linker options are: * Default: retains the current behavior of only creating links when there is an exact match to one and only one authority record; if the 'broader_headings' option is enabled, it will try to link to headings to authority records for broader headings by removing subfields from the end of the heading (NOTE: test the results before enabling broader_headings in a production system because its usefulness is very much dependent on individual sites' authority files) * First Match: based on Default, creates a link to the *first* authority record that matches a given heading, even if there is more than one authority record that matches * Last Match: based on Default, creates a link to the *last* authority record that matches a given heading, even if there is more than one record that matches OPAC * IMPORTANT XSLT systempreference should take a path to file rather than YesNo (4032) You can now display biblio detail and search results using a XSLT taken from a file. It means you can have a XSLT that is independant from the one provided by Koha. You can still choose to display using normal mode or the default XSLT provided * Add ID attribute to certain areas of OPAC so jquery can be used to hide them (4819) * IMPORTANT Star ratings in the opac (5668) You can now activate (through a system preference) local rating in the OPAC. Logged-in users can rate any biblio * IMPORTANT Display information about library on OPAC detail (7264) In libraries administration, there is a new field that, if filled, is displayed on the OPAC when the patron put his mouse over library name. This can be used to enter library opening hours, address,... * System preference to configure export options for OPAC detail page (7392) The new system preference allows to give a list of | separated values to define, which download options are offered in OPAC. You can choose between BIBTEX (bibtex), Dublin Core (dc), MARCXML (marcxml), MARC-8 encoded MARC (marc8), Unicode/UTF-8 encoded MARC (utf8), Unicode/UTF-8 encoded MARC without local use (9xx, x9x, xx9) fields and subfields (marcstd), MODS and RIS * Add ISSN to SearchForTitleIn (7576) The placeholder {ISSN} is now available in SearchForTitleIn systempreference (as title, author, isbn were previously) * Introduce sys pref to control 'browse results' in OPAC (7935) A system preference has been added to activate or desactivate the "browse result" feature (that let you move to the next/previous record when you've made a search) * "Add to Cart" changes to "Remove from Cart" when a record already in the cart is checked (3215) * comments shouldn't show patron's full name (5503) * Babeltheque integration (7470) Babeltheque is a french provider for enhanced content (comments, reviews,...). The basic support available in previous versions has been improved a lot. * social networks links (7470) You can activate a system preference that will display Facebook 'I like', google+ '+1', linkedIn and some other social networks links. (Note that the system preference OPACBaseURL must be filled in order to have this feature working correctly) ACQUISITION * Linking suggestions & orders (5346) You can now jump from a suggestion to the order placed or from the order to the suggestion it comes from * IMPORTANT keep track of cancelled orders (5358) When you cancel an order, it does not disappear, but is displayed in a table below the other orders * Create new budget from a copy of a previous budget (6943) * Claim notice in acquisitions is now using the message queue (7103) * Claims/Late orders in acquisitions give feedback (7104) * Modify order notes when basket is closed (7166) When a basket is closed, you still can update an order notes. This will let you, for example, add a comment about a delay for delivery * Change booksellers search results display (7169) The page displayed when you search for a bookseller has been changed a lot for a better readability * edition statement field (7289) The edition statement field has been added to the order form * IMPORTANT claims management improvement (5347) When you claim a late order, the date of the last claim and the total number of claims is now saved and displayed * IMPORTANT new fields in vendor table (7293 and 7291) There is now a field to store the common delivery time. It is used to calculate estimated delivery when placing an order, and displayed in acquisition claims. There is also a field containing the library customer number at the vendor * IMPORTANT display suggestions from librarian library only by default (7300) By default, the librarian sees only the suggestions placed by patrons from his library * Add default date limit to acquisitions histsearch (7301) * Suggestion show page (7577) There is now a page to display a suggestion, that is used when jumping from order to suggestion * Use of date filters on bookseller pages (7737) * When adding Vendor default to active currencies (4161) PATRONS * The patron password is masked as it is entered (5280) * Display Organisation and Parent Organisation names when viewing a borrower of type organisation (6303) * Link in readingrec.pl to export a barcode file (6751) * A system preference has been added to renew membership from expiry date or from current date (6843) * Clean up interface on fine payment screens (7080) * IMPORTANT Group borrower attributes and link between patron category and attribute (7154) In patron extended attributes, you can now: - group patron attributes, in a PA_GROUP authorised value list. - select a patron category for a give attribute. If you choose one, only patrons of this category will have this attribute available and displayed * IMPORTANT Add ability search borrowers only on email / phone (7544) In patron search, you can choose on which field you're doing your search: - standard (the default option, the previous one : search on patron card, then name+surname) - email - borrowernumber (Koha internal number) - phone * Custom field removal from patron entry screens (6190) The systempreference BorrowerUnwantedField (same format as BorrowerMandatoryField) implement a mechanism for removing unwanted fields from the entry screens SERIALS * Partial duplication of a subscription (5354) A syspref has been added that you can use to define fields that should not be duplicated when you duplicate a subscription * Add a 1/4 month frequency (6321) * The hardcoded routing list note is now a system preference (7557) CIRCULATION * IMPORTANT Hourly loans (5549) issuing rules can now be defined in hour unit, enabling daily/hourly loans * Make fields from issues table available in overdues (5607) * IMPRTANT Offline circulation improvements : Firefox plugin, and upload all files, apply at once (5877) You can download a Firefox plugin ( https://addons.mozilla.org/fr/firefox/addon/koct/) that will let you do offline circulation when your network is down. When the network is back, you can upload all KOCT files from your circulation desks, and apply all of them at once. * Adds staticfines.pl for static fines processing (6858) This script let you define static fine like "when the patron is late, set a fixed fine of 1€ for each book late" * IMPORTANT User Configurable Slips (7001) - Slips and checkout reciepts are now driven under the notices editor. - The Notice for a given event can be defined for all libraries, or library by library - You can define a CSS to format the notices (see systempreferences) * Floating collection (7144) Adds support for Floating Collections (i.e. items that don't automatically return home when checked in at another branch) on a per branchcode/itemtype basis. * Display of issue number for serials in overdues (7434) * Printing Transfer Slips for checkin items that do not have holds but need transfer (7467) * Display fine amount and make payment link during checkin (7566) * add columns to overdues export (4051) * Double-clicking the 'place hold' button can result in duplicate holds (4054) * Suspension of holds (7641) Users are now able to place a hold 'on suspension'. This means the hold will preserve it's place in the queue, but it will be skipped over to the next non-suspended hold when the item becomes available. Upon un-suspension, the hold will resume it's original place in the queue. * Expire holds that have been waiting too long (7408) For holds that have been waiting for pickup longer than the ReservesMaxPickupDelay number of days, there is now an automated way to mark these holds as "expired" (misc/cronjobs/holds/expire_holds_over.pl). * Cancel all waiting holds (6039) There is now a button to cancel all waiting holds and an option to choose to cancel or not hold needing a transfer when clicking on this cancel all button * Add "AllowItemsOnHoldCheckout" syspref to allow issue to the patron regardless of hold status (7090) An item scanned at a self check station connected to Koha over SIP2 can generate an issue regardless of whether there is a hold on the item. If the patron has the book in hand, they should be allowed to check it out; otherwise, what's to stop them from just taking it? * Add system pref to control behavior of submitting empty barcode field on circulation page (7077) It used to be that submitting an empty barcode input field when a patron's account was open in Circulation would clear the page (the same behavior as the "clear screen" buton offers now). Since inclusion of Bug 4389 this action has been co-opted to pop up a quick slip print window. A system preference has been added to allow the library to choose which behavior they want. PERFORMANCE (see below for more information about performance) * Use memcached cache koha-conf.xml configuration variables (6193) * Caching Templates (7511) * work on persistency compatibility to make Koha Plack / mod_perl compliant (7172) * Enhancing the performance test suite (6015) SEARCHING * More options for AdvancedSearchTypes (7031) Adds the ability to perform advanced searches in both the OPAC and staff client on more than a single AdvancedSearchType at a time. Support included for Itemtype, Collection Code and Shelving Location. AdvancedSearchTypes syspref preference is repurposed; no longer a single value, it can now take multiple item code fields separated by "|". The order of these fields will determine the order of the tabs in the OPAC and staff client advanced search screens. Values within the search type are OR'ed together, while each different search type is AND'ed together in the query limits. The current stored values are supported without any required modification. Each set of advanced search fields are displayed in tabs in both the OPAC and staff client. The first value in the AdvancedSearchTypes syspref is the selected tab; if no values are present, "itemtypes" is used. For non-itemtype values, the value in AdvancedSearchTypes must match the Authorised Value name, and must be indexed with 'mc-' prefixing that name. * Add ICU option to Koha out of the box (7698) during installation, you now have an option to use ICU. ICU is a unicode library that improve a lot zebra search engine for non latin alphabet catalogue INTERNALS * Be stricter with utf-8 output (6752) * Have mysql returning errors (7184) * Move SIPconfig.xml, sip_run and sip_shutdown outside from C4 (7238) * Allow authentication to Koha via PKI / x.509 certificates (6296) * Using OPACBaseURL for CAS Authentication (7745) * Cleaning up import tables and action_logs (7240) The cleanup_database.pl now can clean imported records and logs * Opac-ics depends on Date::ICal which is largely unmaintained (7532) the Date::ICal dependancy has been removed * Use KohaDates Template::Toolkit plugin to display dates (7743) all dates are displayed through a Template::Toolkit plugin, that make the code more readable and maintainable. This change is not visible to users * A lot of html div & ids & spans have been added to help with CSS customization (7760, 7781, 7876, and some others) TOOLS * Give option to use description for homebranch/holding branch in label creator instead of the branchcode (7615) * It is now possible to export MARC records without private/local fields (7345) * It is now possible to duplicate a holiday calendar (7477) * It is now possible to mark a range of holiday as closed (7681) LISTS * a deep work has been started to clean up the code and make it more flexible (7310 most of this work is invisible for now, but new features will come soon. for now, the only visible improvement is the system preference OpacAllowPublicListCreation that let you enable or disable the creation of public lists by patrons VARIOUS * Main page enhanced (7781) The search toolbox available on most page has been introduced on the main page for more consistency. A "Welcome to Koha" has been added, The menus are located at the same position if there is no news or if there is some * Improving koha-list and koha-create (6913) The biggest change is to add support for pre-determined MySQL credentials using a file in /etc/koha/passwd (for security reasons, if you use this feature, make sure the file is not world-readable). The configuration file has the following format: instance:user:password:database The database is optional, but the other two are both required if you want to specify MySQL credentials. If no credentials are specified for a given instance, the standard koha_instance username and an auto-generated password are used. The following additional command line options are now available: * --use-db - use a pre-existing database, see also --database * --database - specify the name of the mysql database (still defaults to koha_instance) * --passwdfile - specify a custom (Koha) passwd file for MySQL credentials The following additional variables are now available (for use in koha-sites.conf or a custom config file): * OPACPORT (previously added but not documented) - port on which the OPAC should be served * OPACPREFIX - prefix for the OPAC's virtual host * OPACSUFFIX - suffix for the OPAC's virtual host This commit also adds the --keep-mysql option to koha-remove, which, if specified, will prevent koha-remove from deleting the database or MySQL user when removing an instance. * rebuild_zebra.pl now has a --limit option to allow partial re-indexing (7246) * a System Preference has been added to select the first day of week (Sunday or Monday) to use in the calendar (OPAC and Intranet) (7261) * Koha's OAI-PMH now fully support sets (6440) * Provide datepicker for sql reports runtime parameters (5698) * Installation might fail it user web doesn't have in its path the database command path (6008) * Script to recreate entries in the statistics table from the issues and oldissues table (6025) * Set a timeout to z3950 servers that could have network problems occasionally (6140) PERFORMANCE ========== A lot of work has been made to improve Koha performance. Some of those improvements are available for everybody in any situation (like database connexion that has been speeded by 200ms (7188) However, the 3 most important speed improvements requires a tweaking of your configuration file TEMPLATE CACHING Without the tweak, templates are compiled everytime you call them. It means that, when you call circulation.pl page, the circulation template is read, parsed and analysed before being filled. The read/parsing/analysis need to be done only once. Fortunately, Template::Toolkit is a great tool and provide a caching mechanism: the read/parsing/analysis phase is made only once and the result is stored on your server, at a location defined in your koha configuration file. To activate the caching you must: - open koha-conf.xml - search for the <config> part of the file - add a line <template_cache_dir>/tmp</template_cache_dir> - that's all folks ! Of course, the /tmp directory is at your choice, you can use whatever directory you want. The directory you choose will be filled with files under path/to/koha/koha-tmpl/... (so, if you choose /tmp for template caching and your Koha is installed on /usr/opt/koha, you'll have /tmp/usr/opt/koha/koha-tmpl/...) The size of those files on the disk is less than 5MB The performance improvement is a rough 10%, so it's worth it MEMCACHE Memcache is a global caching mechanism that we use for caching almost static data that are retrieved from mySQL. It has been introduced in previous versions of Koha, but it has been upgraded in this release. Previously, the memcache configuration was in the Koha configuration. The consequence was that it was not possible to cache the configuration file itself. In Koha 3.8, the memcache configuration is now in the Apache setting. If you're upgrading from a previous version, you must update your configuration, or the memcache won't work anymore. To activate memcache: * install memcached server (apt-get install memcached). You should not need to update the memcached configuration file, the default values are OK, but it may be worth reading it, to let him use more memory or listen on a different unix port * update your koha-httpd.conf file, and add the following lines: <memcached_servers>127.0.0.1:11211</memcached_servers> <memcached_namespace>KOHA</memcached_namespace> Note that, if you have more than one Koha instance on your server, you *must* have a different namespace for each. Otherwise, the'll all share the same cached values, and you'll get some unexpected behaviour !!! DISCLAIMER = the memcache mechanism read cached values only once every 10 minuts. So, if you change some parameter that is cached (like cataloguing frameworks), you'll have to wait up to 10 minuts before seing the changes when cataloguing. You've been warned. In future versions, we plan to add a more efficient caching mechanism that will update the cache when it's needed, but for now, just wait. At your option, you also can restart memcache (sudo /etc/init.d/memcached restart) or flush the cache (echo "flush_all" | /bin/netcat -q 2 127.0.0.1 11211) The performance improvement is a rought 10%, mostly due to configuration caching (reading and parsing the XML on each page is costly) PERSISTENCY Since version 1, Koha run on the webserver in CGI mode. This mode is not the most efficient we can have. We made a lot of changes on the code to make it persistency compliant. The OPAC is safely run under Plack mode in production in Lyon 3 university and a few other early testers. The staff interface is still considered as experimental, but if you want to help us polishing and make it stable, you're welcomed to try it. Setting up Plack result in a huge performance boost. The speed of most pages is multiplied by 3 ! It means that a page computed in 1.8s will be computed in 0.6s under Plack. If you want to activate Plack, head to the wiki page: http://wiki.koha-community.org/wiki/Plack If you want to activate Plack for staff, we strongly suggest to be (or become) a subscriber of koha-devel mailing list (the Koha developers one), and announce there that you're running Plack for staff ! System Preferences ========== The following system preferences have been added or changes (the number in () is the bugzilla number) * OpacBrowseResults (7935) * OpacStarsRating (5668) * OPACXSLTDetailsDisplay, OPACXSLTResultsDisplay, XSLTDetailsDisplay and XSLTResultsDisplay (4032) * AutoResumeSuspendedHolds (7641) * Babeltheque_url_js and Babeltheque_url_update (7470) * SocialNetworks (7470) * OpacAllowPublicListCreation and OpacAllowSharingPrivateLists (7310) * UseICU (7092) Be carefull that this syspref can be changed, but only in conjunction with zebra configuration files * OAI-PMH:AutoUpdateSets (6440) * AllowPKIAuth (6296) * RoutingListNote (7557) * CalendarFirstDayOfWeek (7261) * ExpireReserveMaxPickupDelay and ExpireReserveMaxPickupDelayCharge (7408) * NoticeCSS and SlipCSS (7001) * AutoCreateAuthorities, LinkerModule, LinkerOptions, LinkerRelink, LinkerKeepStale, CatalogModuleRelink (7284) * OpacPatronimages (3516) * ShowReviewer is now none|full|first|surname|firstandinitial|username instead of yes/no (5503) * TransferWhenCancelAllWaitingHolds (6039) * OpacExportOptions (7392) * AllowItemsOnHoldCheckout (7090) * BorrowerRenewalPeriodBase * OPACLocalCoverImages, LocalCoverImages, AllowMultipleCovers (1633) * CircAutoPrintQuickSlip (7077) * BorrowerUnWantedField (6190) System requirements ========== Installation ========== You can install Koha from: * the tag.gz provided, see INSTALL and INSTALL.debian (even if you're not using debian. There are some usefull hints here) * git repository. Download Koha from git.koha-community.org, and checkout branch 3.8.x or tag 3.8.0 * debian package, that will be provided soon (check http://koha-community.org for announcement) Upgrading ========== If you have a Koha already running, you must take care of the following changes: * The SIP start and shutdown scripts and configuration file have been moved from C4 directory to misc/bin, Update your system or your SIP server won't work anymore * The cleanup_database.pl script has 2 new options, to clean-up imported records and logs, update your crontab : --import DAYS purge records from import tables older than DAYS days. Defaults to 60 days if no days specified. --logs DAYS purge entries from action_logs older than DAYS days. Defaults to 180 days if no days specified. * The Date::ICal dependancy has be removed and a DateTime::Format::ICal has been introduced, update your perl packages on your server ! * The memcache configuration has been moved from koha conf file to Apache configuration file Also note that Koha 3.4.x or later no longer stores items in biblio records. If you are upgrading from an older version ou will need to do the following two steps, they can take a long time (several hours) to complete for large databases misc/maintenance/remove_items_from_biblioitems.pl --run misc/migration_tools/rebuild_zebra.pl -b -r Documentation ========== The Koha manual is maintained in DocBook format. The home page for Koha documentation is http://koha-community.org/documentation/ As of the date of these release notes, the Koha manual is available: english: http://manual.koha-community.org/3.8/en/ french: http://manual.koha-community.org/3.8/fr/ 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 are available in this release for the following languages: * French (100%) * Spanish (100%) * German (100%) * Chinese -Taïwan- (97%, OPAC 100%) * Italian (86%, OPAC 100%) * Danish (81%) * Portuguese (79%) * French -canada- (76%) * English -nz- (76%) * Greek (74%) * Norwegian (73%) Note that some strings in online help have been introduced after string freeze, so: * the previous number don't count them * you'll find some strings in english in online help Partial (less than 50%) 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): Chris Nighswonger <cnighswonger(a)foundations.edu> Release Maintainer (3.8.x): Chris Cormack <chrisc(a)catalyst.net.nz> Credits ========== The following individuals contributed patches to Koha 3.8.0.: Paul Poulain Owen Leonard Katrin Fischer Chris Cormack Colin Campbell Marcel de Rooy Dobrica Pavlinusic Nicole C. Engard Kyle M Hall Ian Walls Jonathan Druart Jared Camins-Esakov Adrien Saurat Frédéric Demians Julian Maurice Srdjan Jankovic Liz Rea Robin Sheat Magnus Enger Duncan Tyler Elliott Davis Garry Collum Chris Hall Frédérick Capovilla MJ Ray Juan Romay Sieira Chris Nighswonger Alex Arnaud Sam Sanders Maxime Pelletier Matthias Meusburger Sophie Meynieux Tomas Cohen Arazi Mason James Marc Balmer Stéphane Delaune Henri-Damien Laurent D Ruth Bavousett Connor Dewar Christophe Croullebois Zeno Tajoli Gaetan Boisson Aleksa Vujicic Brendan Gallagher Marc Veron Galen Charlton Serhij Dubyk {Сергій Дубик} Janusz Kaczmarek Salvador Zaragoza Rubio Koustubha Kale Kate Henderson Jono Mingard Albert Oller Frère Sébastien Marie Martin Renvoize Peter Lorimer Bart Jorgensen Jorgia Kelsey Lyon3 Team James Mason Jesse Maseto Fridolyn Sommers Jon Aker Greg Barniskis Joy Nelson Nahuel Angelinetti 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. Bugs and feature requests ========== Bug reports and feature requests can be filed at the Koha bug tracker at http://bugs.koha-community.org/

5 8

Blog post about BibLibre development rebases
by Claire Hernandez 09 Jul '12

09 Jul '12

Hello all, I wrote a blog post about our developments and the community integration. You can read it here: http://drupal.biblibre.com/en/blog/entry/biblibre-developpments-rebase-and-… It is about: - 2012 goals development rebases - Vision and roadmap - Progress and learnt of january and february - Why the community needs you The purpose was to make visible our work and explain how people can invest into this development integration (for example for our french customers). If you have questions, juste ask. Have a good day, Claire;

5 9

Branch Specific System Preferences
by Chris Nighswonger 11 May '12

11 May '12

Recently the need has arisen locally to run the self-checkout (sco) under multiple user accounts to accommodate multiple branches using the sco module. To the best of my understanding this is not currently possible due to the way in which the user for the sco module is defined using a system preference. While there may be a number of ways to accomplish this, it seems that it may be desirable to have a category of "branch specific" system preferences. This would be an attempt to group system preferences into one of two general categories of "global" or "branch." Before launching out into writing such a feature, I thought I'd run it by both lists to see if a) I'm way off base, b) if such a feature is desirable, and c) if I'm off on an insanely hard project. Kind Regards, Chris

8 17

MARC::Record, record length and leader
by Julian Maurice 09 May '12

09 May '12

Hello, I know this is an old discussion but I just realized that saving a biblio record longer than 99999 bytes result in a malformed leader. Length of the record takes more than 5 characters and therefore remaining characters in the leader are shifted to the right. This cause the leader to have more than 24 characters. I'm not sure of what have to be done. Should MARC::Record die when encountering such a record? or should it force length to be 99999? or should the record be truncated to fit the spec? Has someone ever faced this problem? How did you handle it? -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

12 18

SQL reports [error]
by Paul 30 Apr '12

30 Apr '12

Good morning all: I have no problem with the philosophy of the following (bright yellow) pop-up error message: "The following error was encountered: This report contains the SQL keyword UPDATE. Use of this keyword is not allowed in Koha reports due to security and data integrity risks." and would not even consider suggesting a "bug." However, it would be most helpful to staff for a very specific but repetitive job that we do at year end (batch changing items.accessiondate after Tax Receipts have been issued for donations) to be able to use Koha from a work station, rather than getting me to work directly on the production server (I've already been asked 50 or 60 times, and there's another 400+ to go ...!) Can anyone point me rapidly to the portion of script that I should have a look at? For the record, the CLI mysql in question is: UPDATE items SET dateaccessioned='2011-12-31' WHERE price IS NOT NULL and price != '0.00' AND booksellerid = 'xxx' AND DATE(dateaccessioned) BETWEEN '2011-01-01' AND '2011-12-31'; Obviously for a report, I would use a construct for the last two conditions along the lines of: AND booksellerid = <<Pick your donor>> AND DATE(dateaccessioned) BETWEEN <<Accessioned BETWEEN (yyyy-mm-dd)>> AND <<and (yyyy-mm-dd)>>; Thanks and best regards, Paul

4 5

Re: [Koha-devel] SQL reports [error]
by Paul 30 Apr '12

30 Apr '12

At 05:44 PM 4/30/2012 +0200, Fischer, Katrin wrote: >I really donât like the idea. I think if you want someone to make >changes to the database, you should give them a proper tool and training >to do that (outside of Koha). Respectfully, we might be talking apples and oranges. *All* staff and many users "make changes to the database" - not fundamental structural changes, but add, modify and delete data records. And it was the latter point that I raised earlier today. You are of course correct that the various options allowed by UPDATE, DELETE, DROP, INSERT, and CREATE *can* modify/damage the structure of your database; but they can also be incredibly useful (see my earlier email that uses UPDATE.) I don't know how you are setup, but in my organization for any intervention that requires CLI, I personally have to go to our server room (I am the only keyholder) as I have locked the Koha server down fairly tightly from remote access. I decide (after consultation with staff/volunteers) what scripts can|cannot be used in the "normal course of business." I have tested a certain script required by staff (hundreds of times every year) by running it some seventy times to ensure it does what it is supposed to and does not do anything else. It is ready to go into useful production, but "as-is" Koha 3.6 does not allow me to make it available to staff -- and every time they need it (ad hoc basis) it takes me ten minutes, instead of staff "clicking a button." This is because the design of Koha includes very well-intentioned, but arbitrary nonetheless, hard code denying the use of UPDATE. The chances of a major catastrophe are much greater if I try and train our cataloguers in the intricacies of MySQL and allow them access to the server room, than if I develop a secure script and make it available on the staff interface -- and that was the only reason I raised it on this list and will implement it on our Koha server. YMMV. Best - Paul > The interface for statistics is very limited and does not give feedback > when your SQL statements have errors or produce no result sets. Also it > seems like a big security risk to me. > > > >Katrin > > > >From: koha-devel-bounces(a)lists.koha-community.org >[mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Jared >Camins-Esakov >Sent: Monday, April 30, 2012 5:21 PM >To: Paul Poulain >Cc: koha-devel(a)lists.koha-community.org >Subject: Re: [Koha-devel] SQL reports [error] > > > >Paul, > > > > > >On Mon, Apr 30, 2012 at 11:17 AM, Paul Poulain <paul.poulain(a)biblibre.com> >wrote: > >Question to all = could it be a good idea to let superlibrarians execute >dangerous SQLs like the one forbidden by the test ? >Otherwise asked: could we add a >unless permission eq 'superlibrarian' >condition ? > >( ie: "with great power comes great responsibility" -@spiderman uncle- ) > > > >We were actually just discussing that on #koha a few days ago. I argued >that only the database user (i.e. user 0) should be allowed to do it. If >you have the direct login, there's nothing you can't do with the system >just by logging into the database. > > > >Regards, > >Jared > > > >-- >Jared Camins-Esakov > >Bibliographer, C & P Bibliography Services, LLC > >(phone) +1 (917) 727-3445 > >(e-mail) jcamins(a)cpbibliography.com > >(web) http://www.cpbibliography.com/

2 1