Backlinks and Search - Display Information based on hierarchical document structure (bullet list level or enclosing header breadcrumbs)

[Nikdotca]

I noticed that toggling “show more context” allows me to see nested items but not items at a higher level of hierarchy. This results in missing context. This could be solved with the above solution (although it would require users to add headings where they might not otherwise have done so).

An example, coming from Roam:

On my daily note page of [[2021-09-28]] I might have the following

[[Hawaii trip]]

• Going from [[2021-01-01]] to [[2021-01-08]]
  • Bring a baiting suit

In Roam when I look at my backlinks for [[2021-01-08]] I see:
[[Hawaii trip]]

• Going from [[2021-01-01]] to [[2021-01-08]]

I also get an indicator that there is further nested context and can expand to see “Bring a bathing suit”

In Obsidian I see:
[[2021-09-28]]

• Going from [[2021-01-01]] to [[2021-01-08]]
  • Bring a baiting suit

Is there a way of automatically exposing “[[Hawaii trip]]” in the backlink without having to manually tap on the little “show more context” up arrow?

[fcand1]

Thanks I just had the same problem.

Is there any news on this issue? For me, the backlinks often are useless right now. I also have to Roam/Logseq concept in mind. Or do I miss something?

[mmplx]

This is a feature in logseq and it makes such a difference. It’s understandable because logseq works with hierarchies of blocks, but a breadcrumb of headings could fulfill a similar role in obsidian.

[caHerrera]

Yes, looking forward to seeing something like this in Obsidian

[mrkuramoto]

First, I love Obsidian, and I respect the Developers putting in thousands of hours to run the software

I’m a daily notes user, and I try to use it as much as possible, but the way Obsidian returns the backlink results when “Topics and Subtopics” are used represents a problem.

In this example, I’m trying to see all the movies performed by Matt Damon, but the result is useless. It is possible to see the actor and the date but not the movie’s name which requires to open each file to see the name of the movie

Roam Research, which I know works in a different way (not plain text/markdown files?), can bring the three needed information:

• 01 - Bullet
• 02 - Sub-bullet
• 03 - Date (filename)
• 04 – in the case of Roam, it brings the page and all the related back-links

Which is interesting, making a test with Logseq, accessing the same Obsidian database, it can bring the three information

I’m aware of the “dataview” plugin but it requires building the information in a fixed structure to work properly using YAML or using “::”

In this example using Will Smith, the first move is inside a daily note, but the second had a dedicated page, and Roam could bring both.

And LogSeq also, accessing the same Obsidian database.

questions:

• Is there any workaround to retrieve the information from Obsidian the same way as Roam Research and Logseq? (maybe using Logseq together with Obsidian?)
• Am I doing something wrong and could already be taking advantage of Obsidian’s full potential?

• the movie example maybe sounds silly but I had used them just as an example. I face the same issue everyday with work subjects.

[mrkuramoto]

Using Logseq together with Obsidian and very satisfied with the result - Logseq accessing the very same Obsidian database

[mrkuramoto]

I think Obsidian is very close to be able to return the block name as LogSeq.
Here an example of block reference. Obsidian now brings the block perfectly, with the block name and all the sub-bullets. I think the reverse, when we tag or add a wikilink in a sub-bullet is something similar. Nowadays I have been using LogSeq as an workaround but I cross my fingers, everyday, for Obsidian. I think this is the only limitation Obsidian has comparing to “competitors”

[mrkuramoto]

I think this subject is very sensitive among Obsidian users or, better, Obsidian culture. I’ve seen other topics like this and, like mine, no single comment.
I’ve heard that Roam Research, which has an imposing treatment of each bullet, was built based on another kind of system, and Obsidian was born based on markdown files, focusing on the file, not bullets. This explanation was faithful up to LogSeq. In my case, LogSeq is accessing the very same database as Obsidian, but Logseq can deal with “parent bullet” and “Children bullet.” efficiently.
Maybe someone is questioning: why does this guy just move to Logseq? (Obsidian Culture). Because I love Obsidian, and every day, I cross my fingers and check for updates, which would solve this limitation.

