Josh, I've watched so many videos and read so many articles to try and wrap my head around the "Self Referencing" technique within Templates, and after listening and following along with this tutorial, it finally clicked. I can't thank you enough! Subscribed!
Loving the more regular uploads. Your perspectives method has changed the way I use Notion, run my business, and have finally stopped me from template-hopping. Appreciate the work you do!
I came here for a tiny bit of info and now I am returning with a heap of info. Great explanation, great video, I'm so grateful to have come across this video.
This is great but I'm having a hard time understanding how this connects with your "Perspectives" methodology. Should we have a single database for all data or should data go into separate "Packs"?
Appreciate the question! Perspectives is all about how you VIEW data but your actual data is something different. This video shows you how to relate projects and tasks - perspectives shows you how to create a "mini-application" to manage those projects and tasks. You should be able to delete an entire pack and it doesn't touch your data, they're separate.
Whats the limit number of rows in this kind of database? If I have a small team and 20 tasks each week per person, that could be hundreds of tasks in a month, after year, for example 3000 tasks, 5 years - 15000 tasks. Is it still ok?
There is no hard limit that I know of (there may be an extreme one), you just may encounter performance issues. That's also dependent on the number of properties and types. Formulas and relations can slow things down so it just depends. All that to say, you won't break it, it just may load slower.
How do i make it so that i could use the same tasks in each project? Say all 5 tasks are the same in every project I do. If i tick it in project 1 it ticks it in all projects?
If 1 task is related to 5 projects and you check that task done, you are checking THAT task done - there is only one task. So no matter where that task is showing up, it will be done.
@@JoshRedd Ok. I have the same tasks needed in several projects that run concurrently. What’s the best way to implement that? The task is relevant to each project but isn’t completed due to start dates for instance, one may have started a month earlier and has 15 out of the 30 tasks completed and another may have 10 completed. Have you a video showing what I mean? Thanks and sorry for the long reply!
@@Pep2106 Im not totally clear on what you mean but I think the important concept to learn is that a database item represents ONE unique thing - whether its an idea, a task, a physical object, or whatever. It's unique. Even if you relate it to 5 projects, there is still only that one unique thing. So even if you have 5 tasks that are labeled the same, they are unique tasks and can each be completed separately.
interface: Scarlett 4i4 speakers: krk rokit 5's keyboard(s): Keychron k8 pro - have a ferris sweep though that Im learning colemak on microphone: marantz mpm 2000 mouse: MX master S dock: caldigit TS3+ Let me know if you want to know anything else, I should probably make a gear list!
Confusing. Also, zoom in on what you're describing. We don't need to see see you the whole time. Sometimes I glance at you a few times because you're talking instead focusing on what you're describing. But when I manually zoomed in and pushed you out of the frame, it helped. If you need to be in the video, then don't stick yourself in the lower corner.
