If no one can voice a reason to have separate indexes for the OPAC v. the
staff client, best to use the same ones.  It's what we do for biblios, and
authorities is just another Zebra database.

Keeping things simple will improve life for everyone.


-Ian

On Thu, Jul 12, 2012 at 12:35 PM, Jared Camins-Esakov <
jcam...@cpbibliography.com> wrote:

> Hello.
>
> Triggered by bug 8206 (add additional search options to authority browser
> on OPAC: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8206)
> Marcel, Katrin, and I have been discussing the inconsistent indexes used
> for searching authorities in the staff client an OPAC. Somewhere in git
> history (I can't remember exactly where I saw it) there was a note that the
> OPAC "had" to use different authority indexes than the staff client, so
> when I re-added the search options for bug 8206, I used the same indexes
> that the OPAC had used previously. Marcel pointed out quite correctly that
> if no one can explain *why* the OPAC should have to use different indexes,
> it would be better to make the staff client and OPAC consistent. So, I turn
> to the community: at this point could I just use the same indexes in the
> OPAC as are used in the staff client?
>
> Regards,
> Jared
>
> --
> Jared Camins-Esakov
> Bibliographer, C & P Bibliography Services, LLC
> (phone) +1 (917) 727-3445
> (e-mail) jcam...@cpbibliography.com
> (web) http://www.cpbibliography.com/
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to