Hi Dario, thank you for this awesome explanation on logseq properties, especially the highlight on the distinction between page properties and block properties.
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.
I can see the utility of both properties and templates. As I refine my database and think things through, I'm sure that I will find applications for both properties and templates. Thanks for a great introduction.
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} 🚀
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
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
Awesome content!! I'm doing a book reading list using the same concept with blocks. If I want to add a property called review, in this example. Can I have logseq to retorn a shorter sentence where I define the maximum length of the paragraph? But I'd like that not messing around the config and CSS file. Is there a property or something else to be defined inside the table? Thank you!
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.
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. 😞
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.
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.
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...
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.
@@CombiningMindsPKM Sorry. I phrased the question sloppily. If the property already exists, to insert it into the block just type "colon" twice and choose it from the menu, after which the list of associated values appears. If I want to change the value without typing it I necessarily have to redo the entire procedure. Is there a way to make the list of values appear again?
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.
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
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 :)
I can see the utility of both properties and templates. As I refine my database and think things through, I'm sure that I will find applications for both properties and templates. Thanks for a great introduction.
Thanks!
This as an awesome refresh on properties. Thanks a million Dario!
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
love the explanation. Well done.
Thank you :)
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
Great video!!
Thanks!
hi, thanks for your videos! can you tell me the procedure the followed to build the online Logseq documentation? or make a video about it??! ;) thanks
ua-cam.com/video/fHc2cVNMNrA/v-deo.html got it!
Here's the link: ua-cam.com/video/fHc2cVNMNrA/v-deo.html
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...)
Awesome content!!
I'm doing a book reading list using the same concept with blocks. If I want to add a property called review, in this example. Can I have logseq to retorn a shorter sentence where I define the maximum length of the paragraph? But I'd like that not messing around the config and CSS file. Is there a property or something else to be defined inside the table? Thank you!
Hmm, don't think so 😑
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 :)
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.
Good stuff 👍
Thanks 👍
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. 😞
Yep, that's one of the unfortunate things about Logseq.
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.
what is plugin with green / yellow dot? it show syncing files in graph?
That's Logseq Sync :)
Very nice
Thanks :)
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.
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 can I change the property value without re-creating the prop?!
It should be as simple as highlighting the text and editing it?
@@CombiningMindsPKM
Sorry. I phrased the question sloppily. If the property already exists, to insert it into the block just type "colon" twice and choose it from the menu, after which the list of associated values appears. If I want to change the value without typing it I necessarily have to redo the entire procedure. Is there a way to make the list of values appear again?
@@MrFeudis Ah, I get you.... unfortunately no way I know of
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 🤷🏼♂