Really appreciate the original content you are creating. While I enjoy other creators, it is really refreshing to see advanced use videos. Some of us are interested in learning some of the tricks/strategies/fresh ideas that you don't find other places. Keep them coming, please. I just found your channel and am watching your videos back to back, and already excitedly anticipating watching them a second time when I implement some of them.
Thank you for this! You taught me something…I didn’t realize I had the ability to rename a property in the back link of a linked database when I’m setting it up. Never saw it I guess. I can’t wait to use this. It’s a game-changer. Thank you!
Hello Matthias! Thank you for all the effort you put into your videos! I love the way you are thinking about organising notion. I would not come up with such an approach! I am currently starting to rebuild my notion from hierarchically structured pages to databases. And here comes my question: I have watched the video where you suggest having only 3 databases which run the whole workspace: projects, tasks and documents. However, won't Document database get unbearably HUGE if I store all my knowledge in there? There would need to be a dozen of general tags to systemise the knowledge which at some point will become a mess. Can you share any approach on how to decide whether data needs a separate database or not? Eg, in this video you have mentioned input and output databases. Maybe can you give an example on how to unite knowledge (courses, articles, studies, movies,recipes, planning etc) from all spheres of one's life in notion database?
Oh yes, it would get huge! But typically, using meta data like tags and type should be enough to break it down through views Usually, there are two criteria for breaking something into several databases despite being a similar data type 1) access rights 2) different meta data For example if you have 10 unique properties for recipes that aren’t used on anything else, you probably want a separate db for that 😇 Then just make sure to use global tags if you still want to be able to connect information across databases 💪🏻
@mfreihaendig @mfreihaendig Thank you for your reply, Matthias! I have recently found your blog and saw a post there about personal knowledge management! I will study it and then try to incorporate the obtained knowledge to build a suitable database for me🤓 Looking forward to your video about PKM!
Great work Matthias as usual! Knowledge tags are key. Now these global tags are global indeed which means that, when you want to write a specific article, the global tags are too global. I have sub-tags inside the global tags to segment the main topic into different areas. it would be nice to show how to apply your methodology to sub-tags. I personally have “corporate finance” as a global tag and inside this tag i have plenty of sub-tags like “EBITDA” for example. So if I want to write an article about EBITDA, I need to see all the articles related to the sub-tag “EBITDA” and not to the global tag “corporate finance”
Ah interesting! At first glance, I would create a relation within the global tags database for sub-items. Then, you can group tags below a parent tag and when adding something you can apply the specific child tag. This would even allow you to show two things - the articles with the same child tag and all articles that share the same patent tag 💪🏻 Will probably expand the blog article with this ☺️ thanks for the food for thought!
@@mfreihaendig did you write anything about it? I tried to put this sub-item thing, but there is something that doesn't add up. actually, I think it's almost an obligation if a topic starts to have dozens and dozens of related contents
Excellent tutorial and super useful. How would you about adding a third database (fourth if we include the global tags database)? Would you have to make each one connect to the other two? And scale that up for each additional database?
No that’s the beauty of the system! Each new database only requires a connection to the global tag database, so it scales much better ☺️ The one exception: if you want to pull data not just into the global tag but through it into a database (as shown in the last third of the video), then you need to create the additional roll-up to be able to filter properly 💪🏻
Thanks for this interesting video! One non-related question: how did you split the screens to left and right (12:36) on a mac, without using full screen? 🙂
love the general idea but how would you manage tags that are specific to each database. Would you still create them as Select/multi select? E.g. ingredients, musical genres w. sub-genres (my own use-case for now) OR would you further develop a Global Master Tag database?
You have two options there: 1) if you know that there is no way a tag would ever be used outside a single database, you can keep things simple and create them locally 2) you could still create them outside if you‘re unsure But as with all things Notion, nothing is set in stone. Try local, see how it goes and if you later need it elsewhere, you can just expand the system 💪🏻
why not use a wiki instead? I mean if you add all your pages in there, they work like a database, but you can interlink every single page and use the multi-tags feature since the pages have their own unique properties with a wiki.
A wiki at its core is simply a Notion database with slightly different features (like unique properties and the ability to store databases inside databases) But it doesn’t help you connect pages without without having to make the individual connections. If you have 10 articles about productivity and 2 essays you write, you’d need to connect all 10 articles to both essays (20 connections) With global tags, you connect everything to the tag productivity (12 connections) As your workspace scales, you’ll have exponentially more connections if you want to achieve the same results
@@mfreihaendig na man, I am saying, why not have a multi-tag property in that wiki and add "productivity" as a label/select, and then js apply it to the whole thing? That way, there can be a better interconnectivity. You can have multiple tags in a single wiki.
@@HarshitKhemani Ah yes, fair point that would be possible - but you couldn't automatically filter for connected things on that page For filtered views on Article A, you couldn't automatically show all things that have the same tags. Instead, you'd need to manually set the filter for the tags applied to Article A and update that whenever you apply new tags, whereas here, it does that automatically 💪🏻 If you don't need that functionality and just want to cross-reference things though, Wiki would definitely be an alternative ☺
What if a new database relationship has been created with global tag. I already applied the new global tag template to some of my tags. How can the new table has to be reflected for older tags?
Could you share a few more details? Generally, you would update the template and then „reload“ it on the old pages by deleting all the body content and then re-applying the template (only deleting the linked instance of the views of course, not the actual entries)
@@mfreihaendig Say I created two databases by name: Color, Shape. I have two tags tag1, tag2. I created a global tag database and created a relationship for Color and Shape. Then created a template and in that template created two linked databases for Color and Shape. After few days created a 3rd database by name Number. Created a relationship in the global tag and updated the template by creating a linked database for Number. But this Number linked database is not applying for old tags. It would be better if there is an option for this
Definitely similar, but I would set it next to them! Areas and resources usually have fairly defined roles and the beauty of the more general approach is the flexibility 😇
Haha nope - my surname is Frank 😂 but that’s so common that the social handle is taken pretty much everywhere, so I had to come up with something. Not saying freihaendig was a good choice but it is what it is 😂😂
