http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1092
--- Comment #5 from Michael Hafen <michael.ha...@washk12.org> ---
(In reply to Katrin Fischer from comment #4)
> Michael, could you explain a bit more how this should work?
Sure... I was going to use the cookie tracking from reserves, but I wasn't able
to find it. So I'll have to explain this using my own, very out-dated, code.
This would effect a few pages: circ/circulation.pl, circ/returns.pl,
circ/renew.pl, reserve/request.pl, members/moremember.pl
In circulation, request, and moremember you could have code like:
$borrowernumber = $query->param('borrowernumber') ||
$session->param('borrowernumber');
And in all the pages there would be code like:
if ( $borrower->{borrowernumber} != $session->param('borrowernumber') {
$session->param('borrowernumber', $borrower->{borrowernumber});
}
With code like this when a borrower's record is loaded through a search, that
borrower's number is stored in the session. After that any access to pages
that require a borrower's record to be loaded can present the most recently
found borrower by pulling their number from the session instead of the
librarian having to search for them. It's most useful in going into the
reserves/request.pl page, which is why there is/used to be code to do the same
thing using a cookie. I think there are links into moremember from return and
renew, so this feature isn't as useful there. Though I have added a link
directory to circulation to the top menu, and to the list on the return page so
that circulation is one click closer there.
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
