[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Koha-devel] borrower issues, work made twice

From: Owen Leonard
Subject: Re: [Koha-devel] borrower issues, work made twice
Date: Fri, 31 Mar 2006 09:29:31 -0500
User-agent: Mutt/1.4.1i

On Fri, Mar 31, 2006 at 06:09:00AM -0800, Joshua Ferraro wrote:
> On Fri, Mar 31, 2006 at 04:02:56PM +0200, Pierrick LE GALL wrote:
> > circ/circulation and members/moremember are both showing a table of the
> > unreturned issue of a borrower. The two page provides the same
> > information, displayed with only very slight differences.
> > 
> > I wonder why the same work is made twice. Should we have this table
> > only on circ/circulation? and a link to circ/circulation on
> > members/moremember? The link could give a summary of current issues
> > (eg: "2 issues with 1 overdue").
> I'm not sure why there are two tables, one for 'current issues' and 
> one for 'previous issues'.

Because it's important for librarians to be able to easily tell which items
they've just checked out as opposed to which were checked out earlier.

> As far as why both members and circulation contain current issues, 
> we should check with katipo to double-check whethere their clients
> rely on that for something. Chris? Russ?

I think we shouldn't worry (particularly in the prog templates) about
whether we're displaying /too much/ information. We need to instead be
concerned that we're displaying too little.

The moremember display is useful for the librarian when they want to see
more information about the borrower than is displayed on the circulation
screen.  The circ screen needs to remain fairly stripped-down and
functional because a heavier circ screen will result in slower transaction
times (page reload). The moremember screen is for displaying as much
information as possible so that the librarian has a single page to go for
everything they need to see.

  -- Owen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]