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@lists.koha-community.org writes: Send Koha-devel mailing list submissions to koha-devel@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@lists.koha-community.org You can reach the person managing the list at koha-devel-owner@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@bulac.fr> To: koha-devel@lists.koha-community.org Subject: [Koha-devel] Perldoc website Message-ID: <CAODBKZfM2ddWMazXvfbp3xFNDV1zY8YkL3NhN9LktJrNaBDutg@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@esilibrary.com> To: Nicolas Legrand <nicolas.legrand@bulac.fr> Cc: "koha-devel@lists.koha-community.org" <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Perldoc website Message-ID: <CAPLnt67Sk81EvqsYxqrEHrHU04_dajF3VnnmVhMwZcz73ies7g@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi, On Tue, Dec 22, 2015 at 8:47 AM, Nicolas Legrand <nicolas.legrand@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@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@bulac.fr> To: Galen Charlton <gmc@esilibrary.com> Cc: "koha-devel@lists.koha-community.org" <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Perldoc website Message-ID: <CAODBKZdcYcrnQS3XVBrObMrVMaohZyO4o3SecOkbp0rtdpBNkQ@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Thanks ! 2015-12-22 15:36 GMT+01:00 Galen Charlton <gmc@esilibrary.com>:

Hi,

On Tue, Dec 22, 2015 at 8:47 AM, Nicolas Legrand <nicolas.legrand@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@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@web.de> To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Get rid of item-level_itype? Message-ID: <567A4C49.2050806@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@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.htm...

...

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@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@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 *******************************************