Up: [[1 Atlas]] # 1a Maps of Content Maps of Content or MOCs are a fundamental component of the LYT approach to note-taking. If you're new to [[p003-3.1 Obsidian|Obsidian]] you've almost certainly come across the LYT framework. a MOC is meant to be a Hub note, that captures all of your notes on a topic. [[6 Spaces/Life/3 Projects/03 Personal Knowledge Management/p003-2.1 Niklas Luhmann|Niklas Luhmann]] did utilise summary notes, but giving it a succinct and actionable title didn't come until [[p003-2.3 Nick Milo|Nick Milo]] gave it a handy title, and a brilliant use case in the framework. One of the challenges that come from a Maps of Content, is that it creates an artificially large note on the graph, and everything links back to that - for some people this is great, and I encourage that approach - it helps with the concept of [[p003-2.3b Idea Emergence|Idea Emergence]]. I don't love having to update a parent note all the time. The best way to do this would be with the [[6 Spaces/Life/3 Projects/03 Personal Knowledge Management/p003-3.1b1 Dataview|Dataview]] Plugin. Dataview will allow you to create a query that runs over your notes looking for specific items. Dataview however doesn't create "true" links back to that MOC note, but it does automate the process of linking it back to a central note. So there will be no reflection on the graph view, and there will be no reflection on the backlinks pane. The other note to make here is that [[Obsidian Publish|Obsidian Publish]] doesn't currently support Dataview as a plugin and so won't work should you upload your MOC to the publish site. You can then keep the link by linking the MOC in your base note, so the backlink exists. Further a MOC of a topic can have "SubMOC's" which are more targetted to specific segments, eg. AI MOC might have a SubMOC of Machine Learning. I tend to drop the super parent note out of the links and link instead to the SubMOC, as that helps get more targeted idea emergence. --- ## Key Points - Links all the notes back to a central point. - Dataview Hub Notes - Overviews - Logs ## Dataview This code block requires your TaggingFu to be pretty tight - it will grab any note in your vault that has this tag. For example the tag used on this is #ACCESSMethod to try and align all notes in this project to that and update my MOC dynamically as I continue through the process. ``` ## Topic Heading ```dataview LIST FROM #your-topic-tag SORT file.mtime desc ``` ## References ## Related Notes [[6 Spaces/Life/3 Projects/03 Personal Knowledge Management/p003-1.1e Maps of Content MOC]] [[6 Spaces/Life/3 Projects/03 Personal Knowledge Management/p003-3.1b1 Dataview]] [[p003-2.3 Nick Milo]] [[6 Spaces/Life/3 Projects/03 Personal Knowledge Management/p003-2.1 Niklas Luhmann]] [[_hub Access Method]] ## Tags #PKM #ACCESSMethod