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

RFC: Circulation Rules Interface and Backend Revamp RFC
by Jesse 13 Jan '16

13 Jan '16

The backend and frontend of the circulation/policy rules in Koha have been extended and stretched to the point where they cause a fair amount of issues and frustration. Many librarians and developers are uncertain when default rules are applied, and the very large number of possible settings makes the interface and backend unwieldy. Full details for our intended solution can be found at the link at the bottom of this email, but here's the gist: Instead of having one database row with all settings for a given library/category/itemtype, allow each setting (checkout length, fine amount, holds allowed, etc.) to be specified separately. Rework the interface to more clearly show the specificity of default/specific rules, and allow for this new database model. Accomplish the above incrementally by gradually changing APIs. http://wiki.koha-community.org/wiki/Circulation_Rules_Interface_and_Backend… Any and all comments are appreciated. Development on this project has been fully sponsored, and we are looking to start work later this year. -- Jesse Weaver

2 2

Reminder: General IRC meeting 13 January 2016
by Katrin Fischer 13 Jan '16

13 Jan '16

Hi all, just a quick reminder of the Koha General IRC meeting on 13 January 2016 at 20:00 UTC http://wiki.koha-community.org/wiki/General_IRC_meeting_13_January_2016 Hope to see you there :) Katrin

1 0

Playing with NYTProf
by Jonathan Druart 12 Jan '16

12 Jan '16

Hi devs, I have played with NYTProf at the end of the last week, here is my loosely structured notes: https://joubu.github.io/koha/nytprof/dbic/index.html I have not found big things to implement in order to improve the speed but I am wondering if there is not something wrong with the queries cache (Search in the page for "Update:") Hope to get some feedbacks. Cheers, Jonathan PS: If someone has a better idea to share the profiles, I am open-minded.

3 3

Prevent normalization during matching/import process
by David Cook 11 Jan '16

11 Jan '16

Hi all: I've opened a bug for preventing normalization during the matching/import process: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15541 I was trying to use a URL field as a matchpoint, and it was going horribly badly. 1) By default, punctuation is stripped, leading/trailing spaces are trimmed, and more than one space is condensed down to one space. This makes a URL into a string without any spaces or punctuation. 2) So, I had to add "Identifier-other:u" to biblio-zebra-indexdefs.xsl but I couldn't access it until I tried "id-other,st-urx" as my match point. The st-urx is necessary to make it use the ":u" register. 3) I also added some code to C4/Matcher.pm so that a match point normalizer of "None" would disable the normalization from #1. 4) I also plan to add a flag to C4::Search::SimpleSearch to disable the s/:/=/g normalization since that also destroys the URL in the query and makes it fail to match. I've only tested this so far with CHR but it works well. I'll probably look at ICU tomorrow. I'm sure there are probably other cases than just URLs where we will want to skip the default normalizing when doing matching. or normalize it in a way that accords with the way Zebra normalizes the data in records. For instance, Zebra will replace punctuation with a space for "phrase" indexes rather than just stripping it out and leaving nothing behind. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

1 0

Koha Hackfest in Berlin?
by Mirko Tietgen 07 Jan '16

07 Jan '16

Hello there, European (and other) Koha devs, I am considering hosting a Koha hackfest in Berlin/ Germany next year. It is not supposed to be a counter event to the Hackfest in Marseille nor the Kohacon, but an additional option to meet and work together. It could maybe take place July 2016 (very preliminary date for very preliminary planning), maybe 3 days or the whole week. Before I spend more time fantasizing about it, I'd like your opinion… - do you think it is a good idea (and you would consider joining)? - do you think it is a good idea (but you know you won't join)? - do you think it is not a good idea (given there is a Hackfest in Marseille and Kohacon already, or for other reasons)? - do you think you would have to decide between Berlin and Marseille? - do you think something completely different? No hard feelings if you say Kohacon + Marseille is enough, that would be very valuable feedback. For obvious reasons I would love to hear opinions from Europe (positive or negative), but if coming to Berlin is an option for people from more distant places, I'd love to hear that too. Cheers, Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

