Candidate Backlinks: Feedback on the preview feature #3583
Replies: 3 comments 1 reply
-
I think something else that would be useful for this and provide a more powerful experience would be a way to review all suggested candidate back links rather than just having them all enabled/disabled, perhaps via a doctor command. The idea being that this would help users discover hidden connections in their notes that either they didn't know about, or just that as the vault grew there was the potential for linking to older notes. |
Beta Was this translation helpful? Give feedback.
-
For me this feature only work sporadically, at best. Reload index isn't enough, but creating a hard link will cause the candidate links on that page to show up. After that it works even if I remove the hard link. And then when I follow a candidate link, the wrong part is "linked" for example, In the sample above, when I follow the candidate link to my.new.note from the backlinks, This is what I get: And yes, it would be much better if each "node" of the name was considered independent. Ex. I use "python" then "reference.languages.python" would have a candidate backlink to the note where I typed python. If I typed "I like programing languages" in note1, then reference.language would have a candidate backlink to note1. Also, I should match title or a node in the filename. Unlinked references can be slow in org-roam, but I never had any complaints with the performance. I used the feature a lot when I decided I wanted to split notes... I would split the note, use the unlinked references to find places where the concept was mentioned to create real links. |
Beta Was this translation helpful? Give feedback.
-
thanks everyone for providing feedback. as a reminder, candidate backlinks are a preview feature so there are still many rough edges. some context: we're currently in the middle of switching our metadata backend from a json blob to sqlite. this should provide near instaneous (<100ms) latencies for all operations in dendron. performance has been a major concern for the candidate backlink feature which is why we've been holding out on working on this until we've finished the migration in terms of what we want the functionality to be:
|
Beta Was this translation helpful? Give feedback.
-
Description
I was looking at some issues after trying out Candidate Backlinks today:
I think the functionality currently provided by candidate backlinks could be revisited. I'm not sure if it would make sense for this feedback to become a GitHub Discussion, or potentially an RFC (not a new feature, but quite an expansion of an existing feature), or a series of different feature enhancement requests. So, I created this discussion.
Candidate backlinks definition
Thoughts on current state
Candidate backlinks only seems to work if you use the exact full filename (
this.is.my-note.over-here
), with the dot notation included.Looks like I can get it to work, but only because it is implemented in a very unintuitive/unexpected way:
title
or thebasename
(as mentioned in Find backlink candidates using basename #1059) (basename
beingpython
inlang.python
, I think). I've added a comment to that issue around basename, because it brought up questions for me there, too.Testing out templates.derek.my-note right now
in order for it to appear, so to me this seems like not the most helpful feature at the moment since people would rarely use that notation in the middle of a note (unless that feature is for people who are hesitant to link to an existing note, or hesitant to link to an existing note and just want a placeholder? But I see that as being a really rare situation/workflow to support).How to test out candidate backlinks
dendron.yml
my.new.note
my.new.other-note
my.new.other-note
, type:I'm looking at my.new.note today
my.new.note
my.new.other-note
is listed as a backlink, and if you collapse it, it will show the plug iconDendron: Reload Index
for it to appear.What does an ideal workflow look like?
I feel like ideal scenario would be:
title
value of a note, for example, maybe?)I'm not sure what the demand for this feature is, or would be, or if users would want/expect candidate backlinks to function differently. It seems good, in theory, to become aware of potentially hidden connections across notes. It sounds especially cool if being able to do so in multi-vault scenarios, as a note I've made may now have a candidate link to newly imported notes.
Beta Was this translation helpful? Give feedback.
All reactions