Links in intranet-html/issues/index.html point to missing files such as: countissues.pl countreturns.pl ... and so on. I also note a reference to missing "kumara" directory. Shame they are missing, they look really useful :^) R.
On Fri, Mar 29, 2002 at 10:23:30AM +1100, Roger Buck said:
Links in intranet-html/issues/index.html point to missing files such as:
countissues.pl countreturns.pl ... and so on.
Good lord, i forgot we even had an issues folder :-) That can disappear. You can use the dailystats report in the reports section to get a count on issues/returns. And Kumara was the working name of Koha, before it became koha. It was C4, then Kumara, then Koha. Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
Chris Cormack wrote:
On Fri, Mar 29, 2002 at 10:23:30AM +1100, Roger Buck said:
Links in intranet-html/issues/index.html point to missing files such
[-snip--]
That can disappear.
OK.
You can use the dailystats report in the reports section to get a count on issues/returns.
I think that was thrown out in last CVS cleanup? R.
On Fri, Mar 29, 2002 at 10:39:23AM +1100, Roger Buck said:
You can use the dailystats report in the reports section to get a count on issues/returns.
I think that was thrown out in last CVS cleanup?
Ahh nope, its still there If you look reports/index.html It has a link to stats.pl which does the list of issues/returns per branch Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
On Fri, Mar 29, 2002 at 03:26:18PM +1100, Roger Buck said:
Chris Cormack wrote:
[--snip--]
Good lord, i forgot we even had an issues folder :-)
That can disappear. You can use the dailystats report in the reports section to get a count on issues/returns.
Do any of the current reports provide issues || reservations || returns by user ?
Not really The borrowers reading record provides a lot of information about the borrower's reading habits. (All accessed in the members section) The librarians at HLT arent to worried by sql, so they run queries against the database using myODBC and whatever windows program they like that month. Hence the reports section is really developed that much. Finlay is working on some reports about branch rotation, (which books/items have been issued from what branch and when) and a report to choose books which should move to another branch. It wouldnt be hard to do a report per borrower. If its something ppl would find useful? Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
Chris Cormack wrote: [--snip--]
It wouldnt be hard to do a report per borrower. If its something ppl would find useful?
This is part of something more related to web based reservation. I will have a short term need for web users to lodge a request (via koha OPAC) to borrow via the net. The librarians will then process the request and send out the resource by mail. The volume for this specific need is very low (around 10 - 20 requests per day). The transactions are entered manually into a non koha, school library system (OASIS). In the short term, the OASIS system will remain the sole authoritative database for all transactions. Rachel mentioned (yesteday) that on-line reservation functionality was planned for koha in medium term but I need to get our trial system up and running more quicky and didn't see this a a major problem anyhow. I was thinking that I would create a quick and dirty javascript "reservation form" as a link in the koha OPAC to do that... but am thinking that suitable functionality may already be available in koha... or "potentially" available, and just as easy as it would be to create my quick and dirty email based javascript stuff. Enough of my rambling. Any feedback? R.
participants (2)
-
Chris Cormack -
Roger Buck