7 14

API keys
by David Cook 06 Jan '16

06 Jan '16

Hey all: What do people think about having keys for Koha APIs? Someone would register a key in Koha and give that key to the developer, the developer puts it in their app configuration, and they're good to go. One advantage would be that apps utilizing web services wouldn't actually have access to Koha itself - just to the APIs associated with the API key. By that same token, a Koha administrator could easily revoke access to an API if necessary for whatever reason. I'm sure there are other advantages as well. I was thinking a single API key could replace the username/password pair, but you still might want a client_id and an API key, so you're still managing two fields in your configuration. Anyway, just a thought. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

2 2

Questions about the development process of koha
by Fabricio Soares 05 Jan '16

05 Jan '16

My name is Fabricio and participate in a team that studies the Koha in Brazil, we are writing a scientific article about the evolution of the development of Koha and bug fixes. We evaluate the information contained in Bugzilla and GitHub, but still remained some doubts. I would like to have contact with some Koha master developer to be able to solve our doubts but could not an email address to establish a contact. Below are some of the questions. 01) How to divide developers? 02) How the project's maintainers are organized? 03) How they separate new features treatment bugs? 04) The developers fixing bugs are the same as producing new features? 05) Github users also post questions in bugzilla? 06) Is there any way to relate the github user with bugzilla user? 07) Is there any study on incident response time? 08) They assign a delay so high between the opening of a call and incident resolution (average 805 days)? 09) As they face the forks LibLime and Kobli? 10) The project maintainer makes a comparison study between the development of Koha and OpenSource and Owners competitors? 11) The project maintainers evaluate the response performance to incidents? 12) Any development methodology to the new features is used? Grateful for the attention. Fabricio

2 1

Koha Community Newsletter: December 2015
by kohanews 30 Dec '15

30 Dec '15

Fellow Koha users: The Koha Community Newsletter for December 2015 is here: https://koha-community.org/koha-community-newsletter-december-2015/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! Chad Roseburg Editor, Koha Community Newsletter

1 0

Next General IRC meeting
by Brendan Gallagher 29 Dec '15

29 Dec '15

Hello All - The next meeting is 13 January 2016 at 20:00 UTC Conversion to your local time: Time and Date.com converter for various local times <http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+M…> Here is the agenda - http://wiki.koha-community.org/wiki/General_IRC_meeting_13_January_2016 Thanks and I hope to see a lot of you there. One thing we need to do is to encourage more people to sign-off on bugs. I think I will add a brainstorming session to agenda for people to throw out ideas for encouragement for sign-offs (also see Jonathan's email for more sign-offs). Cheers, Brendan Gallagher

2 1

easykoha update announed but downloads only 1.8 meg or 11 meg? where is whole
by COURYHOUSE＠aol.com 29 Dec '15

29 Dec '15

