obsidian-omnisearch VS minisearch

Mobile Document Scanning using QuickScan iOS app and OCR search with Omnisearch and Text Extractor: I was a power user of the Scannable app by Evernote for capturing scans of receipts and documents, so moving on from this was going to be tough. But QuickScan has the same functionality (OCR scanning) and has quick outputs to where my scans are stored in my Obsidian folder. Using Omnisearch, searching my scans feels just as intuitive and snappy as what Evernote used to feel like for me.

In the past I have used Omnisearch which I have found to be an improvement.

https://github.com/scambier/obsidian-omnisearch

Combine this with my favorite Obsidian search plugin Omnisearch and you end up making this bunch of random chat threads useful - now I can link and tag across, and source them for new ideas.

The Omnisearch plugin might be what you need. No AI but weighted results depending on where your query words are found (filename, titles, frequency...). It works well for me, it's my primary way to find notes.

The tag system works well for GTD workflows and organization in general. Default search isn't the best but the Omnisearch plugin fixes that.

Also - and speaking about plugins in general - the best way to get an issue resolved is to ask it on the GitHub page. If the plugin is maintained, its developer will usually gladly help you solve your problem :) https://github.com/scambier/obsidian-omnisearch/issues

I think Obsidian Omnisearch can help you with that.

The Omnisearch plug-in for Obsidian does search in PDFs and images via OCR.

In my opinion it is absolutely possible. The developer of the Omnisearch plugin now works on PDF indexing - https://github.com/scambier/obsidian-omnisearch/releases/tag/1.6.5-beta.3.

I wrote an online catalog a while back (and I need to get back on adding graphics and products at some point). It’s written using Eleventy and the minisearch library. The source and data are available on Github if you want to see how I did things. I’m not a professional web designer either, but it was a fun project.

You could have a look at https://github.com/lucaong/minisearch/

If you're dealing with thousands of records or less, searching titles and summaries rather than long bodies of text, I recommend looking into client-side solutions. Nothing beats the responsiveness of search-as-you-type entirely on the client side. It can be fairly sophisticated fulltext search. For example, I've built had great success with MiniSearch.

I quite enjoy minisearch[1] which is also 0 dependencies, actively maintained, and I expect would work well in a worker environment. I dropped it into a service worker and plugged it with a simple point in polygon script to enable geosearch for a recent project[2] and it played v. nicely.

[1] https://github.com/lucaong/minisearch

No magic here, the underlying engine is Minisearch, which uses the BM25 algorithm (the de facto standard among search libraries). Omnisearch adds a magic sauce during indexing by converting notes into custom objects, with the following fields: - body (the plain markdown text) - filename & yaml aliases - level 1 headers - level 2 headers - level 3 headers

It's actually really simple! Minisearch did most of the heavy lifting so all we needed to do was the crawling, storing and UI etc. I'd check that out if you're interested in the search part!

We use MiniSearch for searching, while fast-fuzzy is used for highlighting of detected search terms.