How to use Logseq for research: Structuring your literature review and knowledge synthesis
HTML-код
- Опубликовано: 24 июл 2024
- One of the turning points in my PKM practice was coming across a video by @roberthaisfield3349 where Professor Joel Chan breaks down his model for knowledge synthesis in Roam. I was blown away by the power of networked-thinking & block-based writing workflows.
In this video I break down how to go about applying Prof. Joel Chan's model for knowledge synthesis in Logseq.
You can download the Excalidraw file that I used to produce this video on my Lemonsqueezy page in exchange for a small contribution. shop.combiningminds.org/
📚 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 RUclips 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
03:41 - The research process
10:12 - A high-level ontology for research
12:42 - Questions
13:26 - Observations (used almost interchangeably with evidence in this video)
15:00 - Claims
17:16 - Synthesis
20:23 - Structuring your work in Logseq
23:49 - Adding relationship syntax betwen
24:59 - Some general tips on structuring in Logseq
27:38 - Creating an overall index of your work
29:45 - Example of structuring in Logseq
43:19 - Important points for consideration
51:14 - Ontologies in different contexts
52:52 - Additional tools for research
53:20 - Conclusion
📚 FURTHER RESOURCES
───────────────────────────────────────────────────────────
🌐 Finding research papers: scite.ai/, www.researchrabbit.ai/, elicit.org/
🌐 The IDEO methodology of Diverge and converge I mentioned: designthinking.ideo.com/blog/...
📺 @DannyHatcher's video on Research Rabbit • How I use Research Rab...
🎈 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
I see now that the video and audio are slightly off with the head shots. It does get better when the video moves to the screen-share section 👍🏽
An excellent presentation of both theory and practice. Bookmark it. Rewatch it. Take notes. See if it doesn't increase your understanding and improve your workflow. To quote my favorite Logseq power-user and instructor, this is a "very very useful" video.
😁 Thanks Rick 🙏🏽
When I read books, I use the following highlighter convention:
orange = big ideas
blue = cold hard facts/trivia
green = vocabulary
pink = memorable quotes
Kudos for having a system - I still stick to one colour 😋
I rather the entire video be just one upload. You can easily watch it in segments and just write down the minute where you stopped.
Very very useful :-)! Thanks a lot for this video and your work on YT.
Thanks Anderson 😅
I need this! Prepping for grad school. Thank you so much!
Glad to hear :)
'A claim (noun) is an assertion that something is true. To make a claim (verb) is typically done without evidence. A hypothesis is expected to include limited evidence as a starting point for further investigation. Perhaps I'm too old but when we change the original understanding of terms for stylistic reasons it allows for ambiguity. It's expected in PR but not useful in scientific debate. If I want to make an unsupported claim I now need to think of a new word. I contend that this paragraph is a valid declaration. 😄
This was a great video, thank you. I'm running two test graphs, one in logseq and one in Obsidian, and I'm now addicted to Excalidraw and Excalibrain but logseq is wonderful in other ways. I've dug myself a hole!
I didn't notice the timing issue as I always watch non-music videos at x1.5+ and the difference was compressed.
Thanks again 🙏🏽
If your current language works for you, it works for you 🙂 I found this language helpful starting from base-zero. This is another reminder to me that working with others would require clarification and alignment on the usage of terms.
Whiteboards will be coming to Logseq fairly soon, fingers crossed. They're currently in alpha testing 🙌🏽
@@CombiningMindsPKM Whiteboards are a good development. I didn't mean you need to change your vocabulary. It's my hobby horse to moan about word usage. The internet creates so many new words. Uwu 😄
Thanks for the awesome video! Do you always do the handy-work with new pages up-front, or do you have some workflow for capturing these for later processing?
And I'm also curious - how do you treat citations of other works in the article you're reading? Let's say in a Da Vinci article, there would be a sentence "Donatello claims A". Would you capture that as "Da Vinci claims that Donatello claims A", or "Donatello claims A" or would you just somehow mark it for later finding the reference in the original Donatello article?
Thanks Krystof.
Do you always do the handy-work with new pages up-front, or do you have some workflow for capturing these for later processing? ->
It's a bit of a mixed bag, but if I don't do the processing I will either create a TODO or LATER task, or use my #Fleeting tag to come back to it.
how do you treat citations of other works in the article you're reading? Let's say in a Da Vinci article, there would be a sentence "Donatello claims A". Would you capture that as "Da Vinci claims that Donatello claims A", or "Donatello claims A" or would you just somehow mark it for later finding the reference in the original Donatello article? ->
It's difficult to be too prescriptive of this, but I think I would default to the simplest approach which requires less legwork to understand, so probably "Donatello claims A" (looking at the original source to verify that Donatello does indeed claim A requires a bit more work, and if you really wanted to be thorough that would be the way to do it I think)
Thanks for such a great video, I have seen so many on Logseq workflows and always come back to yours :))) two questions...
1) have you had any issues adding notes to the hls_ pages? That workflow would really suit me, but I had seen comments on discord that people's notes that aren't annotations sometimes disappear and the answer was basically that it may happen, cause adding your own notes to hls_ is not "officially" recommended. so it freaked me out, cause losing notes would be a big nono
2) this workflow seems to move towards working from project and question pages, instead of daily notes pages, for knowledge stuff. Have you encountered any disadvantages from that? When I'm reading pdfs and stuff, I have been trying to add notes from the daily notes page, which works well if I finish that pdf in the same day, but if not then picking up the next day is a bit annoying, so I started just adding the source page from the daily notes, but then adding my notes straight to the source page so I can pick up next day where I left off. How does it work for you?
Thanks Karolina
To answer briefly:
1) No, I have not had any issues when storing the PDFs in my 'assets' folder. I had some issues when I was storing the PDFs in my Zotero folder. When there were special characters in the filenames it caused the link to break, and some information went missing. I'm not sure if this is the problem that people were referring to, and unfortunately can't guarantee that you won't lose your notes.
2) I don't think you have to make a decision on working from projects/question pages vs. daily notes pages. You can work with the two in unison (I think the way you're describing sounds about right) Some people default to the DN page, but I found that to be cumbersome.
Hello Bro, I recently purchased your Logseq course (full bundle) 2 days back and completed it .
A BIG thank you to you 🙏for putting so much efforts - diagrams , notes , so much indepth details of workflows, ideas etc.
I would say your course is priceless ❤. Worth every penny spend on it.
I never saw anyone till now, explanining so much in detail touching so many concepts with beautiful examples.
RUclips videos were all in bits and pieces and i didnt understand the basics of logseq.
Your course helped me understand in detail the real use of logseq.
I found logseq is better than obsidian - having the block reference and its so easy to "query" also. In obsidian its very complicated to query using dataviewjs etc.
Sorry for my long message. But my expression of Happiness is out of the world completing your beautiful course😊
From tomorrow i will be applying all that in learned from your course.
A HUGE thank you to you Bro ❤🙏. I felt life changing with new ideas after completing your course.
Would highly recommend anyone who are new to logseq. The uses & ease of workflows , ideas are IMMENSE in logseq compared to obsidian.
Have a good day ! 😊
Hi Ramesh.
Thanks so much for the feedback, this was truly heartwarming to read ❤
I hope you continue to find the course (and Logseq in general) useful.
Wishing you all the best.
@@CombiningMindsPKM Thanks so much bro for your message ❤🙏. So happy reading your message. Yeah, exremely useful course ❤ . Have a good day ! 😊
How are you getting those coloured page links ? You touched on it a bit in this video. Can you please elaborate ?
Hi - I'm using custom CSS :) Here is a guide www.onestutteringmind.com/adding-custom-css-to-logseq/
I'm really interested in these videos. The problem I have is that I have a bit of phd burnout and these videos are too long for me to digest with the amount of other work I have to do, if you could do a more concise video it would be so so helpful. Thank you for doing this channel
I'm working through it however!
As Mark Twain said, "I didn't have time to write a short letter, so I wrote a long one instead." 😅