>From a librarian point of view, I think that the intranet side should be
different.  Librarians want to see more information when searching than the
general public would.  I agree that the staff search results need to change
- but I don't know if making it the same as the OPAC is what we need.

This is what I've heard from catalogers and it's what I (as a librarian)
feel as well.


---

Nicole C. Engard
Open Source Evangelist, LibLime
(888) Koha ILS (564-2457) ext. 714
nce@liblime.com
AIM/Y!/Skype: nengard

http://liblime.com
http://blogs.liblime.com/open-sesame/


On Tue, Aug 5, 2008 at 5:04 AM, Henri-Damien LAURENT
<laurenthdl@alinto.com>wrote:

> MJ Ray a écrit :
> > Paul POULAIN <paul.poulain@free.fr> wrote:
> >
> >> One of our libraries bugs me to have exactly the same look the the
> >> biblio summary in the list result.
> >> atm, the differences I can see are :
> >> - in staff, title/author are on 2 lines, in OPAC, they are on 1 line,
> >> separated by 'by'
> >> - in staff, publisher is after author, in OPAC it's on line 2, before
> pubyer
> >>
> >> Is there an explanation for those 2 diffs, or can I modify the staff to
> >> have exactly the same look as OPAC ?
> >>
> >
> > I've been told that there are also differences in how the series title
> > is displayed in the two interfaces.
> >
> > I think we should try for both interfaces to look similar, as far as
> > possible, because it confuses library staff.  I'm not familiar with
> > the display code.  Can we drive both displays from the same
> > code/templates?
> >
> > Thanks,
> >
> Unfortunately, in that regard, Koha is designed to have a real
> disconnection between OPAC and intranet
> so having the same include would not be possible. (unless we decide to
> enable links in apache configuration, which is BAD).
> + it wouldnot be really efficient since OPAC's API is different from
> staff's :
> cgi-bin/koha/opac-detail.pl is cgi-bin/koha/catalogue/detail.pl at staff.
> We could write a translator from staff to OPAC display (there is
> something like that in ISBDdetail.pl if i don't mind.)
> But then there would still be the problem of template separation.
> This raises also the problem of features : for instance, basket is not
> provided at intranet, but is really useful also for staff members.
>
> Should we change and unify Koha's scripts and naming ?
>
> Should this be an RFC for 3.4 ?
> for Koha 4.0  ?
>
> Any other comment ?
>
> --
> Henri-Damien LAURENT
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha.org
> http://lists.koha.org/mailman/listinfo/koha-devel
>

Maybe the answer is to make the staff interface a bit like the social networking websites do and have a first part of the display as "public profile" and then an extra part that appears in the staff interface.

To preface: I think the advanced search interfaces are underdeveloped. They've really not been properly overhauled for 3.0. Maybe we can hash something out that's better for 3.2. Josh and I discussed at one point an advanced search interface for the OPAC that was much like WorldCat's: http://www.worldcat.org/advancedsearch Fairly bold, very linear, and with some basic hints on functionality. The way we talked about it, there could be a link to a "power search" interface that had more options like boolean operators, additional limiters, etc. I'm not sure that the staff interface would really have to differ significantly (if at all) from the public one...it doesn't in dev_week, and that has worked well for NPL. I do think that the staff interface for search results should offer the librarian more information if necessary. Right now the primary functional difference is the detailed display of holdings information and statuses. I'd say that's an appropriate difference. But as for line breaks and minor display changes, as Paul describes, I don't have any objections to making the displays more alike. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org