Search Service 'General Document Indexer' for Document Retrieval

[CallmeT-ty]

Wouter suggested implementing a search endpoint to facilitate document lookups within Switchboard, potentially filtered by document model type and title, streamlining user interactions in UI for linking documents.

wouter:

let's call the "Search Package" instead "General document indexer". This is one of the read models.
Nice to haves:
Clean up / iterate on the read model plugin architecture when implementing the general document indexer.
Creating an example of a read model using the analytics engine, merging in goldenmule's work.

• Subgraph on /driveid/search
• Subgraph offers a GraphQL query to search through documents
• Document ID's & titles as search target. (Objects will come later)
• Search query accepts a query string.
• The resolver looks into the database for entries and returns a list of search results
• Search results contain a DriveID, DocumentID and a title of the document. (todo-list)

We'll need an internal listener that listens to changes of all drives and listeners to add_file, update_node, delete_node ,update_file, (add_folder?)
The listener creates or updates an entry in the database.
A readmodel that should have a full text database?

How will this fit in the demo? What do we show on front end?
Could we repurpose the search bar in connect? (to be seen)
It's a combobox that we could implement via chadcn

Search typing, makes initial query, search what you typed, updates what you retyped (debounced necessary)

Connect will interact with a switchboard remote instance. in case user was offline it would search in it's local drive.
It could do the remote results later.