Logseq Namespaces - How to use (or not use) them

[@JustinSCampbell]

Seriously, the suggestion to do this, building a second brain (book), was a game changer for me.

[@CombiningMindsPKM]

Glad to hear little snippets like this can be valuable

[@alxlg]

FYI the plugins Favourites Tree and Hierarchy Jump can complement the namespace hierarchy with one defined using a property, like tags:: or parent::.

[@CombiningMindsPKM]

Awesome, thanks for the heads-up. I hope that this becomes standard, rather than having to use a plugin. But for now I guess that's a win.

[@alxlg]

@@CombiningMindsPKM I agree, there are so many low-hanging fruits to unleash much more power from Logseq...

[@yohanesliong4818]

Very informative. Thank you

[@Siferiax]

The more I've learned about Logseq the past year, the more I've moved away from namespaces. Page titles can become quite unruly. My general rule of thumb for myself is now to ask "does it make sense to have the parent in the page title?" Outside my use of namespaces to make an easy index on my website, I only use it for one specific case, my notes of the D&D campaign I ran. As the page title "Notes session 1" makes no sense without the name of the campaign in there. All more general linking and such I use properties for. They are so much more flexible. Especially with a bottom up approach.

[@CombiningMindsPKM]

Indeed, most of the namespaces in my database are older. I wish there was a query which showed all the namespaces you've used, that would be cool. Properties are really powerful! I hope Logseq formalizes some sort of "instance-of" or "type" property. This will be a huge step forward towards Tana-like functionality.

[@Roy.Abhishek]

16:36 Thank you so much for this beautiful video. Are you using the same vault in both Logseq and Obsidian?

[@CombiningMindsPKM]

Thanks Roy. Yep, I'm using the same vault in both :)

[@Roy.Abhishek]

​@@CombiningMindsPKMThank you for your reply. So I was wandering, do you use any plugin to make the process seamless? Because as I understand, the blocks from logseq have logseq meta-data, does it not appear in the notes in Obsidian?

[@MatteoOrefice-t4e]

Hello can the properties have namespace ? ie: write prop/mine:: value

[@CombiningMindsPKM]

I just did a quick test and it seems to work, but not sure how robust it will be long term

[@philippneukomm]

Dario, you didn't told us how to make these buttons in custom.css 🙂

[@CombiningMindsPKM]

Whoops , thanks for the heads up! Just added the link in description. Here it is again though: www.logseqmastery.com/blog/adding-custom-css-to-logseq

[@philippneukomm]

@@CombiningMindsPKM thanks! Found it already 👍 But I didn't find the right custom.css code to make it look like you did in the video. Do you mind to show me the right code only for the button design? It doesn't have to be filter-specific like you did only the design itself.

[@voldefox]

2:38 you say "not so nice from a longevity perspective", then why do you use Tana, which is cloud-only and the data are exported in a way that can't be used by any other format, so if Tana is abandoned one day, all our data wull be lost?

[@CombiningMindsPKM]

I'm only really using Tana for project management and some systems building. Most of my information is still in Logseq. Despite that, I think Tana are doing great work in building export functionality (to Markdown), and they're not a Mickey Mouse startup that's going to be abandoned willy-nilly.

[@3c4j]

This namespacing problem could be easily fixed if logseq introduce a simple folder structure. This is available in ALL operation systems and any online storage like google drive. Theres absolutely zero reasons to not support it in pages.

[@CombiningMindsPKM]

It would be a nice addition.