Feature Requests

MOTIVATION: I'm a recovering metadata nerd. I studied it in grad school. In many ways, connections between nodes are more important than the nodes themselves. Right now, the knowledge graph does an amazing job at node management, but connection management can be improved. If this is done correctly, it will accelerate insight generation and improve user experience. REQUEST: Add an automated connection summary between two or more nodes. This can be placed directly in a connection card or elsewhere. Rather than limiting summaries to just nodes, treat connections as important by giving them summaries as well. As a user, I can see the connections between nodes, but they I am still forced to investigate those connections manually. I propose that the knowledge graph adds treats relationships as first class entities. SOLUTION: Users should be able to interact with connections directly. Just like how a user can click a node, they should be able to click a connection. This will reveal a panel just like the panel for nodes. The difference is that this panel will provide detail on the nature of the connection itself. Users should be able to save and manage connections. This is particularly useful when using the "pathfinder" feature. The summary will compile each connection summary and rapidly overview the relationship between the starting and ending nodes. IMPLEMENTATION: It feels like the knowledge graph is currently designed around RDF triples, which deprioritizes relationship fidelity. I recommend leaning further into the property graph approach. The graph already utilizes this to describe [NODE] <-out/inbound-> [NODE] connections. However, by giving the connections priorities too, users will gain more insight. This can be done by shifting to a [SUBJECT] <-predicate-> [OBJECT] connection view to provide semantic context. Here's the difference spelled out in an example: (Current State) Node Relationship: [Richard Hamming] references-> [Bell Labs] [Bell Labs] <-is referred to by [Richard Hamming] (Future State) Semantic Triple: [Richard Hamming] was employed by-> [Bell Labs] [Bell Labs] employed-> [Richard Hamming]

When selecting two nodes for the pathfinding feature, the user still needs to click through each node to explain nature of the path. It would be helpful to produce an automated summary of the path and save that as its own metadata entity.

Hello! I love the knowledge graph. I'd love to see a "content gap" or "knowledge gap" feature. Other tools like InfraNodus prioritize highlighting content gap analysis as a way of driving insight and new perspectives on a topic. https://infranodus.com/docs/content-gap-analysis Whereas Recall pathfinder mode is "brute forcing" a connection between nodes, there isn't a content gap-centric mode.

I thought of this after I responded to the beta testing email for the knowledge graphs. I was wondering if it would be feasible to create new connections between cards directly from the graph view. Since a common use case for using the graph view is to find connections between cards that you may not notice otherwise, I thought this might be useful. What I was thinking was if you right click on a card in graph view the system would allow you to drag a line between that card and another card that is not connected. Then the cards themselves would be updated with the connections/backlinks.

I want to be able to create a connection from a paragraph, or sentence. For example if I have a sentence/paragraph that references a set of stats quoted in a book, I would like to be able to add a connection to the whole relevant section. Right now if I try this the connection searches for the the whole paragraph and comes up with nothing and I cannot edit what is bing searched for.

Cards should be linked even when articles or notes are in different languages. For instance Alexander the Great should be considered identical to Alexandre le Grand.

I would like to move around the blocks in my mind map, to isolate the topics in an empty space to and remove the background clutter without losing the connecting nodes, like in obsedian.

I read this awesome Co-founder guide on the recall docs page: https://docs.getrecall.ai/use-cases/the-co-founder-guide-to-recall I went to try organise my connections but found that I needed to manually edit each connection. Let me bulk edit the knowledge graph!! And bulk edit connections on each card.

Enhancing Connection Features in the Recall App While quick and easy connections are the core functionality of the Recall app, there are several areas where the user experience could be improved: 1. Toggle for External References : When creating new connections by highlighting text and using the ⚡ button, the dropdown menu should include a checkbox option to enable/disable external references like Wikipedia. This would allow for faster loading and decluttering the options when users only need internal references. 2. Flexible Search Functionality : The search function for connections should be term-order agnostic. For example, searching for "important card" or "card is important" should both return results containing those terms in any order, such as a card titled "this card is an important one". 3. Automatic Connection Suggestions : When reading a card, there should be a "Propose Connections" button that automatically highlights potential connections to previously created cards. Users could then simply accept or reject each suggestion, streamlining the connection process compared to manually adding each connection with the ⚡ button.

Add support for block references — the ability to reference and embed specific blocks (paragraphs, bullet points, or sections) from one card into another.