This series (Dario and Cara) has to be my favourite discussion on applied PKM. Most of the other videos I have watched seem to be focussed on PKM for entrepreneurs (not even close to my work) or made by people who make money out of producing videos about PKM. My personal system in Logseq is still very immature, but I have enhanced it from things demonstrated by Ramses, Cara and Dario. Thanks guys and PLEASE can we have more of these?
Thank you Mark! The plan is to have several of these sessions each month. Once your use of Logseq has matured, definitely consider reaching out to Ramses to host a Workflow Wednesday session together.
I am all inspired by this broadcast Ramses and Dario. I want to work on a 'relational database' type structure where I can link all the possible uses for my photos. Listening to you guys make me think that using Properties and Namespaces would put me on the right track. Where can I ask for help in structuring this and perhaps adapt templates of a similar construct? I want to build this so I can learn to use Logseq in the process.
Thank you for the energy you but into creating thise videos but I think it would be quite helpful if you had some shorter video tutorials rather than just hour plus videos.
Great feedback and I wholly agree. The next step will be cutting up long sessions like these into clips, and after that we'll start make dedicated shorter videos that demonstrate just one (part of a) workflow.
I've watched lots of these Logseq videos. Obviously, there's a bunch of repetition, and YET it is still not at all clear how to query properties. I've watched Ramses' video, I've watched this one, I've studied the documentation (OY!), and I cannot get it to work, and i don't know where I'm going wrong. I get the sense that you (Ramses) think you've repeated this info enough, well, you've maybe said the same things several times, but you haven't found a way of explaining properly it yet. This comment feels mean, which I certainly don't intend. Just to say that you need to provide some more basic documentation before any of this ambitious stuff Ramses is often referring to. Just make the docs clear!
Thank you for the feedback, June. It’s unfortunate to read that your experience has been less than ideal. We’re always trying to explain advanced topics in a way that makes it easier to understand for beginners, and we’re continuously learning. But this session wasn’t about queries, and Ramses generally warns against jumping into queries too soon. Have you already watched this office hours about it? It has helped many people. In both this office hours and the onboarding event, there’s a demo and explanation about properties. m.czcams.com/video/i9Xdj6WG_C0/video.html We’re looking to improve the documentation with the help of our community (as we’re just a small team). In the meanwhile, we recommend people who get stuck to ask help in our community where lots of people are willing to help. There’s also a channel specifically for queries: discord.gg/KpN4eHY Finally there’s the community hub that contains more community content about queries: hub.logseq.com
For me there is too much high level bla bla. I would be happy to have more detailed information. I can not really follow what you are doing for what reason. It makes this a long video difficult to follow
@@Logseq I would like to know for example what is the scenario. Why is loqseq in this scenario a good solution. You also jump into examples and expect from what I can see on the screen I know the background of it. You do not for example explain how your files are structured. Also these are very small specific example. Is this how you use it every day. How does this scale. You describe a research project but do not show how this fit with the concept of daily notes. Does it mean for your research project you abuse logseq. Or is it meant that I have for every research project my own logseq or do you suggest put all research projects in one folder. I also understand that if I have the properties I can make a search. However adding the properties for every block is a lot of work and would be too much for me if I would use logseq as a day to day work. So sure if you have well structured data you can make queries etc. But the example data you show are already structured and you do not show how hard it is to enter all the data. I think the template example is useful but I can not see what is the outcome of the video. You represent two workflows but in my view they are quite different. And both seem very specific examples but they do not show me how I can use logseq in my day to day work, where I may do 2h of research, 1 h of Italian course, 30 min organising my shopping list, 1 h planning my wedding, 1 h organzing my videos. I would have expected you show how I can manage this all with one tool. However the different concepts of workflows seem not be able to be combinable and the outcome is find out your own way of using the tool but not this is how we recommend using the tool and that was the idea when we programmed the tool. In this way we think you should organise your work to use our tool efficiently.
@@schlundfeger2158 I find your comment lacks construction. Many of the topics you mentioned are easily found if you check other videos by both Ramses and Dario (shout-out!). There is also easily available logseq documentation and a Discord channel with a outrageously welcoming community. There is also a search bar were you could (kindly) explain your needs and also (kindly) ask for help. Other than that, enjoy this totally free and open software and have a great day!
This was fantastic, I'll be watching it more than once. Great choice of guests, Dario's material on CZcams has been very helpful.
This series (Dario and Cara) has to be my favourite discussion on applied PKM. Most of the other videos I have watched seem to be focussed on PKM for entrepreneurs (not even close to my work) or made by people who make money out of producing videos about PKM. My personal system in Logseq is still very immature, but I have enhanced it from things demonstrated by Ramses, Cara and Dario. Thanks guys and PLEASE can we have more of these?
Thank you Mark! The plan is to have several of these sessions each month. Once your use of Logseq has matured, definitely consider reaching out to Ramses to host a Workflow Wednesday session together.
hey please make a video on hierarchy vs page tags and how to organize notes using the two. really love this content
Yes!
I am all inspired by this broadcast Ramses and Dario. I want to work on a 'relational database' type structure where I can link all the possible uses for my photos. Listening to you guys make me think that using Properties and Namespaces would put me on the right track. Where can I ask for help in structuring this and perhaps adapt templates of a similar construct? I want to build this so I can learn to use Logseq in the process.
Great app. Thank you. Looks great and is easy to use. Also great plug-in's available. Is there a chance to get a layout like Tana or Notion?
Just a question @Dario, is what you cover on your workflow what your overall logseqmastery: workflows is about?
At 10:12 you talk about a system of tags by Carl Void? I've googled this and can't find anything. Have I got the spelling correct?
Hi RJ. The reference is Karl Voit :)
Thank you for the energy you but into creating thise videos but I think it would be quite helpful if you had some shorter video tutorials rather than just hour plus videos.
Great feedback and I wholly agree. The next step will be cutting up long sessions like these into clips, and after that we'll start make dedicated shorter videos that demonstrate just one (part of a) workflow.
@@Logseq - Sounds great. I look forward to that! A short video on migrating from RR would be especially useful for some. 😃
Hello, what LogSeq theme is Ramses using in this video? Thank you!
It's the Quattro Theme by Alexander Rink, available in the Logseq Marketplace.
@@Logseq thank you :)
I've watched lots of these Logseq videos. Obviously, there's a bunch of repetition, and YET it is still not at all clear how to query properties. I've watched Ramses' video, I've watched this one, I've studied the documentation (OY!), and I cannot get it to work, and i don't know where I'm going wrong. I get the sense that you (Ramses) think you've repeated this info enough, well, you've maybe said the same things several times, but you haven't found a way of explaining properly it yet. This comment feels mean, which I certainly don't intend. Just to say that you need to provide some more basic documentation before any of this ambitious stuff Ramses is often referring to. Just make the docs clear!
Thank you for the feedback, June. It’s unfortunate to read that your experience has been less than ideal. We’re always trying to explain advanced topics in a way that makes it easier to understand for beginners, and we’re continuously learning. But this session wasn’t about queries, and Ramses generally warns against jumping into queries too soon.
Have you already watched this office hours about it? It has helped many people. In both this office hours and the onboarding event, there’s a demo and explanation about properties. m.czcams.com/video/i9Xdj6WG_C0/video.html
We’re looking to improve the documentation with the help of our community (as we’re just a small team). In the meanwhile, we recommend people who get stuck to ask help in our community where lots of people are willing to help. There’s also a channel specifically for queries: discord.gg/KpN4eHY
Finally there’s the community hub that contains more community content about queries: hub.logseq.com
For me there is too much high level bla bla. I would be happy to have more detailed information. I can not really follow what you are doing for what reason. It makes this a long video difficult to follow
What detailed information would you like to see?
@@Logseq I would like to know for example what is the scenario. Why is loqseq in this scenario a good solution. You also jump into examples and expect from what I can see on the screen I know the background of it. You do not for example explain how your files are structured. Also these are very small specific example. Is this how you use it every day. How does this scale. You describe a research project but do not show how this fit with the concept of daily notes. Does it mean for your research project you abuse logseq. Or is it meant that I have for every research project my own logseq or do you suggest put all research projects in one folder. I also understand that if I have the properties I can make a search. However adding the properties for every block is a lot of work and would be too much for me if I would use logseq as a day to day work. So sure if you have well structured data you can make queries etc. But the example data you show are already structured and you do not show how hard it is to enter all the data. I think the template example is useful but I can not see what is the outcome of the video. You represent two workflows but in my view they are quite different. And both seem very specific examples but they do not show me how I can use logseq in my day to day work, where I may do 2h of research, 1 h of Italian course, 30 min organising my shopping list, 1 h planning my wedding, 1 h organzing my videos. I would have expected you show how I can manage this all with one tool. However the different concepts of workflows seem not be able to be combinable and the outcome is find out your own way of using the tool but not this is how we recommend using the tool and that was the idea when we programmed the tool. In this way we think you should organise your work to use our tool efficiently.
@@schlundfeger2158 I find your comment lacks construction. Many of the topics you mentioned are easily found if you check other videos by both Ramses and Dario (shout-out!). There is also easily available logseq documentation and a Discord channel with a outrageously welcoming community. There is also a search bar were you could (kindly) explain your needs and also (kindly) ask for help. Other than that, enjoy this totally free and open software and have a great day!