Use Zettelkasten and Obsidian To Build a Personal Knowledge Base

1. Introducing The Class: Hi there. My name is Mustafa, and I will be your guide through this course. In this course, we will explore how to build your very own personal knowledge management system using the zer Casten method and OBCDian. Here is what we are going to dive into. What is personal knowledge management and why it is essential, how it can help you to learn more efficiently, how it can spark creativity and help you to generate new ideas. The history of the ZirKstN method and how it was implemented by Nicholas Suman, a practical way to manage your own personal knowledge base using Obsidian how I have adapted the Zittle custom method to suit my own needs and to improve my BikiEWflow. This course is out of my own learning from these incredible books, how to take smart notes, a system for writing, building second print, writing to learn, how to read a paragraph, and countless hours of research and experimentation to optimize my own BikiEWflow. If you are ready to transform the way you organize your knowledge learn faster, and think more creatively, this course is for you. Let's get it start. 2. What Is Personal Knowledge Management and Why It's Important?: Before we jump into the ZietlKstn method and how we can use it, we need to clarify a few things. ZietlKstn is just a way to manage your personal knowledge. But what actually is personal knowledge management in the first place? BKM or personal knowledge management is the process of gathering, storing, and interacting with knowledge through our lives. In the past, managing knowledge was only concern for the intellectual elite, writers, philosophers, scientists and politicians. They use tools like commonplace books to organize their sorts and to synthesize their work. But with industrialization and technological advancements, the nature of work has evolved. Today, more than half of the workforce can be considered as knowledge workers. People whose primary job involves handling and using information. They use their expertise to solve problems, create new knowledge, and to generate new ideas. Unlike the manual labor, knowledge work depends heavily on cognitive abilities and specialized knowledge. You, as a knowledge worker or as a learner, personal knowledge base can help you in a different dimensions. First, it can improve your understanding, making notes in a right way while learning and engaging with what you are consuming or learning is a skill that help you to understand things better. When you try to put the main idea into your own words, it is not just the best way to get what you are reading. It is also a way to check if you understood it or not by writing it down. We will dive deeper how to do so during taking literature notes. The second thing is improving your thinking. Making notes is also a form of thinking in the medium of writing and dialogue with your existing notes and knowledge, moving information that you are reading from its original context into the context of your existing notes and knowledge with your own words requires a certain complexity of coherent argument, even by just adjusting the language that makes you think at least twice about what you are reading or consuming and that only happens when you write this knowledge down. This all would make sense when we dive debar into the process of writing and making permanent nodes. The third thing is that you can build a career through building your knowledge. Writing notes into your personal knowledge base with dittal casting can be considered as comboind interest. Writing more nodes mean more possible connections, more new ideas, and more synergy between different projects. And therefore, much higher degree of productivity. The Nikolas Tuman, the Mnh polarized this method, his personal knowledge base contained 90,000 nodes. I will tell you more about his amazing career achievements by writing more than 400 academic paper and publishing more than 50 book only by working effectively by D sitted custom work. 3. The Story Of Niklas Luhmann: In this video, we'll go through the story of Nicholas Lumen, the man who popularized the ZterCustin method, and how it helped him to publish more than 400 academic paper and 50 book only in 30 year period, making him one of the most productive social scientists in the 20th century. Lumen was born into modest beginning as a son of a brewer. After law school, he pursued his career as a public servant. However, his work required socializing and managing multiple clients didn't suit him. Instead, he followed his passion for philosophy and sociology and started diving into books after his nine to five shifts. At the beginning, as many of us, he started to take notes on a margin of text. However, soon he realized that wasn't helping him to connect ideas or building real knowledge. So instead, he started to take notes on small paper cards and collecting them into one place, which is the slip box or in German, the Zittel custom. He knew that idea is only valuable in its context, which is not necessarily its original context. So he started thinking how one idea can contribute and relate in a different context. His zer custom became his dialogue partner and main idea generator. He also used to collect notes into two different Zed customs or two different note boxes, one for bipographic references and brief notes, and another one for his main ideas and thoughts. He did not copy codes, and instead, he translated them with his own words to fit a different context. He also used numbers, letters, slashes, commas to make an alphanumeric ID that represent his train of sort. And he bought this ID on top of every note he's taken. Making something called Folgeztel or sequence node, which we'll explain later in this course. He also used this ID to link nodes together in his system. Luman developed the topics, bottom up and instead of top down approach. He will explain how this can be useful to generate new, unique topics and ideas. Lumansle custom wasn't just a tool. It was his key to his career transformation. He used it to organize his sought into a manuscript, which he shared later with scientist called Helmut Chilski Chilski was so impressed with Luman's work so he encouraged him to pursue academia. However, Luman didn't have a sociology degree or a doctorate or any academic credentials. But with the help of Hes Caston, he acquired all the required qualifications within a year by 1986, and at the age of 38, Luman became a professor of sociology at Bilfield University, where he remained there for the rest of his life. His system didn't just allow him to publish more work, it also allowed him to focus on writing as the core of his work. While Lumen didn't write extensively about his ile custom, his method inspired countless individuals. However, it wasn't immediately impressed because the focus was only placed on the slave box itself, ignoring the workflow it supported. Also, its simplicity often lead people to underestimate its power. Lumen's story is a testament to the power of well designed system or transforming ideas into achievements. 4. What Is Zettelkasten?: Before we jump into how we use Zr casten, let's discuss first what we mean by Zr custon. Zerksten is a German word and its literal translation means Nut box. So Zerocastn as an object mean ut box like this. So back in the time, people write their notes on index cards and put them into wooden boxes like this. Actually, this method is still used until now. And people refer to it at the moment by the naloxeor custom. This is exactly what Nicholas Luma used to build his knowledge base. But in this course, we are not interested in the naloxeter custom, we will use instead, the digital version. An addition being an object, dial custom is also a workflow, a way to capture ideas and notes, establish connection and relationship between them, and leverage them for knowledge work. The workflow formula is pretty simple and straightforward. First, you have an idea or thought, you capture it with reference node or fleeting node or literature nodes, and then you try to turn them into concrete permanent nodes. You make connection between your permanent nodes. And then when you have enough connection, new ideas, topics can develop out of your existing connections. Later, you can turn those ideas, topics or train of sorts into a publishable piece of work that you can share with the world. So the unique part of this workflow is the chaotic organization that it has. So Zile custom has a unique way of organizing nodes. You don't have a fixed topical folders or top down organization. You just place your permanent nodes into one folder and make connection between them. Later, this connection will develop a bottom up organization. So as the relationship develops between your nodes, areas of Zetycin where aswell common topics and seem emerge and also can be recorded in additional index nodes. With this lumen style Zettel cain organization, we begin with neither a redefined set of categories to which our nodes are assigned to nor do we store them into atopical folders? It's important to understand that Nicholas Sluman didn't invent the zer custom, instead, he developed this unique way of organization and structuring the nodes. This way, you don't have a predeterminate organization, and instead, topics and seams emerge out of relationships and connections that you make between your nodes. 5. Capturing With Fleeting Notes: Note taking, lets you quickly get ideas out of your head and onto the page, forcing previously vague sorts to engage with the language needed to bet them into coherent and concrete ideas. Zettlcsten provides a structured framework for organizing information. Well organized nodes enable learners to review content efficiently, locate specific details, and grasp overall flow of information. The first way to capture information with Zitle custom is through the flatting nodes. But what exactly a flicking node in Zita custom? These nodes are only reminders of information that can be written in any format, and they will end up in a trash. So they should be improved then when the that's why they are also called inbox nodes. How to take a flatting node? It's very simple. You have a sort, you write it down. For most people, this is where the process ends. Only with acetic custom, you are asked to make a fundamental cognitive shift, knowing that the note you just took has yet to realize its potential, and your workflow should contain one more step that requires you to create something useful out of the reminder you just took. The flitting node can become a permanent note, but before this transition can occur, you will need to stage your flatting notes in an inbox until they can be processed. An inbox is as easy as putting default folder for the new nodes to be created in until you move them permanently to their new location. An inbox will give you a place to store nodes on the go so that you can come back to them later. But also an inbox is much more than writing room for your ideas. It's also a reminder that the nodes that's stored in your main zer custom are special containing connection and context where similar ideas are in your Z a look, for example, over my own inbox folder, and let's see what exactly what are my current flitting nodes. So for example, this is one of my flatting notes. This about something called event modeling, just a link to article that I want to read. The type is fleeting and I have to review the article and to create a node out of it. I have to review the article and create useful node out of it that relates to my Zr casting. Also, you can find here more Azure of fleeting notes that I took on ago and they all stage it in the inbox folder in my Zr to process leaving notes. Any new note you took, you put it in your inbox, which is a difault folder for your new nodes. Then you can come back to them and review them if they are useful and you were able to create something useful out of it, then you can put them as permanent notes in your Zetrcastm. If notes and they are not relevant anymore to your own sinking and sorts, you can just read them. And that's it. That was one of the ways to capture information within Ztrcas. 6. Capturing With Reference Notes: We talked about how we can take quick ideas and sorts out of our heads via flitting nodes. Now, we will discuss how we can bring others' ideas and cite them in our Zettlecston using the reference nodes. Are reference notes. Reference notes are source specific notes that provides detailed information about a specific topic. They are usually directly taken from external sources, such as books, articles, website, or research papers. They are often used as raw data for creating more refined notes. A single reference notes contain a brief citation or references to what caught our attention while consuming a material. It should contain a link to the original source, like the book name and big number. This note should allow you to come back later to it and revisit what attention and make a permanent note out of it. So an example to this, this is one of my reference notes. Here I have the title of the node. I have the source, which is the book name. Actually, this is the book itself. I have the book name written here and I have the big number. I have the type also I reference. I have the de from the book that caught my attention in this page. So this is an example of what a reference node could look. To take a reference notes. The practice of taking reference notes comes from Nicholas Lumen who avoided writing in his book, referring to write on an index card. Anytime a message spoke to something he was working on or reminded him of an idea previously recorded in his Zr custom, he would write the ***** number of where the message could be found, followed by a brief description of what was say it or how it was related to his thinking. On the back of the index card, he recorded the bibliographic information. I think the message that got his attention, Lumen doesn't appear to give himself rules as how many is too many. Reference nodes are a special nodes that are stored within your zittle custom, but in a different partition away from your permanent or main nodes. They have their own specific folder or partition where you store your references, your reference nodes inside it. 7. Capturing With Literature Notes: Instead of citing and quoting sources directly in your ittle castm, you wanted to interpret or summarize them with your own words. Here comes the role of literature notes. What exactly literature notes? These notes are your personal interpretation, reflection, and summaries of the information you gathered from your reading or learning. They are more concise and focused on capturing the essence of the source material. Your own words, facilitating deeper understanding and integration into your knowledge system. Lumen usually wrote literature note with an eye towards already existing ideas and sought in his ite cast. And while literature notes were brief, he wrote them with a great care, not much different from his style in the final manuscript in full sentences and with full references to the notes somewhere in his ZETecast. Literature notes are not copying ideas from a text that you have read, but a translation from one context to another, the context of the book or the article you are reading to the context of your Again, it's very much like translation where you use different words that fits different contexts. How to take a literature. This symbol when you read something, make note about the content, write down what you don't want to forget or sing you might use in your own thinking or writing. But try to keep those rules. Keep it very short, be extremely seductive and use your own words. If you need to cite something, use a reference note for that. Here is an example of my literature note from a technical book that I was reading, and this is the note itself. Here I have the tags. I have the source, which is the book name in the chapter itself and I have them that caught my attention that also have an example on this thing that caught my attention about the deep modes in software design. It is important to understand that copying codes always change their meaning by stripping them out of the context, even if the word didn't change. This is a common beginner mistake that can only lead to a patchwork of ideas, never coherent sorts. While selectivity is the key to smart note taking, it is important to be selective in a smart we should seek out the conforting arguments and facts that challenge our way of thinking, we naturally are drawn to everything that confirms what we already believe in, which is known as a confirmation bias. How to avoid confirmation bias while taking reference notes and literature notes. Confirmation bias and etic custom can be tackled by turning the writing process on its head and changing the incentive from affirming facts to gathering any relevant information, regardless of what argument it will support, developing arg the ideas bottom up instead of top down is the most important step in opening ourselves up for insight. We postpone the decision on what to write about specifically and focus on building critical mass within the Zir custom. As we want to one, first confirm that we have separated task and focusing only on understanding the text that we are reading. Second, making sure that we have given a true account of its content, shared, find the relevance of it and make connection. 8. Making Permanent Notes: To integrate what you capture into your knowledge system, you must transform it to something that connects to your existing thoughts and ideas without by confirming, expanding or even changing it. These links create relationship that wave your ideas into a cohesive knowledge network. This transformation is only done when you make the permanent notes. What is permanent node. They're also sometimes called evergreen notes or main nodes. For me, all are the same. These nodes will never be thrown away and contain the necessary information in a permanent, understandable way. They are always stored in a zitted custom, and they are the main building block of your knowledge base. What a per node can contain. In its basic form, a Bermant node should have first a single idea. When a node contain a single core idea without counter arguments or follow ups, just one unit of information, you can easily associate it and link it to other core ideas as needed, making the ideas connectable, memorable, and linkable. If you feel a lot is going inside your Burman node, remember, it's all done in service of your future self as you will be introduced to new ideas and forgetting old ones. You will help yourself by making quality information second thing in your perman nodes are links to other nodes stored in your Zr custom. Links are used to establish relationship between ideas connecting SOTs. We will discuss links and relationship later in details in this course. Also, the third and last thing, if it is required, you can boot a title for your permanent node. A title should be declarative, clearly indicates its content, consistent naming convention can also save you some mental effort when creating new nodes, such as using capitalization, lowercase or prefixes like a specific IDs in your node headers or titles. There is or additional information that you can put in your permanent nodes, like the source or a link where the idea comes from, a unique alphanumeric ID or FolgtsetL which we'll discuss later in the next video in details. Now let's jump into an example, permanent node that I've created in my Ze custom. This is one of my permanent nodes. It has all the information needed to be stored in my zer custom. It has one unique idea about something called phantom reads database phenomena. Also, it has another link to the parent idea where I have all the database phenomena listed there. Here, one last thing that I don't use usually, which the alphanumeric ID called Forget settled, which we will discuss in detail in the next video. How to add a new Berman node to your zer custom. You can create a new permanent node either directly from your sorts and ideas or by processing one of your literature or fleeting nodes. Regardless of the source, the process should remain first, write the idea into a file, use a complete sentences to capture the sort that you are trying to introduce. Second, look how this idea relates to other ideas in your Zettle custom. If it relates to something else, add links and relation to different nodes and ideas that is already in your Zettle custom. If you want, you can rewrite the node to speak directly to one of those nodes in your existing Zeta custom. Third, put the new node either behind the node that you are referring to. If you don't follow up on a specific node, just put it behind the last node in your Zeted casting. If you are using FolgZety number it consecutively. First and last thing, make sure that your new node is discoverable. It should be found via the index node or the entry index, if necessarily. Refer the node to be connected and connectable. As use tag to make it discoverable if you are using tool like OBC. 9. Building Connections With Folgezettel: We talked about how links and relation are fundamental part of permanent nodes and zer casting in general. In this video, we will discuss one way to link your node together using the Folgtseter. But what exactly Folgtsele? Forget setter is a German word that means consecutive nodes. By giving an alphanumeric ID to each of your nodes, you create a sequence relation between them. However, Lumen didn't use the term forget setter itself, but he was also engaged in the practice of creating sequence of nodes, which has relation to the node before it. If you are using analog Zittel custom, adding an ID to each node is absolutely required. But in the case of using digital Zittel custen was a tool like obsidian or oxic, that is not required because you can easily link the previous and next node in your train of SOT with your current node without any IDs. However, using the forget settle has various AR benefits that we will discuss later in this video. How to use Forget Settle and how to implement it. As we mentioned, Forget settle is just an alpha numeric ID that represents your train of sorts. Let's have a look together on one example from my notes. I have this node, which is database engineering. It has the idea of 3a2g, and it has five other branch out nodes from the original node. I have 3a2g1, 3a2g2, three, four, five, okay? So I have a new number for each follow up node here. So I have 382g1, 382g2, 382g3, and have also this note here, database read phenomenon with this ID 382g4, and I have a branch out notes from it. I have 382g4 A, BCD. I have here added a letter instead of digit because I'm alternating between numbers and digits. So you have a letter, number, letter, and then that's what we have at na2g, four A. And here I have the same, but instead of A, it is B, C, D. So this is how you branch out from your current node by adding a new character to the end. Depending on your train of sort, this can be changed. So if I had this first, this ID should be the other way around. So this should be B. Here instead of A, but this is not the case. I had this first and this after it. For example, this node has another follow up node. That's why I also added another number to the end of the current ID. So that's how you branch out and follow up with your notes in a Fg settle. It's very easy. You just have to pick one node and follow up with your train if sort and give it a new number or a new ID to the new node or the branch out node or the follow up node that you have. So let's back to our presentation. So the thing that I want to discuss how this can be useful in your Zetrcas or how it can help you in your Zero cast. First, it adds friction when you add a new node to your Zeal custom. As Bob Toto, the author of system of writing book, mentions that Fogltsetl slows the note maker down just enough to force them to think about what they are doing. It's the kind of friction is needed to help note taker who tend to draw and capture plotting, always emboding, never offloading. I also agree with this that Fogltsitl will make you think before placing a new node into your permanent notes or in your Zirc we also force you to see how this new node will fit into your existing sorts and ideas, which is kind of useful instead of blindly capturing new nodes that might be far away from your current thinking. Forcing yourself to assign a new idea to your new node will help you doing that. Second thing is high level overview. FogeTiter can provide a high level overview of your nodes. You can think of it as some kind of mind maps where you can navigate your nodes or ideas knowing which is follow up to which and which is branch out of which. This kind of mind mapping helps me to figure out how topics and sorts are related or depend on each other. 10. Building Connections With Links and Index Notes: In this video, we will discuss how to use link to build the relation between our nodes and Zeta cast. When adding a new permanent nodes in our zeta custom, it might have a relation towards what we already recorded in our Ztedcas. That's why we mentioned we need to look what we already have in cited custom growth before placing a new node. We look for other nodes that supports or related to the new node or even contradicting. Also, it is important to think on high level, not only look for the meaning of the node, but also to say on a high level w one node can be related to another even metaphorically. Remember, on aviation, usually you measure out of multidisciplinary environment. Creating a node with relation with supporting or contradicting it with Azure node and your Zeted custom can reinforce other independence. Lumen stated, every node is an element which receives its quality only from the network of links and pack links within the system. That's why when you make connection, you are expanding your ability to express complex sorts. It is also important to give context to your connection. Relationship between ideas are strongest when you have a clear reason for their connection. Also, if you link nodes without stating the reason, you will definitely forget the reason for this connection in the first place. I have a how I connect nodes together in my Zita custom. Here I have this note about something called technical programming. As you see here, this node has lots of relation between other nodes. I have here the parent node where this node comes from or its parent idea or previous idea in my train of sorts. That's it. This node is represent the difference between strategic and tactical programming. I have here the main idea of technical programming in place. I have here the deeper, which is a x node in my train of sort, which can be done using the fgetseal. But here I'm just linking the nodes in this way. I have here also against node the node that contradicts with this node, which is the strategic program I have related note on a high level, this topic about strategic and tactical programming is part of my literature note from philosophy software design book and this how I represent all the relations. I have a parent deeper against something that contradicts against this mode and I have also related note. Also this is the type of the note itself. Something else, which is the text, we will discuss it in more detail later when we look how to implement cussing with getting back to another topic which is using the index nodes to build relation about a specific seam or topic in your Zital casting. What exactly index nodes, Index node are special nodes that shows and explain how to navigate through Azure collection of nodes. As your Zitlcstm grows, you might develop collection of related nodes. These nodes sometimes do not have rhetoric relation, instead, they have a common them or subject. Index node helps point towards various places in your Zeta custom where you have written about this subject acting as access point for node collection or train thoughts about the same theme or subject. But how to identify those themes or subjects in your Zeta custom? When you have a number of nodes referring back and forth to one another and each one dealing with different aspects of the subject, this area of your Zitter custom has lots of ideas have lots of connection and relations. Also, if you are using tools like obsidian, you will see this wall clearly through the grav Ve. For example, have lots of notes about software architecture topic because this is one topic that I'm interested in. I can have one index mode collecting all software architecture topic that I have in my Zor custom. Also, this should give a good overview of what I have logged, I learned so far. I will show you in details how we can create index modes of obsidian tools like Gravvie and data view. Now let's have a look on example of one of my indexes. I have this index mode about database engineering. It's also a topic that I'm interested in somehow. I have here all the nodes that is related to this subject. I have lots of notes about database internals and transaction, read forms, isolation levels, but partitioning and charting and so on. All these nodes are about the same thing which is database engineering. That's one example of index nodes in minds 11. Obsidian Foundation : In this part of the course, we will discuss how to make the most out of obsidian and how to use it to build your own person knowledge system with Zito custom. First, let's start by why I use obsidian. There's hundreds of note taking applications out there, but I still prefer obsidian for the following reasons. First, store all your notes and markdown formats in your local storage. You don't have to worry about privas. It's only stored on your local storage. The second thing, all the notes are stored in markdown format that you can manipulate with other applications. You can even use file editors to write your notes. There is, like, a lot of people using them to write notes and to manipulate. Have to worry about the compatibility of using other file editors to write your notes. It's only stored and marked on files. So it's very easy to manipulate the files after you edit them with the other thing that obsidian is totally free unless you are making profit out of it. You are using Obsidian for work in your nine to five or something like this, you don't have to pay anything. Even the commercial license, pretty ships $50 per year, you don't use it to make profits totally free. One more thing, there is Greek community around Obsidian. There is hundreds of blog inside Obsidian that you can use. Most of them are community plugins like developers developing their own logins we shared with AR Obsidian users. There's hundreds of these plugins that you can put in an setup. On last thing, they have very active development and they have very active team. You can see every week or every two weeks, there is a new version released. Application is very mature at this point. You don't have to worry about the company or the application not being continued or anything like this. Even if this happened, you still have your notes written and marked down and you don't have to worry about using the application. You can use any file edit or any Azar note application to continue working with your notes. Any fars I do, let's jump into Obsidian and let's start by creating a new volt. Let's see how we can use it. Here I have a completely new volt created for this video. So that's what you get out of the box. It's pretty simple interface. You have here your notes, and you can also customize everything, yeah as much as you can. On the other side, you have all the nodes. So let's create a new node, for example. Um Node. You see here the files and you can open them actually in the finder or the file system, you will see all the files inside the volt. So by creating a new node, you create a new file in your system like here, and also you are creating a new node in your graph view over there. And you will see the connections between your nodes, like here. So, yeah, that's the point of using this gray view. You will see your connections between your nodes. And also, you can see them even if they are not there yet. So here you have a link, or you can link also, like the new node that you created. You'll see here, the link is being you can see the link is now visible because I link the two nodes together here. How you create the link, you just have to write square brackets twice and you look for the big. You look for the bige that you want to link it, and that's it. Yeah, and also the grave is updating instantly. As we mentioned, Visitian uses the markdown format to format the text that you have in your node. So, for example, if I have hash tag or something, I will have A H one hitting. So here, if I have this, I will have H two hitting. And so on. It's about getting used to this markdown format. Yeah, you don't need to remember everything. It's very simple and very intuitive, to be honest. So this is, like, the point. By point, for example, um, and yeah, you can do it like this. It's very intuitive. That's pretty much how you format. How you also create external links and so on. Yeah, you will see it here in this example. So yeah, you have your link in a Branzs and you have your test between these square brackets. As I mentioned, you don't have to worry about every single thing. You can also look into the markdown examples on the Internet, but this is how CdiN format your more saying that all do commands that you want to do within obsidian, you can find in the command pet. So if I type Command B, I will have all domands inside obsidian. You can, of course, search them. You can, for example, save. I don't know. Yeah, you can switch between dark and light modes, for example, this is the light. I prefer the dark. So you can do whatever you want with this command. You can also export your note to PDF. You have tons of tons of options here. But yeah, I would recommend that you look for what you need and start implementing it. Don't worry about every single command inside the PCIDa. You just look for what you need and start implementing. One more thing that you can do, you can search all your files with Command O. So here I have all the files. Of course, there are few because it's completely new vault, but you can search the files with Command O. It's about opening file. You can also create a new file from here. So let's say a new file to open, I don't know. So that would create a new file. Yeah, that's the basic stuff with obsidian. And also here you can see this grav view. Maybe let's have a quick look. As you mentioned, every file you have, it will be represented here with a node inside this grav view. You can control and filter all the stuff that you have. Of course, it's not useful now because we don't have that many files, but if you have larger graph with hundreds of nodes, it would be more useful. Later, we will show how to filter with like a larger graph with my nodes inside it, and we will see how to group and do all the manipulation. But for now, you can see that if you click this, you will have only the files that already exist in your vault, but files only link it, but without an actual file would be removed from the graph. You can also group some files together. You can search what a specific s. You can search a specific tag. But this is fully customizable. You have tons of option to search and to group your nodes in this graph. Now let's navigate to settings. Let's see what the settings of obsidian looks like. So you can jump into setting by typing command comma. You will see all your setting here. For example, I have here editor settings, for example, you can adjust everything that you want. You can adjust the font. You can adjust everything. Here the default. If you have the default ring mode, you have the live preview, and also have the source mode where you have all markdown symbols over there. And you can have also settings for, for the files. You can see here the setting for the vault and files and links and so on. You have you can have also the setting of the appearance. You can change the color, the accent color if you want. You can change the base color scheme and so so many things that you can adjust here and you can customize. So it's fully customizable. What I'm interested in here is the plugins and the hot keys. So you have two types of plugins. One is the core plugins. This is the plugins that comes within Obsidian or shipped by Obsidian itself. So you have here the canvas. You have the common palette that we were using. You have the daily node, which is generated you node every day. You have also the grape, which we were using at the moment and many others. There is even more plugins that you can use, which comes from the community. So you can turn on your community plugins and you can browse them. So here you will see the most popular plugins. Here we have Excalidro, Data view, and Tim later. We will use the three of them during this part of the course. So maybe let's install it. And enable it. Data view as well. Let's install it and enable it. And also templaor which will enable you to have template for your nodes. It's pretty handy. So I will install it and enable it. Now, let's create a new Exca draw by pressing or going to the command palette. Gala draw, create a new drawing in this new tab. Now we can create a drawing or whatever that we want. Here, I use this mostly for presentation purposes. So yeah, it's pretty handy, pretty neat to use as well. One more thing with the settings that you can set a hot key for pretty much everything. For example, rename your files, rename. By faults is if two, but I would like to I don't know, change it for something else, but set another key Command shifts R, which just rename for me. And this will rename the file. You can also set another key, for example, a new excadro New draw drawing. Let's put it, for example, shift command N. That's already existing. Maybe let's use another hot key for that. Maybe let's use Shift Command E. Yeah, that will create a new drawing like this. You can set hot key for everything that you want, and yeah, it's really need to be honest to be able to customize every bit of note taking application that you are using. That's it for this video. Next video we'll discuss more about how to write notes in psidan and how to add tags and more meta data to your nodes. 12. Obsidian Tags and Meta-data: We talked about how links and relations are important in iter casting. In this video, we will discuss how to create these links and connections between your nodes and obsidian using tags and castomtadata, or properties. Tags and metadata are like the glue that holds your nodes together. In obsidian, they allow you not only to connect your nodes together, but also to group and filter. First, let's start with tags. How I use tags is to label my nodes based on a seam or the topic or subtopic they are related to. I can also use sub tags if I have subcategories or subtopics out of the main topic. Now, let's jump into an example. Here we have three projects in this folder and we have seven tasks. So assuming that we want to label the projects as a project and azotsks to group or filter the we can do the following. So how to add properties to your node is using these three dashes, and then you will have this list comes up. Here you can put whatever you want, but what we are interested at the moment is the tags. So let's choose tags, and we can put any tag that we want. For example, I will use the project to take this note as a project node and we'll do the same for the others as well. O tasks, we have two options. First is to take them as task or to use sub tags. For example, we can have project and sub tag from the project called Task. So you can use it like a separate tag or you can use it as a sub tag from the project tech. It's totally up to you how to use tags and sub tags. We will discuss what is the difference between using separate tag and sub tag like this in a moment. Now let's continue doing the same for all other tasks that we have. Now let's see how this appears in our filtration. Let's close this. We have now this step and we have all the tags that we have in this vault. If you click here, you will see all the nodes that are tagged with tag called project, and here all the nodes that are tagged with TechTsk. Because we have sub tag from the project called task, we will have this as a tree. So here you can have all the tasks or all the nodes that are tagged with sub tag from the project called Task. So it's totally up to you how you want to organize your tags and sub tags. But if you see this makes sense for some topics, for example, feel free to use it. If you want to have every tag as a separate tag like this, this is also available option for. Now let's jump into one real example from my notes. Here I have this note about the benefits of well written good comments. It has two tags. One indicates that it relates to the software design topic, and another one indicates that this note is a literature note taken from my readings. Now, let's filter with these tags in the grave and see what we would get. So I have here my grave and I'm filtering with software design tag. I have here a few notes about software design, and I have a few tags are related to this tag itself. You can see, these are all my notes which is related to the software design. And this is how I filter. You just need to write the tag in this section or in this way, and you will get all the nodes that are related to this topic. Now, let's dig this tag one step further and filter with subtag instead. So I have software design, and I have Subtag called design pattern. So now I get all the nodes that are related to the subtopic that called the design patterns. So here are the nodes and, of course, the tags that are related to software design and it's subtopic design pattern. Obsidian doesn't only offer tags as the only metadata to use, instead, it provides us with a really powerful feature that you can set custom metadata to your nodes, and these metadata can be of any type strings, links, pull in, numbers, date or even an array of string or as they call it list. Let's use this custom metadata to set some unique connections between our nodes. For example, let's try to add a new probity that indicates the parent of this task. So here we need to write parent, and now we have a custom property that we created. We can change its type, whether it's text or list number or Bullion checkbox, al true or false. Date or date and time. So we have all these types. You can set any text that you want, but for example, we can also set a link. So here we can set link to the parent. Let's say it's the project one. So we are linking this task to the Project one, as you see. That's one way to do it. You can also, for example, try to set a deadline. Here, I can set any deadline, and let's change this to be a date. And let's set it, for example, by the end of the month. So here we have a new metadata or property that we added to this task. We can add even more. So, for example, let's have a list, call status, and for example, this task is still in to do, or maybe you want to have another task with another status. Let's do it like this. And for this task, let's put it as in progress. So you can have a list of statuses. So you can have lists like this and you can even add or create any other properties that you want. Now, let's have a look how I use custom metadata in my own nodes. So for example, this node has tags, of course. This is the default thing that I use to indicate topics as we mentioned. But also I have this custom metadata that represent the type of this note, whether it's permanent literature, fleeting or reference node, even. So I have here all the node types that I know from Zito classing to indicate the type of this node. Later, I can filter all my index node, for example, or even all my literature nodes. I can filter out with the node type. For example, this was one of my permanent nodes, so I will keep this. Here I have also another link. Which indicates the parent of this node. And I have another link that indicates the deeper sort or the deeper idea. So in this case, is the benefits of general purpose modules and software design. And I have another link also that indicate the opposite idea or the opposite node of this node as well, or this. For example, for reference node, I have very special metadata that I use. I have the type. Still reference, I have the source, which is the book name or the source of the material that I took this note from or this reference from, and I have the Bige number. If it's a book or something like this, I indicate all the information that I need inside these properties or inside this metadata to make connection as much as I can, or to build the connection as much as I can. And that's it for metadata and text. Make sure to use them in a way that suits your needs to build connections and relations that fits your system. 13. Obsidian Note Templates: Imagine that I wanted to create multiple task nodes like this with all properties and metadata that it has without any automation help. I will have to write them every time I create a new task or at least copybST fills. However, there is a way to automate this creation process. Here comes the rule of temblaor plugin. Templaor is a community plugin that allows you to define the structure or a format that you can reuse, so you don't have to rewrite them when you create a new node from this type. In this example, we will use temblaor to scaffold a new task node for. One important node, there is another plugin called temblts which is a core plugin that comes with obsidian. It also allows you to create custom templats. However, it has very limited options, unlike temblaor, which is why I will start by disabling it and then installing temblaor and setting it up. I make sure that Templet plugin is disabled. Now I jump to the community plugins. Hours and you can search for temblaor. I have it already installed. Now let's look into the option. First thing that Templaor needs from us is a folder to store all the templates. So let's start by creating a new folder just for templates. Let's go here. We'll create a new folder, call it templates and get back to the temblaor temblts. So that's what we need. Now, let's create a new task Timlet. What we need is to scaffold those properities here. Now, let's start by adding those properties. We have tags, and the tag that we want is project task. We also need a status, which is by default, let's have it as to do. We want created ad, which should be the file creation date. To do so, we need the help of Templaor. I need to use the template format like this. It is better if we had the source modes. We have this autocomplete thing. So file, I say creation date. Yeah. So this is created ad would be the file creation date. We need the prances at the end. What we also need is the parent, which should be the node folder. So we can also use the head of templaor to detict the node folder for us. So TP file note folder. Maybe we also want to have a deadline. By default, let's put it after seven days of the creation date. You have also to specify the format. I use this standard format. Then we add seven days. That's it. Now the content of the note. The description and the subtasks, if we have any. So now we have our first template. I think that I missed the T and Bond, so let's add this back. And now let's try to create a new node from this template. Let's start to create a new node first. And let's call it Tsk. Let's call it Tusk create it with Telter. Now let's insert the template. So templter insert this one. So now we have all the properties that we wanted inserted here. One important thing that we can do those steps of creating the node and then inserting the template in just one step by setting up a hot key. Let's jump into temple or setting, and let's jump into the hot key section. So template hot key. Let's add a new one. We want to have a hot key for the task template, and let's assign a hot key. Let's now search for task. Yes. So let's set a hot key for this one. Let's use Option Shift Now we have a hot key for diste Blade. Now, let's try it again. Option Shift, And now we created a new task note. You probably need also to view it like this. Yeah. So that's it with Timblaor. Of course, there is more advanced usages. You can do it. I would recommend that you read the documentation of temblaor. It has many options. You can even write your own JavaScript scripts and run it to scaffold whatever you want. So it's fully customizable. You can rebuild links and connection via noting template. 14. Obsidian Dataview Plugin: Data view is a community plugin that helps you to quer your notes based on tags, roberties or metadata that you attach to your notes. So let's see how we can do this. First, let's install the blog in itself. By going to the community plugin, we need to browse it and we look for data view and install it. You can also check the options and hot keys. I already installed it, so I don't need to do this again. Now let's jump into some examples that I've prepared to show you how data is useful for multiple cases. But basically, data view, plug in supports four different format or output for your query, first is the list, table and tasks, and last one is the calendar view. So let's start with the list example. Here, if you want to write a data view query, you have to write this back text three times and you write the type of your code as data view, and then you start quering or asking Data view to query your nodes. So here have a simple example telling the data view to list all the nodes inside our vault. So here, if I just moved out of the data view way, I will have all the nodes inside my vault listed for me in this way. You can also have anoRview If you have a use case that requires a table, you can query your nodes as a table or view them as a table. So you just need to tell data view that you need all your nodes as a table, and you have to specify the table head. So here I'm asking Data view to list everything and to specify the type of the node and the arent of the node. Type and Barant or metadata or properties that I have attached to some of my nodes. So if we see this view, you will have here. So nodes like this have the type. So nodes has the type like this, and some of them have the parent and some note. So if you have value inside it, it will be displayed. If you don't have, you will have this dash or something like this. So let's have a look into this node, for example. And if we decided to change this to something else, let's say, it's a reference node, for example, and we try to get back to our query, you will see this change it dynamically here in the printout or in a table. Whenever you change something into your node, it will be changed here as well into your data view table or whatever you are using. So that's a simple example, how to use table. And let's say that we want to a property type, but we don't want to display it as type. Let's say we just want to display it as T. So using this sign text, you will have you will have your table heads displayed in a different way. So here, I have the type. It is still the same type, but with different naming, and also it's still the same property parent, but with different naming. So it's just like aliasing your property into something else. That's it for the table example. Now let's jump into another view, which is the tasks view. And let's try to look into how we can show all the tasks that we have inside the busing here. Whenever you have a task like this in your vault, you can list all of them via the data view. You can get back to the data view and ask to list all the Ruskes that we have inside our Obsidian vault. So for example, here, this will display all the Ruskes that I have inside my vault, and you can query them or filter them. So here, if I would like only to display the completed tusks, I would say tusks where completed. And now I will have all my completed tasks. If I would only see the tasks that are not completed yet, I would do it like this. Display all tasks we are not completed. So this should display all the tasks that are not completed. You can also attach Ametadta to your tasks the same way that we do for notes. So here I have attached a meta data called urgent to my task. In this way, you have to write square practice ones and write whatever key that you want. So here I have the key urgent and the value is true in this way. So getting back to the data view query, we can filter only where the task is completed, only when the task is urgent. So we can look for tasks that are only urgent. We get this only task. It is the only task that we have as urgent in my Obsidian vault. The last thing is the calendar example or the calendar view. You can queer your volt and get the result as a calendar. So here is a very simple example to get all the files, and they are displayed inside that calendar view depending on their creation time. Here I have calendarview and displaying all the files by their creation time. That's what I get out of it. Here I have the calendar. I have the files that I've created during those days. You can see that I've created multiple files on the 11th and two files on the 19th and so on. That's how you get this calendar. We saw what output formats that data view supports. Now, let's check how to filter the data that we get from data view with some examples. So let's start with the first way to filter your result is from. So let's say that I would like to list all the nodes, which has attack code project and also or attack code software design. So let's start with this part first. So here I will get all those nodes where they have this project tag and also I can get some other where they have the software design tank. Let's get back here. This query means I would like to list all the nodes, whether it has project tag or software design tank. So that would give us this list. Now, let's try to filter it even further by adding where let's specify also the type. We would like to get only the nodes where their type is literature. So I will get only those nodes. Here I have this note with software design tag and it also has the type literature. So that's how you filter down or narrow down your result using the data view. You can also take this one step further and you can sort down your results. So here I have almost the same query as above, but I only edit the sort command. Here I am sorting the files depending on their file size, ascending. You can also you can also do them descending like this. And with that, you get your nodes displayed on a reverse order. And that's it for daaview that was temple introduction to how to use it or some examples to how to use it and how to filter the results that you get out of data review. I also use data review on my personal volt to create some index note about a specific folder. So here, this, for example, I can create an index node or the project nodes that I have in my vault, I can also do the same with any type of tag that I have in my vault. It also helps me to identify some topics in my Zr custom. 15. Obsidian Vault Structure: As you make more and more notes, you will start to realize that you need a way to organize and categorize them, especially if you are using obsidian for everything as I do. I have notes not only about my learning, but also about work, learning, project management, and life tasks in general. And the first natural way to think about organization is to use folders. Then if folders are not enough, you start to even more subfolders and more nested folders. And then you might get the idea of creating a totally separate obsidian vaults for each main area of your life, like one for learning, another one for work related notes, and maybe another one for your tasks and planning. Seems right. Right? Not really. Having separate obsidian vaults will limit you in some ways. Way would be your ability to search across all your obsidian nodes. As you can search nodes only if they are in the same vault. The second way is that it will limit your ability to cross links different areas together, as you can also only link nodes when they are in the same volt. These are the downside to use multiple obsidian volts. If you are okay with that, you can use separate obsidian volts. I used them at the beginning, but they didn't work the way I wanted. However, don't be influenced by my choice and feel free to use whatever suits. I try to structure my notes at this moment is to use the Bara organization, which was introduced by Tiago Forte in his book, Building Second Brain. How I use Bara or Project Areas resources Archive. I have here my projects folder, which should contain short term collections of tasks and notes that are related to a specific project. For example, I have inside this project, a specific folder containing all the scripts and the presentation for this course. The second mail folder that I have is the areas folder where I have notes or tasks that I responsible for over a long period of time. For example, I have inside this folder, all family and work related notes. This is also where I store my journals and daily notes. The third one is the resources folder. That's where I store all my permanent notes or my main settle custom. Example, I have here my learning and all my technical nodes, and inside it, I have all the nodes are scattered. I don't have any folders, only one folder for my reference nodes, and other nodes are scattered in this way. It's completely flat folder with hundreds of files inside it because I don't need folders to organize them. Instead, I use index node to detect topics that emerge out of this chaos. Last thing in Para is the archive folder, which should contain all nodes that are not useful currently finished tasks or project that you don't need at the moment. If you don't need them now, you might do in the future. The archive is the safe place to store nodes and at the same time, avoid having your tasks and projects get cluttered. Have extra few folders that I use outside the barrel. For example, I have the inbox folder for all my zer cast and fleeting nodes, and I have other folder called acids for all the attachments that I use in my notes, for example, images or BD Fs and so on. And Excalidro is the folder for all my Excalidro drawings or presentations. And templates is for tela templates, and that's my current obsidian vault structure. 16. My Current PKM Workflow: So in this video, I wanted to share with you my current workflow of hike and make new nodes. First, let's start how I capture new nodes in my current workflow, let's say. So first, taking quick or fleeting notes. I usually have obsidian oven on my computer all the time. I also use recast Lancer in my Mci which has obsidian blogging that you can create a new obsidian notes from everywhere in your computer. So it's also very handy to use it. Some other time I take fleeting notes or quick notes on the paper index cards, and I bought them on physical inbox on my desk. And on later time, I usually process those notes in my physical inbox in my Obsidian inbox and move them if I need. It's also easy to do this in Obsidian, especially if you have hot key set for everything. So let's say that I have created a new node, and um and now I have my new node, and let's say that I have already processed the node, and now the node node type is now perment. So it's still in the inbox. But imagine that I want to move it. I already have a hot key to move nodes. I move my node to whatever folder I want by pressing Command, and I choose where I would like to put this new node. As easy as that, I process my inbox with the help of Hurkes. Of course, at the beginning, I need to write and rewrite the node into permanent node or a permanent state that would allow this node to live in my ziter custom. Moving and creating new nodes should be frictionless. So you should have this ready in your fingertips with hot keys. The second thing, how I take and capture literature notes or reference node from books or other I only use index cards and pin to do so. Even if I have this material is eBook or something like this. I usually print the epoch and start studying it. That helps me to avoid the distraction that comes from the Internet or any other application on my machine. I can get away with my paper and pen from the device distraction. Using ban and paper, especially index cards helps me in different ways. First, index card has a very limited space. So you have to think how you are going to fit this idea into this limited space. Also, it helps me to avoid passive copying or passive taking text from the book because as I mentioned, has a very limited space. Also writing or being forced to write slows you down, makes you think about what you are writing and how this going to be related to what you already have in your knowledge. Again, it makes me also think if what I'm writing makes sense or not, if it has any gaps or follow ups or questions that I need to add to it. After I finish my study session, I collect all those notes that I made on those index cards and then move them to my physical inbox. When the time comes to review my physical inbox, I rewrite them into Obsidian, allowing myself to rethink again about what I have taken and rewriting them again, maybe this time with more understanding, and I connect them with other notes that I already have in my Z I know this is a long slow process to study. Definitely, it is, but I prefer to study one book very well and understand its content rather than studying or reading ten books with a mediocre understanding. Another step in my workflow is very important one, which is a system maintenance. Usually, I have a fixed time to review my system every week or every two weeks. I review if there is something that I need to update or if I need to update some structure on my current workflow. But more importantly, I usually review my notes that I have with the help of data view to list all literature, reference, index, and permanent notes where I pick random notes and I start to review them and update them if needed. Sometimes I find some old notes that need to be spited down into multiple or some notes that I don't have enough metadata or probities that I need to add to them. By doing so, I make sure that my notes are always connected and serving me as I expect. More thing in my current workflow is the topic discovery. When I have many notes around a specific topic, I usually know from the gravie here, for example, you can see, you can see this area is somehow swiled around software design tag. That means that I have good amount of notes around the software design topic. Using this to identify what topics that can also be branched out of the software design is important. I know this from the grav view or even by intuition. Sometimes you know that you have written many notes about a specific topic, and you know that you need to review them and make an index note for them or even a mind map about this topic. One more thing that I share my technical and BM notes in my Github as open source notes. I have Github repository where I share them with whoever interested in this topic. I use Github to sing my main personal knowledge base. When I commit new thing or I commit a new commit in my Github repository, I have Abri commit hook that transfer any notes that is under resources technical and under resources PCM, then they are moved to another folder where I have my public Github notes. Then I commit those notes as well. And I have even website serving those notes on the Internet. So whoever is interested can check this website where I have all my public, let's say, Ziya however, I use Git and Github to sync my notes. I still use the Obsidian thing. You can know from here that I use Obsidian T to sync my notes across all devices like my phone and my iPad. It works very well for me, and it is relatively cheap at $4 every month. Also, good way to support the project or to support Obi. Thing that I want to share is that there is more blog ins that I use. For example, there is two that I want to highlight here. The first one is project blogging, which is helping me to organize and do project planning, and it is super easy to use. The second one is the Bretic notes. It's also very useful if you want to have weekly and monthly and yearly besides the daily notes that comes with obsidian, I usually use the weekly note. For my weekly planning and weekly tasks. And that is my current workflow. It is suiting my needs for now, but it also might change in the future. As my understanding and my needs change, feel free to copy parts that might help you to improve your workflow. And I would also like to know if you have any tips or improvements for my current workflow. Feel free to leave them in the commons. 17. Note Taking Mistakes: I started making notes seriously almost four years ago, and since then, I have made lots of mistakes. There are some that I would like to share with you, maybe that would help you also to avoid those pitfalls. First thing is Bacific copying, which is copying content from other places, putting it in your notes, and assuming that way, you have made a note because you have read about it once, which is completely wrong. And this leads to something called the Illusion of competence, which you assume that you understand something because you note about it or you have read about it, but actually it is just passed above your head. To avoid that, you have to actively make notes and to engage with the content that you are consuming. Making written notes, work is the best for me. Writing small and concise notes or paragraphs about what I have understood or my interpretation of that part of the content helps me to avoid this illusion of competence. Now let's move to some zit custom specific mistakes. The first one is to treat all your nodes as fleeting nodes. And just collecting lots of unprocessed nodes, this inevitably will lead to chaos, which will make you feel that you need to start all over again. To avoid this, you have to have a specific way to separate fleeting nodes from your main Zettle custom. As we mentioned, you can use an inbox to do so. However, you can go the opposite way and treat all your nodes as permanent nodes. Every single idea that you have, you write it down and try to connect it with other nodes by force or forcing yourself to connect ideas that are not actually connectable. This is state of unprocessed nodes, which is missing lots of details and follow ups and relations with other nodes can lead to the same chaos as you have on the fleeting nodes. So it is important to define what makes permanent nodes for you and what are the conditions to move a node into your permanent italcst booting a specific for your notes to be moved your main ittle custom will help you to identify when to consider a note as a permanent note. One more mistake is that you ignore the maintenance of your system. It is very important to maintain your tools, to be efficient in doing your job. Imagine a woodworker with all sow. He can't cut more wood unless he sharpen his saw. That is the same for your system. Make sure that you keep your uncluttered and sharp rigor by reviewing your notes, starting from your inbox to the index nodes and the topics that you already have. Check if some notes are missing some metadata that you have recently introduced. Heck if older notes also need to have new metadata or propities so on even just exploring your old nodes will give you a refresher of what you have written a while ago. You can also rewrite them with a new perspective. One last mistake is the tool obsession. Trying every single note taking application will not make you a better all of them get the job done. Just define what you need out of your tool. In this case, the note taking application and find the one that satisfy this criteria and start working with it and most importantly, stick to it. You don't need to change your note taking application every few months because there is a new one out there. All you need is to write more and more. Writing more and more notes make this critical note mess that will help you to generate new creative ideas. 18. How I leverage My PKB for Learning with NotebookLM: Since the AI and ELMs are taking over everything, including learning tools, I thought it might make sense to use some of them also in my learning. At the beginning, I use different Obsidian AI plugins. However, none of them worked the way I want. I wanted an interactive tool that could discuss with me my notes and propose more questions and challenge my assumption. But later, I found one tool which is not an obsian plugin. This tool is from Google called Notebook order to enable it to discuss your notes with you, you have to provide it with your node as the source. To do so, I collect the note about a specific topic and give notebook LM, this collection as a DF and later I can discuss this topic with notebook LM and define and challenge my ideas around this specific topic. How I do that, let's see, I start by creating a totally empty node. I will try to collect all the nodes about one specific domain driven design topic called bounded context. Let's rename this to be bounded. Context, collection notes. Okay. We would like also to search for all bounded notes that I have in my vault. So bounded context. So I have here one note about what is bounded context that is useful definitely. And let's look for more. So here, bounded context partnership. There is also bounded context. Subdomain. I know I have this, and bounded context. Let's look around. So there is also bounded context, context map, bounded context in real life. So I want all of them in real life. Oh, that's maybe that is enough for now. So how I convert this, I just embed the nodes as this and embed it like this. Again, like this. And here, I have all the nodes are embedded in this way. Maybe some of them have links to other nodes. We can also take those notes and bot them into our collection node if we want. One thing that you can also do, go for this node. Let's assume this is the main node for bounded context. And search for the relations or the links. So we can do this by opening the local graph for this specific node, and you can see it has some relation with other nodes. So make sure that you also include all those nodes on your collection node. Here, I would like to have bounded context. Shared kernel, also embedding it like this. We have another node about integrating bounded context with cooperation buttter. I can also add this to my collection node. And so on. So you get the idea. You add all the nodes that you want in this way. You can navigate them through the graph view. So for example, if we go to this node and open its local graph, we will have another nodes that are related to this node. So you can also include this node in your collection node. But for now, that should be enough for our collection node. And assuming that here is all my node that I want to challenge my understanding for it, or this is the topic that I would like to challenge my understanding of it. So after I have all this, I would export it to DF. And yeah, I would like to have it like this. So here, I went to notebook LM. I created the new node, and I uploaded my collection node as a BDF source. You can add source here. You can also try to add even more sources, not only your collection node, but you can also you can add also the book about domain driven design. For example, in this case, you can add also videos about domain driven sign unbounded context, anything that is related to the topic that you are trying to understand deeply and you're trying to challenge your understanding. Once you add all the sources that you want, you can add up to 50 source like this. And assuming that you added all your sources that you need, now Notebook LM will propose some equations for you to understand your topic more deeply. So let's assuming that you choose one of the questions that he proposes. It will go this way. I will take some time to go through your sources and give you some answers to your questions. You can also make Notebook to create a brief document about the sources that you provided. You can also make it to make you an audio overview about the topic and so on. There is also one let's say interesting feature in Notebook M which is generating audio padcast about the topic and about the sources you have uploaded. And also, you can generate this conversation between two AI or discussing the topic or the idea that you provided or the sources that you have provided. You can even ask them questions and they can answer you depending on that. It is really powerful tool to use Notebook AM. I'm not going to deep dive how to use every part of it. You can find, a lot of tutorials around Notebook LM. I just want to show you how to take notes from Obsidian and put it in notebook and sharpen your understanding of a specific topic from your notes. That's pretty much it.