[Koha-devel] found = Null in CancelReserve

[BOUIS Sonia]

Thanks Katrin. I've filled a bug with a patch :  http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14968

Regards,
Sonia

Date: Sun, 4 Oct 2015 15:13:45 +0200
From: Katrin Fischer <Katrin.Fischer.83 at web.de>
To: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] found = Null in CancelReserve
Message-ID: <56112609.6090201 at web.de>
Content-Type: text/plain; charset=windows-1252

Hi Sonia,

I have been thinking about this, but see no reason not to keep the found status when moving the hold. I think we are not using the data in old_reserves. Can you file a bug report please?

Katrin

Am 02.10.2015 um 14:27 schrieb BOUIS Sonia:
> Hi,
> 
> We are working on hold stuff at the moment and we have a lot of questions !
> 
> We want to provide statistics on canceled holds to know if they 
> haven?t been picked-up as waiting for the borrower or if the 
> expiration_date on hold have been passed.
> 
> But if we can see if a hold is waiting in found column of reserves 
> table, this information disappeared from old_reserves table.
> 
> In C4/Reserves.pm, there?s this SQL request in CancelReserve :
> 
> UPDATE reserves
> 
>             SET    cancellationdate = now(),
> 
>                    found            = Null,
> 
>                    priority         = 0
> 
>             WHERE  reserve_id = ?
> 
>  
> 
> I?m not a specialist, but I wonder why found is set to Null when 
> cancelling and why we can?t keep this information in old_reserves ?
> 
>  
> 
> Thanks in advance for any explanation.
> 
>  
> 
> Cheers,
> 
>  
> 
>  
> 
> *Sonia BOUIS*
> 
>  
> 
> *Responsable du Syst?me int?gr? de gestion des biblioth?ques***
> 
> * *
> 
> *bIBLIOTH?QUES UNIVERSITAIRES*
> 
> *Universit? Jean Moulin Lyon 3*
> 
> 6 Cours Albert Thomas - B.P. 8242 ? 69355 Lyon Cedex 08
> 
> *ligne directe **:**+*33 (0)4 78 78 79 03*| **http://bu.univ-lyon3.fr
> <http://bu.univ-lyon3.fr/>*
> 
> * *
> 
> */L'Universit? Jean Moulin est membre fondateur de l'Universit? de 
> Lyon/*
> 
>  
> 
> 
> 
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at 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/
> 



------------------------------

Message: 2
Date: Mon, 5 Oct 2015 13:48:53 +1300
From: Mason James <mtj at kohaaloha.com>
To: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Bootstrap 2.2.2 in the staff client
Message-ID: <5611C8F5.6010705 at kohaaloha.com>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 15-09-9 12:28 am, Owen Leonard wrote:
> On Tue, Sep 8, 2015 at 2:32 AM, David Cook <dcook at prosentient.com.au> wrote:
>> Owen: Ahh, I didn't realize that Bootstrap had a customizer. I figured it
>> had to be something along those lines. It's a shame they don't indicate in
>> the comments that it was a custom version built by them at least :S.
> Newer versions do, for what it's worth.
>
>> Owen: Regarding the speed, did you find there was a noticeable difference in
>> the speed of the custom CSS vs the full CSS?
> I didn't test speed differences, I just worked on the assumption that
> smaller is better. I think shaving off every byte we can is going to
> add up to speed improvements.

here is some nice info about measuring the load time of a page
  https://developer.chrome.com/devtools/docs/network#resource-network-timing

also..  http://docs.webplatform.org/wiki/dom/Event/DOMContentLoaded

one thing i'm curious about is measuring the parsing/rendering time of CSS
anyone know how to do that?



------------------------------

_______________________________________________
Koha-devel mailing list
Koha-devel at 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 119, Issue 6
******************************************