mumi: Add context in search results when querying for (subject:<something>)

Open

Details

3 participants

Arun Isaac
Felix Lechner
Giovanni Biscuolo

Owner: Somebody

Submitted by: Giovanni Biscuolo

Severity: wishlist

Giovanni Biscuolo wrote on 7 Sep 2023 18:52

[mumi] [wishlist] Allow searching subject prefix

Recipients:(address . bug-guix@gnu.org)(name . Arun Isaac)(address . arunisaac@systemreboot.net)

Message-ID:871qfaexil.fsf@xelera.eu

Hello,

IMO is useful to be able to search for "subject:foo", it's a different

search than searching for foo in the body

in file mumi/xapian.scm I read:

Toggle snippet (9 lines)

;; Index subject and body without prefixes for general

;; search.

(index-text! term-generator subjects)

(increase-termpos! term-generator)

(index-text! term-generator text)

Is it possible to add such a feature please?

Thanks! Gio'

P.S.: I did not Cc: Ricardo Wurmus since AFAIU he prefers not to

continue developing this

Giovanni Biscuolo

Xelera IT Infrastructures

Arun Isaac wrote on 10 Sep 2023 06:47

Recipients:

Message-ID:87y1hezlaq.fsf@systemreboot.net

Hi Gio,

Thanks for this feature request! It's always gratifying to know that

someone is using mumi, especially its more advanced features! :-)

Toggle quote (3 lines)

> IMO is useful to be able to search for "subject:foo", it's a different

> search than searching for foo in the body

It looks like we implement this already. See
https://git.savannah.gnu.org/cgit/guix/mumi.git/tree/mumi/xapian.scm#n141
A search for "subject:foo" should work already.

Cheers!
Arun

Giovanni Biscuolo wrote on 10 Sep 2023 16:16

mumi: Add msg number and subject in search results when searching for subject:

Recipients:(address . 65809@debbugs.gnu.org)

Message-ID:8734zmdsfq.fsf@xelera.eu

Hi!

(I'll also try to retitle this bug, after submitting this update)

Arun Isaac <arunisaac@systemreboot.net> writes:

Toggle quote (3 lines)

> Thanks for this feature request! It's always gratifying to know that

> someone is using mumi, especially its more advanced features! :-)

mumi advanced features could be **very** useful to a lot of contributing

activities, if improved a little bit and better understood

Toggle quote (7 lines)

>> IMO is useful to be able to search for "subject:foo", it's a different

>> search than searching for foo in the body

> It looks like we implement this already. See

> https://git.savannah.gnu.org/cgit/guix/mumi.git/tree/mumi/xapian.scm#n141

> A search for "subject:foo" should work already.

Uh I missed that code:

Toggle snippet (5 lines)

