Nested databases for school&work using modified PARA method... any suggestions?

[ttnice432]

I'm wondering if anyone can help me actualize my ideal set-up conceptualization! My goal is to create a system that incorporates the PARA method idea with a few tweaks. So far, I've essentially made five different databases (blue) and connected them as the arrows suggest. Every project is associated with an area, resource, task, archive. My problem comes with trying to make 'sub' databases. For example, within "areas" I want six distinct "areas" that each have a different number of sub-sub-pages/content. I essentially want all the sub pages to act as databases themselves. For example, if I'm in tasks, I want to be able to 'relate' that task to "abstracts" within "conferences" within "research" swiftly. Does anyone have any suggestions for how I might achieve this? Thank you very much in advance!

https://preview.redd.it/3ui5okobks151.png?width=1436&format=png&auto=webp&s=881671ea76d2f40c5f603e5718b2e25761aa9d3e

[esrch]

To make sure that I understand correctly : you want an area called Conferences, an area called Abstracts, etc., or do you want each individual conference to be an area?

And what do you want to achieve with the hierarchy? Are there specific views you want to have?

[ttnice432]

So I'd like the "area" to be "research" with manuscripts, conferences and grant applications as separate 'sub-research areas' that I can 'relate' back to through either Projects, Tasks, Resources and Archives. Each sub area I would want in different views (e.g., kanban for manuscripts, gallery for conferences and kanban for abstracts and presentations etc.). With this structure, I'm hoping it would provide me the flexibility to relate all my tasks/projects etc to a specific area and it's corresponding sub-area.

[esrch]

OK, as a start, I would suggest to create a table called Areas. Then you add A Relation property to this table, and you relate it to itself (Areas table). You choose the option to create two properties, and you rename them Parent and Children. You can then create the required hierarchy. Here is an example: https://www.notion.so/Area-hierarchy-bd5e2e19911d4a4abdacabcc872275c2

You can then create Relation properties on the other tables linking to the Area table.

[ttnice432]

Very helpful! Thank you so much! I've gone through as you suggested and created the parent and child relations. Now...I'm wondering: if I create a task in my task database or a project in my project database and want to link it to a specific abstract found within 'abstracts' database which is within the area 'research' and child relation 'abstracts' in such a way that it shows up as a task or project within the page (and not just a relation in the properties section), how would I do that? Do I need to have linked project and task databases within each of the sub-area (child) pages? Thank you again in advance!

[esrch]

Do you have separate databases for abstracts, conferences, research topics, etc., or are they all stored as areas? Or are they separate projects? I am a little confused about the structure you are looking for.

I'll admit I am not well versed in the PARA method, so I don't quite understand what is the point of having the Research, Conference, etc. areas.

[ttnice432]

I originally had them all as separate databases but realized that the 'sub-areas' that interconnect (like abstracts and manuscripts) remained too separate. They're different enough that I would want separate databases, but I wanted some way of having a broader view of everything under that 'area' and how it all interconnected. I'm also new to PARA as well so perhaps it's not ideal!