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

แชร์
ฝัง
  • เผยแพร่เมื่อ 8 มิ.ย. 2024
  • Spoiler alert: I'm not the biggest fan of using namespaces.
    Using namespaces in Logseq can be very tempting to structure your data in a familiar way, but they tend to be unhelpful and restrictive in the long run.
    In this video, I'm going to break down how they are useful and how my approach to using namespaces has evolved. I'll share some practical ideas for where you can use namespaces in your own database, but also draw attention to their drawbacks.
    LOGSEQ MASTERY COURSE
    ───────────────────────────────────────────────────────────
    Master note-taking in Logseq to finally get value from your notes 👉🏼 www.logseqmastery.com.
    Use your time and knowledge productively and become a Logseq superuser in hours, not months. I've built out a structured approach to learning and mastering Logseq from the bottom-up, so that you don't need to navigate through a bunch of different TH-cam tutorials. There's a wealth of resources, videos, and diagrams to smooth your transition and quickly master Logseq's block-based outliner approach.
    UNLOCK TANA COURSE
    ───────────────────────────────────────────────────────────
    If you want a structured approach to learning Tana in order to organize your information and get mental clarity, take a look at my course: www.unlocktana.com. It's your shortcut to streamlining your digital life without getting lost in unnecessary complexity.
    If you're looking for more free Tana related content, take a look at my other channel @CombiningMindsTools
    RESOURCES
    ───────────────────────────────────────────────────────────
    Adding custom CSS to Logseq: www.logseqmastery.com/blog/ad...

ความคิดเห็น • 20

  • @JustinSCampbell
    @JustinSCampbell 5 หลายเดือนก่อน +2

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

    • @CombiningMindsPKM
      @CombiningMindsPKM  4 หลายเดือนก่อน

      Glad to hear little snippets like this can be valuable

  • @yohanesliong4818
    @yohanesliong4818 4 หลายเดือนก่อน

    Very informative. Thank you

  • @alxlg
    @alxlg 8 หลายเดือนก่อน +6

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

    • @CombiningMindsPKM
      @CombiningMindsPKM  8 หลายเดือนก่อน +3

      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
      @alxlg 8 หลายเดือนก่อน +1

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

  • @Siferiax
    @Siferiax 8 หลายเดือนก่อน +4

    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
      @CombiningMindsPKM  7 หลายเดือนก่อน +1

      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
    @Roy.Abhishek 8 หลายเดือนก่อน +1

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

    • @CombiningMindsPKM
      @CombiningMindsPKM  7 หลายเดือนก่อน +1

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

    • @Roy.Abhishek
      @Roy.Abhishek 7 หลายเดือนก่อน +1

      ​@@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?

  • @user-wh7hi6ke9e
    @user-wh7hi6ke9e 6 หลายเดือนก่อน

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

    • @CombiningMindsPKM
      @CombiningMindsPKM  6 หลายเดือนก่อน

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

  • @philippneukomm
    @philippneukomm 8 หลายเดือนก่อน

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

    • @CombiningMindsPKM
      @CombiningMindsPKM  8 หลายเดือนก่อน

      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
      @philippneukomm 8 หลายเดือนก่อน

      @@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
    @voldefox 8 หลายเดือนก่อน +1

    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
      @CombiningMindsPKM  7 หลายเดือนก่อน +2

      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.

  • @eliocjr
    @eliocjr 19 วันที่ผ่านมา

    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.