(index-text! term-generator subjects #:prefix "S")

otherwise I could have realize that I was misinterpreting mumi search

output.

If for example I search for 'subject:zoneinfo' I get this results:

Toggle snippet (10 lines)

giovanni@roquette [genv]\: mumi search subject:zoneinfo

#31484 [PATCH] gnu: icu4c: Patch zoneinfo directory.

opened on 17 mag 2018 14:58 by Christopher Baines

#57448 ? [PATCH 0/5] gnu: exa: Update to 0.10.1.

opened on 27 ago 2022 12:09 by ???

#58614 ? [PATCH 000/187] Remove unused crates

opened on 18 ott 2022 22:18 by Efraim Flashner

(the mumi CLI output is colored and the separation of each bug is

clearer)

Via web: https://issues.guix.gnu.org/search?query=subject%3Azoneinfo

Since 2 of the 3 patch "titles" are missing 'zoneinfo', I thought the

search was done in the subject and in the body, not just the subject.

For example, bug #58614 actually contains a message with this subject:

[PATCH 185/187] gnu: Remove rust-zoneinfo-compiled-0.4.

...my misunderstanding was due to the fact that each tracked bug (issue)

have a /Title/ given by the subject mail header from the original report

or by a retitle [1]; thus Title _is_ different from the "Subject"s of

the rest of the messages in the /thread/ of the tracked bug; when we

consider bugs tracking patches, actually each and every single patch

submission (not the reviews sent by people using a reply-to) do have a

different subject.

When searching for "subject:" it would be useful to have a speficic

message number and subject along with (or in place of) the bug title.

Using the search example above, a more useful result would be:

Toggle snippet (17 lines)

giovanni@roquette [genv]\: mumi search subject:zoneinfo

#31484 [PATCH] gnu: icu4c: Patch zoneinfo directory.

opened on 17 mag 2018 14:58 by Christopher Baines

#57448 ? [PATCH 0/5] gnu: exa: Update to 0.10.1.

opened on 27 ago 2022 12:09 by ???

[PATCH 4/5] gnu: rust-zoneinfo-compiled: Update to 0.5.1.

sent on 27 Aug 2022 12:10 by gyara

#58614 ? [PATCH 000/187] Remove unused crates

opened on 18 ott 2022 22:18 by Efraim Flashner

[PATCH 185/187] gnu: Remove rust-zoneinfo-compiled-0.4.

sent on 18 Oct 2022 22:20 by Efraim Flashner

I'd also add a blank line to have clear results also with "BW" consoles.

A similar addition would also be useful in the web interface, also

having a link to the message corresponding to the searched subject,

like:

[PATCH 185/187] gnu: Remove rust-zoneinfo-compiled-0.4. -> https://issues.guix.gnu.org/58614#184

Is it doable?

WDYT?

Thanks! Gio'

[1] https://debbugs.gnu.org/server-control.html

Giovanni Biscuolo

Xelera IT Infrastructures

Giovanni Biscuolo wrote on 10 Sep 2023 16:23

bug 65809

Recipients:(address . control@debbugs.gnu.org)

Message-ID:87zg1ucdjn.fsf@xelera.eu

retitle 65809 mumi: Add msg number and subject in search results when searching for subject:

severity wishlist

Arun Isaac wrote on 17 Sep 2023 12:48

Re: bug#65809: mumi: Add msg number and subject in search results when searching for subject:

Recipients:

Message-ID:87ttrtt6rz.fsf@systemreboot.net

Hi Gio,

Sorry for my late reply. I have been travelling the last week and am

just catching up on all my email.

Toggle quote (3 lines)

> When searching for "subject:" it would be useful to have a speficic

> message number and subject along with (or in place of) the bug title.

This is actually difficult to do because of the way we index issues as
Xapian "documents".

First, a quick Xapian primer. Xapian has a bunch of documents each
associated with a set of terms. When a search query comes in, Xapian
decomposes the query into a list of terms and retrieves documents that
match those terms.

In our case, we index entire issues as Xapian documents; we don't index
each individual email message as its own Xapian document. This means
that an issue is the smallest unit we can address. We cannot address
each individual email message. So, localizing a subject to a specific
email message is difficult.

Maybe what you are looking for is some context in the search results to
know why that particular search result was produced. This can be done by
displaying a snippet of text from the issue with the search terms
highlighted. For a working demo of what I mean, see for example,
https://issues.genenetwork.org/search?query=database&type=all. Notice
how the search term "database" is highlighted in the search
results. This is relatively easy to do with Xapian, and indeed I do plan
to implement this at some point.

WDYT? Would this meet your needs?

Regards,
Arun

Giovanni Biscuolo wrote on 18 Sep 2023 17:36

Recipients:

Message-ID:871qev5w8k.fsf@xelera.eu

Hi Arun,

Arun Isaac <arunisaac@systemreboot.net> writes:

Toggle quote (2 lines)

> Sorry for my late reply.

No problem: async! :-D

[...]

Toggle quote (3 lines)

> In our case, we index entire issues as Xapian documents; we don't index

> each individual email message as its own Xapian document.

Ooh, I understand now!

Toggle quote (4 lines)

> This means that an issue is the smallest unit we can address. We

> cannot address each individual email message. So, localizing a subject

> to a specific email message is difficult.

Yes, I see.

Toggle quote (6 lines)

> Maybe what you are looking for is some context in the search results to

> know why that particular search result was produced. This can be done by

> displaying a snippet of text from the issue with the search terms

> highlighted. For a working demo of what I mean, see for example,

> https://issues.genenetwork.org/search?query=database&type=all .

Oooh: a live example is more than a thousand words: thanks!

(I'm following Tissue but someway I missed that feature)

Toggle quote (4 lines)

> Notice how the search term "database" is highlighted in the search

> results. This is relatively easy to do with Xapian, and indeed I do

> plan to implement this at some point.

OK: can we consider this bug report (wishlist) as the "official" one for

that feature? :-)

Can I retitle it to better reflect the upcoming implementation and

assign it to you?

Actually I dont' know if there is some written or unwritten convention

in Guix or GNU about bug assignment, I don't want to put pressure on

you!

Toggle quote (2 lines)

> WDYT? Would this meet your needs?

Yes, absolutely yes: thank you!

Happy hacking! Gio'

Giovanni Biscuolo

Xelera IT Infrastructures

Giovanni Biscuolo wrote on 18 Sep 2023 17:42

Recipients:(address . control@debbugs.gnu.org)

Message-ID:87y1h34hfb.fsf@xelera.eu

retitle 65809 mumi: Add context in search results when querying for (subject:<something>)

quit

As explained by Arun Isaac my feature request was not implementable, he

proposed a slightly different feature to give similar results.

Thanks!

Giovanni Biscuolo

Xelera IT Infrastructures

Arun Isaac wrote on 18 Sep 2023 21:56

Recipients:

Message-ID:87fs3btfue.fsf@systemreboot.net

Toggle quote (7 lines)

>> Notice how the search term "database" is highlighted in the search

>> results. This is relatively easy to do with Xapian, and indeed I do

>> plan to implement this at some point.

> OK: can we consider this bug report (wishlist) as the "official" one for

> that feature? :-)