easykoha update announced but downloads only 1.8 meg or 11 meg? where is whole thing? koha has to be larger!/ i got several update messages from source forge on this yesterday and today..... Help anyone?? Ed Sharpe please email me as I am on digest and miss alot. thanks In a message dated 12/23/2015 4:00:12 A.M. US Mountain Standard Time, koha-devel-request(a)lists.koha-community.org writes: Send Koha-devel mailing list submissions to koha-devel(a)lists.koha-community.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel or, via email, send a message with subject or body 'help' to koha-devel-request(a)lists.koha-community.org You can reach the person managing the list at koha-devel-owner(a)lists.koha-community.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-devel digest..." Today's Topics: 1. Perldoc website (Nicolas Legrand) 2. Re: Perldoc website (Galen Charlton) 3. Re: Perldoc website (Nicolas Legrand) 4. Re: Get rid of item-level_itype? (Katrin Fischer) ---------------------------------------------------------------------- Message: 1 Date: Tue, 22 Dec 2015 14:47:01 +0100 From: Nicolas Legrand <nicolas.legrand(a)bulac.fr> To: koha-devel(a)lists.koha-community.org Subject: [Koha-devel] Perldoc website Message-ID: <CAODBKZfM2ddWMazXvfbp3xFNDV1zY8YkL3NhN9LktJrNaBDutg(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hey, I'm a bit puzzled by the web perldoc, some changes are not effective on master. I bumped on this one: http://perldoc.koha-community.org/C4/Reserves.html#CanItemBeReserved CanItemBeReserved $error = &CanItemBeReserved($borrowernumber, $itemnumber) This function return 1 if an item can be issued by this borrower. The return values has changed in commit 51f0a0b7229c1e76699708a548a9e3e68c9953ad : http://git.koha-community.org/gitweb/?p=koha.git;a=commit;h=51f0a0b7229c1e76 699708a548a9e3e68c9953ad $canReserve = &CanItemBeReserved($borrowernumber, $itemnumber) if ($canReserve eq 'OK') { #We can reserve this Item! } @RETURNS OK, if the Item can be reserved. ageRestricted, if the Item is age restricted for this borrower. [...] Cheers, -- Nicolas Legrand Administration technique et d?veloppements du syst?me de gestion de la biblioth?que Biblioth?que universitaire des langues et civilisations 65 rue des Grands Moulins F-75013 PARIS T +33 1 81 69 18 22 www.bulac.fr ------------------------------ Message: 2 Date: Tue, 22 Dec 2015 09:36:46 -0500 From: Galen Charlton <gmc(a)esilibrary.com> To: Nicolas Legrand <nicolas.legrand(a)bulac.fr> Cc: "koha-devel(a)lists.koha-community.org" <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Perldoc website Message-ID: <CAPLnt67Sk81EvqsYxqrEHrHU04_dajF3VnnmVhMwZcz73ies7g(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi, On Tue, Dec 22, 2015 at 8:47 AM, Nicolas Legrand <nicolas.legrand(a)bulac.fr> wrote: > I'm a bit puzzled by the web perldoc, some changes are not effective > on master. It looks like that a while back an issue with the Git clone used for generating the perldoc prevented updates from being fetched. I've corrected the issue and am regenerating the website now. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager 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 ------------------------------ Message: 3 Date: Tue, 22 Dec 2015 15:39:04 +0100 From: Nicolas Legrand <nicolas.legrand(a)bulac.fr> To: Galen Charlton <gmc(a)esilibrary.com> Cc: "koha-devel(a)lists.koha-community.org" <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Perldoc website Message-ID: <CAODBKZdcYcrnQS3XVBrObMrVMaohZyO4o3SecOkbp0rtdpBNkQ(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Thanks ! 2015-12-22 15:36 GMT+01:00 Galen Charlton <gmc(a)esilibrary.com>: > Hi, > > On Tue, Dec 22, 2015 at 8:47 AM, Nicolas Legrand > <nicolas.legrand(a)bulac.fr> wrote: >> I'm a bit puzzled by the web perldoc, some changes are not effective >> on master. > > It looks like that a while back an issue with the Git clone used for > generating the perldoc prevented updates from being fetched. I've > corrected the issue and am regenerating the website now. > > Regards, > > Galen > -- > Galen Charlton > Infrastructure and Added Services Manager > 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 -- Nicolas Legrand Administration technique et d?veloppements du syst?me de gestion de la biblioth?que Biblioth?que universitaire des langues et civilisations 65 rue des Grands Moulins F-75013 PARIS T +33 1 81 69 18 22 www.bulac.fr ------------------------------ Message: 4 Date: Wed, 23 Dec 2015 08:24:57 +0100 From: Katrin Fischer <Katrin.Fischer.83(a)web.de> To: koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] Get rid of item-level_itype? Message-ID: <567A4C49.2050806(a)web.de> Content-Type: text/plain; charset=windows-1252 Hi Jonathan, thx for looking into this! Am 17.12.2015 um 17:41 schrieb Jonathan Druart: > Update DB migration: > 1/ add column biblio.biblio_type > 2/ update biblio.biblio_type with biblioitems.itemtype > 3/ rename items.itype with items.item_type > 4/ set items.item_type = biblio.biblio_type if items.item_type is not > defined (or if item_level_itypes is not set?) > 5/ rename deleteditems.itype with items.item_type, and don't update it (right?) Hm, I think I'd update it for consistency and easier use for reporting. > 6/ drop column biblioitems.itemtype > 7/ rename course_items.itype with course_items.item_type (to be consistent) I am not sure about renaming the columns. Some thoughts: Both the itemtype on items and on biblio level will still refer to an entry in the itemtypes table. So if we rename, maybe we should reflect the connection somehow. It also looks like we are using 'itemtype' over 'item_type' in a lot of other tables: statistics, branchrules, default_branch_item_rules, issuingrules, suggestions... I think changing items.itype to items.itemtype would make sense to me. For record level... I am not sure about moving from biblioitems to biblio, it will mean that a lot of the reports will be broken and we probably can't fix them easily with a script. > Then we will have to replace the notices ^items.itype^items.item_type^ > and ^biblioitems.itemtype^biblio.biblio_type^ should solve the > problem. We should think about doing something similar to the custom SQL reports - I think there are probably a lot in all the databases that use the itemtypes in some way. > Looking at the code, I have found some places where I am not sure how > to fix the display: > 1/ For instance on the detail page of a biblio, or when a user place a > hold, the item type is display either *on top* of the items list, or > *in* a specific column of the table. > Which makes sense. If we remove the pref, we have 3 choices: > a. always display the item type in the table > b. display the item type on top only if all item types are identical > at the biblio type (will require some additional loops) > c. display both and set a css class: the library will be able to > hide the one it wants > d. the answer d Hm, for me it's either a or c. Or maybe d? ;) > 2/ The change will require a complete reindexation of zebra: the index > will be renamed (itype => item_type, mc-itype => mc-item_type, > itemtype => biblio_type, mc-itemtype => mc-biblio_type). > Is it acceptable? Hm, I am not sure how commonly people reindex after updating. Generally I think it's a good idea, but I am not sure we have this documented well. Could we avoid renaming maybe and use aliases so the old index names still work? > I think I can produce a patch in 2 days of work (which is nothing > compared to the number of days Koha developpers have lost to > understand how this code works...), but it will require a lot of deep > testing. > It will really hard to provide tests for this change since it impacts > a lot of file, but I will write some for the most common subroutines. > > I would like some people engaged in the signoff process, not to let > the patches in the signoff queue too long. > > Cheers, > Jonathan > > 2015-12-11 12:04 GMT+00:00 Jonathan Druart > <jonathan.druart(a)bugs.koha-community.org>: >> Hi devs, >> >> Friday is a good day for this kind of questions, fasten your seat belt >> for a time travel. >> >> As many of you know, the item type is not correctly managed all around >> the different Koha modules. Sometimes it's, sometimes it's not. >> The main issue is that we deal with it at too many places and the code >> is not clean/centralised at all. >> >> So I have searched for previous discussions on this subject and I have >> found this "Abandoned RFC" on the wiki : >> http://wiki.koha-community.org/wiki/Mandate_item-level_circulation_rules_RFC >> filled from this koha-devel thread >> http://lists.koha-community.org/pipermail/koha-devel/2008-October/031144.ht… >> >> The questions are: >> 1/ Is this still valid? >> 2/ Is there something missing in the different steps described? >> 3/ Does someone have some other suggestions to do? >> >> I would be happy to provide this change but first I would like to get >> confirmation about it and get people involved in signoffing/QAing the >> possible patch set. >> >> Cheers, >> Jonathan > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > ------------------------------ _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ End of Koha-devel Digest, Vol 121, Issue 31 *******************************************

3 2