How to use properties and templates in Logseq
ฝัง
- เผยแพร่เมื่อ 2 มิ.ย. 2024
- Learning how to use properties and templates will help you be more effective in managing knowledge in Logseq. In this video, I go step by step through the different aspects of using properties and templates to help you get started using them in Logseq.
For those interested in accessing the early version of the Logseq Mastery updates graph, here's the link: www.logseqmastery.com/updates. Feel free to reach out with any feedback 🙂
📚 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.
⏲TIMESTAMPS
───────────────────────────────────────────────────────────
00:00 - Introduction
01:46 - What are properties in Logseq?
02:19 - How do properties work?
04:51 - How do I create properties in Logseq?
08:42 - Block properties vs page properties
11:35 - Potential errors with properties
13:42 - Significance of properties
18:26 - Useful page properties to know about
21:20 - What are templates and why would you use them?
22:46 - How to create, use and edit templates in Logseq
25:03 - Adding a template to your Daily Journal page
26:04 - What makes for a good template in Logseq?
🎈 SUPPORTING THE CHANNEL
───────────────────────────────────────────────────────────
If you've found the videos useful and would like to support the channel, sharing the video with a friend who might find it useful is much appreciated. 🙏🏽 If you'd like to contribute financially to support further video creation:
☕ Ko-fi 👉🏽 ko-fi.com/combiningminds (no fees, and allows for monthly contributions)
📚 If you're looking for great book summaries, look no further than Shortform. If you use my affiliate link 👉🏽 shortform.com/onestutteringmind you'll get 20% off an annual membership, and support the channel financially in doing so. 👍🏽
🌲 All these links and additional affiliate links are available at: linktr.ee/OneStutteringMind
This is a masterpiece tutorial. And without mindless, distracting background "music" so prevalent in videos. Thanks.
Glad you liked it :) Thanks for the feedback
aliases are also great to provide translations for terms if you are speaking multiple languages
Hi Dario, thank you for this awesome explanation on logseq properties, especially the highlight on the distinction between page properties and block properties.
Glad it was helpful Athanassios :)
Thank you Dario for such a terrific tutorial! You're my main reference in my journey to mastering Logseq. I started using it for building my Zettelkasten workflow and your help has been invaluable. Warmest regards from Nicaragua.
Glad I could help! 🙂
Thank you Dario for this update on properties and templates. This was a very well done update on your earlier content.
Thank you :)
I enjoy your lessons more and more.
Thanks so much Krzysztof :)
This as an awesome refresh on properties. Thanks a million Dario!
Hi! Very good explantiono, But I have one question. If I define a template with some page properties in it and the properties in the template are empty, so, if I use the template there is no pull down menu with all already defined property values to choose them. Instead I have to use ::, then choose the property and at least one of the existing values. But this counteract the sense of templates if I have to new define each property and choose the value. 😞
love the explanation. Well done.
Thank you :)
Thank you, Dario, that’s a useful update. I also use daily journal pages to ingest new content (the alternative of consciously filing everything in pages just recreates the analogue folder problem) but I was too lazy to perfect the advanced queries needed to retrieve and filter stuff. However, I can see from your demo that a couple of block properties provide enough structure to retrieve anything via simple table queries and {filter} 🚀
Glad to hear :) Hopefully the advanced query builder comes soon!
Dear Dario, you are such a great explainer. It would be so helpful if you extend your expertise to tana as well. Thank you also for your great logseq course. It is worth every cent.
Thanks for the kind words Judith. I am looking at potentially doing some content on Tana, although at the moment I'm thinking it might be on a different channel
Good stuff 👍
Thanks 👍
Very nice
Thanks :)
Thanks for this video - I definitely learned some new things. One area where I am still not entirely clear: you mentioned not wanting to create new pages and "polluting" your graph. But, I believe you still made [[links]] out of the properties.
Also, I thought Logseq made properties into pages by default (unless one turns this off in their .EDN config file). Or am I conflating block properties and page properties.
If Dario or anyone else could shed some light on what advantages one gains by using block properties over tags, I would be very grateful!
Hi Zach - It's a case of rather creating pages for concepts as aggregating points, rather than creating unnecessary pages to hold content.
Logseq used to auto-create the pages (it still does for the 'tags::' property), but this behaviour has changed
thanks for this great tutorial. I wanted to ask: there is a way to hide block properties when I visualize a block? It would be great to see only the block without the properties and be able to see properties only if I need to see them
Thanks 🙏🏻 Unfortunately none that I know of or use (I'm sure some people use CSS to do this though...)
Thank you Dario, this concept is so intuitive. One thing that I have used is a comma separated list in a property in the past, so if John lived half the year in Australia and half the year in Ireland I would be inclined to put the property lives-in as [[Australia]],[[Ireland]] so rather than 'subject, predicate, object' it would be 'subject, predicate, objects' - this is actually very useful when defining the areas / groups / expertise within which you interact with a person (whose record this would be). Is this still possible and is there any special syntax that needs to be adopted - I must admit to being bewildered by { and ( and [[ and just a plain ,
Thank you for your selfless journey since I first encountered LogSeq which has been an insightful help as I have bumbled my way to a (mostly) useable Graph!
Thanks for the kind words Kevin. I'm glad that your Logseq graph is mostly useable :)
Your 'subject, predicate, objects' does indeed work. And plain commas are fine, I just like having backlinks there to make sure I can retrieve the information down the line.
Thank you Dario. This introduction is useful. But I am wondering what is the use case to apply property in the page or in the block? For example, we have inputs like paper, article, blog, video and book. Or, it doesn't matter if we can change query for these two types.
I'm not sure I understand your question.
Page properties theoretically give you more querying abilities if you can use advanced queries. This isn't really my forte though.
I maintain a contacts database on airtable
Can I sync columns of airtable as properties in logseq.
Is there a way to do it via api
I haven't looked into this unfortunately. It might very well be possible given the robustness of Airtable's API, but beyond my abilities as a coder for now.
How do you enable the cool icon pack that you seem to have ?
It's just the Windows 10 icons :)
@@CombiningMindsPKM Aaha...problems of mac user :)
New user, quick question - I have been placing block properties as the first child to the block they are intended to reference, which felt natural (given how page properties work)... can you explain why this approach is incorrect? (Also, thanks for your content, really helping me get started with logseq)
AFAICT the issue is that the child properties is the only thing that displays on linked references by default... why is this bad? It seems to create a more compact view in linked references than if I make the props part of the the parent block. That said, I'm still wrapping my head around the idea of using linked references, and as a new user it seems like an overwhelming amount of information... but this might just be my smooth brain coming from Notion talking...
Example:
* block 2
** prop2:: val2
I think I did answer it in the video (or somewhere else, maybe the course) but if block properties are indented underneath a parent block, they no longer belong to the parent block. They then belong to the child block. Took me a while to get my head around this, admittedly.
How to edit a template? Thanks
Just edit the blocks underneath the parent block that has the template property
It's covered in what?
Oh wow, got to the end. That looks interesting!
Glad you found what you were looking for :)
The disadvantage is that Logseq becomes slower and slower the more properties you add. Why one means in the face of these speed losses, nevertheless not to implement everything into a database (and to hold on to the incomprehensible Datalog), Logseq can cost now nevertheless the one and the other user, because Tana fetches at present the users to itself. Also, if you look at how fast Obsidian starts with exactly the same files, it's demoralizing. I have always appreciated Logseq and stayed with it until today, but it really costs me effort to still stay there and I really want to leave, because it also can't be that this becomes a permanent beta for years. I've been paying Opencollective long enough now and the iOS app either can't parse the URL or can't find the Vault and stories like that. It's getting really embarrassing.
I haven't experienced a slow-down due to properties, but maybe I'm just used to the slowness now 🤷🏼♂