[gobbletown]

+1

Just a friendly show of support from a fellow anti-dogmatist…

You’ve stepped on what seems to be the crux of the disconnect (puns) between Obsidian and other PKM’s like Logseq.

It seems to be the level of resolution or granularity in the definition of information nodes.

That is, Obsidian resolves to the “.md” files as its linkable nodes.

• The level of granularity is set by the tool (dogma/opinionated) and not the user, with plug-ins and friction as the answer to increase resolution.

Where Logseq resolves to any intra-file datum, files, blocks, tags, links, link types, etc. as its linkable nodes.

• The level of granularity is defined by the tool-user (unconditioned) and limited more appropriately by use case set by the user.

I similarly cross-fingers and say prayers to teh PKM Gods to help Obsidian break free from its chains of opinionated anti-opinionatedness…

And I penitently ask the community’s forgiveness for my continual blaspheming and rabblerousing…

(truly do luv this community tho)

~Gobs

My latest transgression:

Add support for link types

Any news in this area Dear Obsidies? Still pining away for some flavor of functional disambiguation… It must’ve felt similar to the early adopters of the motorized carriages back before cars replaced horse and buggy as the more robust or advanced means of transportation… Bah Humbug… These hippies and their fancy ‘link types’… Silly fad I tell ya! Why, back in my day… We had to manually connect each little data giblet… By hand [right-click]! Uphill both ways [bidrectionally], in the snow,…

[mrkuramoto]

Please see an update about this subject… an plugin called Influx can do the job… I think is just a matter of “want to”…

Backlinks - return information based on hierarchical structure (bullet level indentation) - Feature requests - Obsidian Forum

[mrkuramoto]

First, I love Obsidian. I have been using it for quite a while, and it is the first program I open in the morning and the last I close at the end of the day.

I migrated from Roam Research, and I always heard that Obsidian does not return the backlinks as Roam due to its nature. Roam’s structure is a “blocks” concept, while Obsidian’s structure is a “page markdown.”

To illustrate, an elementary example → It is possible to see the child block with the link, the name of the file (date) but the parent block is missing. In this silly example, to see the name of the movie, I would need to open link by link.

Then Logseq appears. Logseq accesses the same database as Obsidian and can return the information from the backlinks exactly as Roam Research. I have been using both for this reason.

Logseq information:

And yesterday, by chance, I found an Obsidian plugin called Influx that makes possible to get the whole information when a child block has the link.
In this image we have the child (actors), the parent (movie name) and the filename (date)

I use Daily Notes as a backbone of my structure in Obsidian, and this limitation strikes me daily: meetings, projects, ideas, etc.

I wonder why Obsidian does not implement this capability and remove this untrue comparison against Roam Research, Logseq, and other tools.

[dryice]

Hi @mrkuramoto, I’m realising more and more the benefit of logging in the daily note, linking to a page, and then seeing those logs in the backlinks in document.

Because Obsidian is so customisable without a defined workflow, I wouldn’t have realised this until I looked at how Logseq encourages user’s workflow. However I have not used roam or logseq more than superficially.

These days I put information in its own page if it is a core feature of the note subject.

But for journal logging, such as had an interesting conversion with [[Person]] or worked on [[Active Project]] and had this creative idea, I write in the daily note, and use the [[link]]'s inline backlinks core plugin to see how related ideas are taking shape and growing over time .

And in fact, this is much closer to how one would work and write in a paper journal. But with backlinks, organising ideas can be really powerful.

In summary, I would encourage development of the aesthetics of the backlinks in document core plugin.

[mrkuramoto]

Hi @dryice,

Indeed. Daily notes and backlinks are compelling, and the more I use Obsidian, the better it becomes.

