No subject
Mon Jul 28 14:19:07 CEST 2008
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 at 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 at alinto.com>wrote:
> MJ Ray a =E9crit :
> > Paul POULAIN <paul.poulain at 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 t=
o
> >> 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 at lists.koha.org
> http://lists.koha.org/mailman/listinfo/koha-devel
>
------=_Part_2417_19796566.1217935004619
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
<div dir=3D"ltr">From a librarian point of view, I think that the intranet =
side should be different. Librarians want to see more information whe=
n searching than the general public would. I agree that the staff sea=
rch results need to change - but I don't know if making it the same as =
the OPAC is what we need.<br>
<br>This is what I've heard from catalogers and it's what I (as a l=
ibrarian) feel as well.<br clear=3D"all"><br><br>---<br><br>Nicole C. Engar=
d<br>Open Source Evangelist, LibLime<br>(888) Koha ILS (564-2457) ext. 714<=
br>
<a href=3D"mailto:nce at liblime.com">nce at liblime.com</a><br>AIM/Y!/Skype: nen=
gard<br><br><a href=3D"http://liblime.com">http://liblime.com</a><br><a hre=
f=3D"http://blogs.liblime.com/open-sesame/">http://blogs.liblime.com/open-s=
esame/</a><br>
<br><br><div class=3D"gmail_quote">On Tue, Aug 5, 2008 at 5:04 AM, Henri-Da=
mien LAURENT <span dir=3D"ltr"><<a href=3D"mailto:laurenthdl at alinto.com"=
>laurenthdl at alinto.com</a>></span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt =
0pt 0.8ex; padding-left: 1ex;">
MJ Ray a =E9crit :<br>
<div class=3D"Ih2E3d">> Paul POULAIN <<a href=3D"mailto:paul.poulain@=
free.fr">paul.poulain at free.fr</a>> wrote:<br>
><br>
>> One of our libraries bugs me to have exactly the same look the the=
<br>
>> biblio summary in the list result.<br>
>> atm, the differences I can see are :<br>
>> - in staff, title/author are on 2 lines, in OPAC, they are on 1 li=
ne,<br>
>> separated by 'by'<br>
>> - in staff, publisher is after author, in OPAC it's on line 2,=
before pubyer<br>
>><br>
>> Is there an explanation for those 2 diffs, or can I modify the sta=
ff to<br>
>> have exactly the same look as OPAC ?<br>
>><br>
><br>
> I've been told that there are also differences in how the series t=
itle<br>
> is displayed in the two interfaces.<br>
><br>
> I think we should try for both interfaces to look similar, as far as<b=
r>
> possible, because it confuses library staff. I'm not familia=
r with<br>
> the display code. Can we drive both displays from the same<br>
> code/templates?<br>
><br>
> Thanks,<br>
><br>
</div>Unfortunately, in that regard, Koha is designed to have a real<br>
disconnection between OPAC and intranet<br>
so having the same include would not be possible. (unless we decide to<br>
enable links in apache configuration, which is BAD).<br>
+ it wouldnot be really efficient since OPAC's API is different from<br=
>
staff's :<br>
cgi-bin/koha/opac-detail.pl is cgi-bin/koha/catalogue/detail.pl at staff.<b=
r>
We could write a translator from staff to OPAC display (there is<br>
something like that in ISBDdetail.pl if i don't mind.)<br>
But then there would still be the problem of template separation.<br>
This raises also the problem of features : for instance, basket is not<br>
provided at intranet, but is really useful also for staff members.<br>
<br>
Should we change and unify Koha's scripts and naming ?<br>
<br>
Should this be an RFC for 3.4 ?<br>
for Koha 4.0 ?<br>
<br>
Any other comment ?<br>
<br>
--<br>
<font color=3D"#888888">Henri-Damien LAURENT<br>
</font><div><div></div><div class=3D"Wj3C7c">______________________________=
_________________<br>
Koha-devel mailing list<br>
<a href=3D"mailto:Koha-devel at lists.koha.org">Koha-devel at lists.koha.org</a><=
br>
<a href=3D"http://lists.koha.org/mailman/listinfo/koha-devel" target=3D"_bl=
ank">http://lists.koha.org/mailman/listinfo/koha-devel</a><br>
</div></div></blockquote></div><br></div>
------=_Part_2417_19796566.1217935004619--
More information about the Koha-devel
mailing list