Sure!

Toggle quote (3 lines)

> Can I retitle it to better reflect the upcoming implementation and

> assign it to you?

Yes, please!

Toggle quote (4 lines)

> Actually I dont' know if there is some written or unwritten convention

> in Guix or GNU about bug assignment, I don't want to put pressure on

> you!

No problem! I do intend to implement this feature at some point
anyway. Even if I don't do it, it's good to list this as an issue so
that someone interested can try and hack on it.

Giovanni Biscuolo wrote on 19 Sep 2023 08:37

control commands

Recipients:(address . control@debbugs.gnu.org)

Message-ID:87sf7a4qij.fsf@xelera.eu

owner 65809 Arun Isaac <arunisaac@systemreboot.net>

quit

Arun do intend to implement this feature at some point.

Thanks! Gio'

Giovanni Biscuolo

Xelera IT Infrastructures

Felix Lechner wrote on 8 Feb 19:09 +0100

(no subject)

Recipients:(address . control@debbugs.gnu.org)

Message-ID:87h6ii6d58.fsf@lease-up.com

reassign 65858 mumi
reassign 65809 mumi
reassign 49295 mumi
reassign 64833 mumi
reassign 54204 mumi
reassign 68920 mumi
reassign 55765 mumi
reassign 65923 mumi
reassign 63507 mumi
reassign 60226 mumi
reassign 63936 mumi
reassign 60951 mumi
reassign 66027 mumi
thanks

Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 65809@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it

mumi current 65809

Then, you may apply the latest patchset in this issue (with sign off)

mumi am -- -s

Or, compose a reply to this issue

mumi compose

Or, send patches to this issue

mumi send-email *.patch

is:open	open issues
is:done	closed issues
submitter:<who>	search issue submitter
author:<who>	search by message author
date:yesterday..now	search by issue date
mdate:3m..2d	search by message date