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

Thu Sep 9 21:56:56 CEST 2021


Le 08/09/2021 à 13:56, dcook at prosentient.com.au a écrit :
> 
> I suppose your average user (on either interface) won’t know MARC anyway…
I know a Marc, he is a friend of mine ^^

> 
> 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 
> <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
>     <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
>     <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
>     website : https://www.koha-community.org/
>     <https://www.koha-community.org/>
>     git : https://git.koha-community.org/ <https://git.koha-community.org/>
>     bugs : https://bugs.koha-community.org/
>     <https://bugs.koha-community.org/>
> 
> 
> -- 
> 
> Andrew Fuerste-Henry
> 
> Educator
> 
> (he/they)
> 
> ByWater Solutions
> 
> bywatersolutions.com <http://bywatersolutions.com/>
> 
> Phone:(888)900-8944 <tel:(888)%20900-8944>
> 
> What is Koha?
> <http://bywatersolutions.com/what-is-koha/>
> 

-- 
Fridolin SOMERS <fridolin.somers at biblibre.com>
Software and system maintainer 🦄
BibLibre, France