Vary search results based on current resource

[jg10-mastodon-social]

As a PodOS browser user, search results I am looking for may be different if I search from my dashboard page or within a specific container.

This becomes increasingly the case as the number of indexed items increases, e.g. the term "movie" might appear in a to-do item, receipt, movie index, movie name, blog title, url path etc.

As a user, if I am currently looking at a to-do item, I would expect that search results would prioritise matches that are to-do items.

This is an elaboration issue to explore options for addressing this use case.

[jg10-mastodon-social]

#36 is a possible solution to a narrower use case where an app creator using PodOS elements wishes to limit the search index

[jg10-mastodon-social]

Lunr.js boosting could be used to give higher weight results that share the current container path, e.g.

https\\://current/path/*${escapedTerm}*^200 ${escapedTerm}^100 ${escapedTerm}*^20 *${escapedTerm}^10 *${escapedTerm}*^5

Tests would need to be developed and suitable weights identified.

e.g. test

PodOS/core/src/search/SearchIndex.spec.ts

Line 51 in 7e2f8bf

it("exact match is the first match, even if others are similar", () => {

[jg10-mastodon-social]

Github's approach is to generate editable search terms that restrict search scope, e.g. repo:pod-os/PodOS or org:pod-os.

The same could be done to restrict search to containers, though resource URLs tend to be fairly long and unwieldy and editable search terms are perhaps better suited to power users.

[jg10-mastodon-social]

When at the dashboard page, shorter paths are likely to be preferable, e.g. linking to an index page rather than to an individual item.

Edit: A document level boost could be applied when the search index is built, either based on container nesting or specified in the label index by the user.