[Koha-devel] Listing Zebra (and Elasticsearch) indexes for end-users' benefit

Thu Sep 9 01:56:39 CEST 2021

Hi Andrew,

Thanks for sharing that manual page. It actually reminds me that there’s a difference too between Zebra indexes and CCL qualifiers. For instance 030 is indexed into CODEN, but CODEN isn’t a CCL qualifier, so you can’t use it for searching. That certainly adds an extra wrinkle…

Yeah, Zebra and Elastic are very different though. I don’t know that Search Engine Config would be the right place to show Zebra content which is not dynamically configurable. 

After having another think about it, listing Zebra indexes isn’t accurate enough, because what we really need are Zebra CCL qualifiers mapped to MARC fields. 

In the end to be mostly accurate, it’s processing biblio-koha-indexdefs.xml (it would be more accurate to process biblio-zebra-indexdefs.xsl although that’s much harder), processing bib1.att, processing ccl.properties, and maybe a dynamic lookup from Zebra. 

Ideally, I’d like to be able to show that Zebra CCL qualifier to MARC field relationship to both Staff and OPAC users, although I suppose your average user (on either interface) won’t know MARC anyway…

David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

Office: 02 9212 0899

Online: 02 8005 0595

From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf Of Andrew Fuerste-Henry
Sent: Wednesday, 8 September 2021 11:14 PM
To: Fridolin SOMERS <fridolin.somers at biblibre.com>
Cc: koha-devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] Listing Zebra (and Elasticsearch) indexes for end-users' benefit

Hi all!

For what it's worth, there is a list of Zebra indexes in the manual: https://koha-community.org/manual/latest/en/html/searching.html#koha-search-indexes. I'm all for a fun tool that shows them within Koha, but it'd also be great if the manual were up to date.

Speaking of showing search indexes right in the Koha staff client, Elastic already does that. The Search Engine Config page in administration shows you exactly how all of your MARC data is indexed for Elastic. It would totally make sense to rework this to also be able to show Zebra values.

Andrew

On Wed, Sep 8, 2021 at 3:49 AM Fridolin SOMERS <fridolin.somers at biblibre.com <mailto:fridolin.somers at biblibre.com> > wrote:

Hi, sounds nice.

FIY I am actually using a transformation of Zebra config in order to 
present it in CSV:
https://git.biblibre.com/biblibre/tools/src/branch/master/zebra/list_indexes.xsl

We may use this to display in HTML.

Best regards,

Le 18/08/2021 à 17:12, dcook at prosentient.com.au <mailto:dcook at prosentient.com.au>  a écrit :
> Hi all,
> 
> As always, a new day brings a new Zebra idea.
> 
> One of my librarians asked me if there was any way to get a list of 
> Zebra indexes (particularly for Record Matching Rules), and I was all 
> prepared to say no… when I remembered something I read the other day.
> 
> It turns out you can send the query "@attr exp1 1=1 attributedetails" to 
> the magical database “IR-explain-1”, and it will give you a list of all 
> the indexes in that database along with the type of index and how many 
> documents are indexed against that index in the database. I think this 
> is something that we should add to Koha!
> 
> I’m not familiar with Koha’s use of Elasticsearch, but I imagine there 
> is an easy way of getting a list of Elasticsearch indexes?
> 
> --
> 
> Of course, while having a list of indexes is good, it would be nice to 
> know what MARC data is in each of those indexes. I’m thinking about 
> creating a Koha Plugin that parses "biblio-koha-indexdefs.xml" and shows 
> a user-friendly view of what parts of the MARC record are put into which 
> indexes.
> 
> --
> 
> What do folk think about that? I think having a list of Zebra indexes 
> would be very useful for Record Matching Rules, but also for a “Search 
> tips” guide for the Staff Interface and OPAC.
> 
> While we could provide a static list of indexes, but I think that would 
> be too much of a maintenance burden. I think having a list from Zebra 
> (or Elasticsearch), which we could cache in Memcached, would be the way 
> to go.
> 
> Ideally, we could have an API route that surfaces this information, so 
> that we could just do an AJAX lookup from a web interface.
> 
> --
> 
> I’m hoping my librarian will sponsor development of a plugin, but I 
> think this would be useful in the core Koha code.
> 
> David Cook
> 
> Senior Software Engineer
> 
> Prosentient Systems
> 
> Suite 7.03
> 
> 6a Glen St
> 
> Milsons Point NSW 2061
> 
> Australia
> 
> Office: 02 9212 0899
> 
> Online: 02 8005 0595
> 

-- 
Fridolin SOMERS <fridolin.somers at biblibre.com <mailto:fridolin.somers at biblibre.com> >
Software and system maintainer 🦄
BibLibre, France
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org <mailto:Koha-devel at lists.koha-community.org> 
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

-- 

Andrew Fuerste-Henry

Educator

(he/they)

ByWater Solutions

 <http://bywatersolutions.com/> bywatersolutions.com

Phone: <tel:(888)%20900-8944> (888)900-8944

  <https://drive.google.com/a/bywatersolutions.com/uc?id=1VVVFrey9XECr3VKtRsBrnaF0w5ESXYcA&export=download> 

 <http://bywatersolutions.com/what-is-koha/> What is Koha?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210909/5d4a10ad/attachment-0001.htm>