The only “but” using Obsidian is how it returns the information from the backlink. I always heard it is due to a natural limitation: Obsidian focuses on a page, and Roam Research on a block.

Then Logseq appears and, accessing the same Obsidian database, returns information like Roam Research.

I couldn’t believe it when I, by chance, found Influx, a game-change plug-in for Obsidian.

The picture below shows how Obsidian returns information from a Daily Note backlink.

and this is the Power of Influx plug-in:

The way Obsidian returns the backlinks information is almost useless for my usage, but Influx has changed everything.

This limitation of Obsidian, for sure, demotivates users to migrate from Roam, Logseq, and other programs to Obsidian because those programs work based on Daily Notes with blocks, bullets, and sub-bullets.
*I don’t know why but I can state that Obsidian wants to have this limitation

[mrkuramoto]

Anything that has achieved great expression has the potential to become something that requires a choice between two paths, becoming something almost religious.
Roam Research has the power to do something better. Still, suddenly, Obsidian, who could have the same capability, decides not to (here, first, I mentioned Logseq and then the Influx plugin).
Most of the people who contribute to this group are already “set” to "what the Obsidian community accepts and end up not adding anything relevant.

It is a shame that Obsidian, who can work very close to Roam, decided not to, and, oddly enough, all the followers just support the decision.

Shame on you supporters…

there is an elephant in the room but all the followers, like in a religion, just decide not to see it.

let’s go simple. let’s respect the work of others. And just implement what is best for the users.

at first I heard that it was a limitation of the text-oriented model and that Roam’s structure was born different. And then Logseq appeared, which accessing the same Obsidian database managed to bring the results like Roam. And then came the “influx” plug in which clearly demonstrated that Obsidian had the ability to return the same information as Roam Research.

But here comes fanaticism, blindness, something that religion defines as basic, and then everyone, from developers to supporters, is ok with that.

Here is the start of the END… if Obsidian doesn’t change it mind, it will die.

this STUBBORNNESS I just can’t understand.

[obsequious]

What have you been smoking?

[WhiteNoise]

This is not a matter of religion. This is a genuinely hard to implement feature because Obsidian works directly on text and doesn’t have an internal outline representation document (bullet level outline)

You have the right to proposes future to the community but please don’t nag.

[mrkuramoto]

I want to apologize for how I expressed myself - I was motivated by my passion for Obsidian and the enormous potential I see in the tool. I was outraged when I saw Logseq returning structured information using Obsidian’s MDs and later when I saw Obsidian’s plugin (Influx) doing the same. If a plugin can do it, why not the app?
@WhiteNoise, you are right. Sorry for that.

[mrkuramoto]

To manifest my gratitude, I’m sponsoring the creator of Influx.

[mrkuramoto]

I apologize. I ended up expressing myself emotionally due to the heat of the matter, but it turned out to be inappropriate behavior.

[linkarzu]

I’m also interested in this feature request (or I think so)
I keep most stuff in my “daily note”, but for long technical documents, like “Kubernetes” for example, I like to keep everything under a single big file (for searching purposes), and then link back to each particular “daily note” to keep a record back in my daily, under linked mentions, of what I did that day.

On my long technical documents, I put a heading, and on a line below, I add a [[daily-note]] link, which only goal is to refer back to my daily. So back in my daily I’d like to see the headings when I click on “Show more context”, but currently I don’t, I recorded a video which explains it better (see below)

The reason I put the [[daily-note]] on a single line below the header, is because I don’t want to put it next to the header, or my outline will will have all of those links and I’d like to keep it clean. I could also copy paste the title on the line below, but if the main title changes, I’d have to change the title below too, no big deal and that’s what I’ll do for now.

Maybe I just have a weird way of doing things, but if it could be implemented it would be great, so I don’t have to be clicking on the “up” arrow to see when I click on the “Show more context” button.

Love Obsidian, moving away from my really slow and search inefficient google drive documentation repo that I’ve been using for years

P.S. Originally I thought this was a bug xD