User story

Someone searches for a rather common term, e.g. "rāga". They get 2610 results:

They need some way to narrow things down. At this point they may decide that the sutta they were looking for is in a particular book, or simply that they would be interested in a result that came from a particular book. For example, they think that they might want a pithy verse, so they would like to narrow it down to the Sutta Nipāta.

Currently there is no way for them to know the distribution for their results or an easy way to narrow them (without investigating the "filter" icon).

Feature description

Add a break down of results per book. Clicking on one of those book names would add the necessary filter to the search and re-run the search.

The DPR has something like this (see top right of screen):

Issues:

• Should there be a threshold of x results before this kind of interface is presented?
• Would every single book that has a result be represented? This could lead to having dozens of books with just one result each.

Acceptance criteria (the list of things that need to be done for the ticket to be considered finished):

Pre milestone planning check:

• Small enough to completed in a milestone.
• Dependencies marked
• No external dependencies block the PBI from being completed.
• Details are understood by dev team to decide if the PBI can be completed.

Done check:

• Produced code for presumed functionalities
• Project builds without errors
• Peer Code Review performed/pull request approved x2
• Project deployed on the stage environment identical to production platform
• Feature is tested against acceptance criteria
• Feature ok-ed by Product Owner (moving to Closed on the Board)
• Refactoring completed
• Any configuration or build changes documented (readme, etc...)