![]() So, it can be now understood, all Readings pages must have the lecture field. In Notion, the relation link appears bidirectionally. Lecture pages are higher in the hierarchy but the linking in done in two ways: reading->lecture and lecture->tutorial.Įach arrow represents a field+link here. It is evident that the Readings page has field+link to the lecture(s) and the lecture pages themselves have the field+link to the tutorial pages. I will make this two connection in two ways that it can be made.įile: ] ~ changes made from above category:: lecture Proceeding with an example, let’s consider our course MAT101 has some lectures attached to it.ĭate:: each lecture has some pre-lecture reading and post-lecture tutorials. Only in one of the pages the field+link can be made, and if the practice is not made properly, the database can break. Relation (for example Relation in Notion Databases) is not bidirectional in Dataview. Thus we have already prepared a relational database connection with teacher and course. This course is taught by `= this.teacher`, available at `= `. Table subject, syllabus, teacher, teacher.mail ![]() We start now creating typical pages for each category: Title: Semester 1 Here, Categories (each being a separate database or group of pages) Each page must be organised into a specific database, though some field, most appropriate might be a hash#tag, but to reduce clutter one may use a category: field. In Obsidian Dataview, creating separate databases must be created through creating notes(or pages). I am taking a toy example of a college hub to go though this process. The complete documentation looks like this:ĭownload a copy of this Notion template and click on the Colophon to see the documentation diagrams.Tags: Share-and-Showcase Toying with Relational Databases using DataviewĪssuming a prerequisite knowledge of Dataview and Relational Databases, for example the ones in Notion, we proceed to their implementation using the Dataview plugin. On Products, I document “Purchased by” as rollup-Customers-thru-Orders. That calculates the order total from the sum of the Products prices. □ĭefine formulas as attributes. You can add formulas as attributes to entities, using type and name. So on Orders, I create a Notion property called “Rollup Total,” and document it as rollup-sum-Products-price. These one-or-more, zero-or-more relations create charming links between entities called Crow’s foot notation. Although Notion can’t enforce it, it’s worthwhile to consider the relationship type: an Order has to have a Customer, but a Product might not have an Order. These might be one- or two-way - Products appear on Orders and Orders are displayed on Products, too. Notion uses the Relation property type to hook up databases. We’ll use just enough to show the big picture of our complex Notion database.ĭefine the entities. By convention, I first letter cap the databases Customers, Orders, and Products.Įstablish relationships. Add a code block on your docs page and set the language to Mermaid.Įntity-Relationship Models are often used in software engineering: imagine whiteboards full of boxes and arrows. Mermaid lets you create diagrams and visualizations using a markdown-like plain text syntax. We can create a visual diagram showing all the tables, relationships, and calculations and maintain it with Notion.ĭemo time! Let’s use the quintessential example: Customers place Orders for Products. To understand a template, users have to click on relations, rollups, and formulae, just to get the big picture of how things relate. Everyone’s favorite “no-code” tool, Notion, can get surprisingly complex.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |