Chris' solution still won't give you an accurate issue date, since he presumes that people renew items on the date_due -- and we all know that borrowers are not that dependable (damn!). Adding the issue_date to the issues table seems to be the only way to get an accurate statistic. I'm curious, Henri-Damien -- are you trying to do a daily statistics report? Is that why you need the issue date? Stephen Henri-Damien LAURENT said:
Hi, We are trying to design a stat report module for Koha here in France with Paul. And we have a problem on issues stats reporting.
In issues table, timestamp is modified as soon as the table is touched and returndate stores the date of return. The issue date is never stored in this table anywhere else.
Nevertheless, it is stored in statistics. And returns are also stored there.
But then, there is no way to know how they are related to one another. A selection on itemnumber and borrower card will tell us it was issued and return, but not Which returns answers Which issue. Suppose One borrows an item more than once and we are lost.
If one has a convenient code to know the average Loan period, that is a way to calculate the average time between issue and return date of an item for a borrower, we would be grateful.
Many Thanks
-- Henri-Damien LAURENT
-- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com