From DataViews to Bases in Obsidian  ## Metadata - Author: [[Remkus]] - Full Title: From DataViews to Bases in Obsidian - Category: #articles - Document Note: --- tags: [#Obsidian, #Productivity, #NoteTaking, #Databases] - #Obsidian - #Dataview - #Bases Author: Remkus de Vries Source: Remkus de Vries Blog Reference: [From Dataviews to Bases in Obsidian](https://remkusdevries.com/from-dataviews-to-bases-in-obsidian/) date created: 2025-07-02 12:05 --- # Title: 💾 From Dataviews to Bases in Obsidian ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis Prompt](#-darvo-analysis-prompt) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ## 📝 Summary: In this article, Remkus de Vries explores his transition from using Dataview plugin queries in Obsidian to the new Bases plugin, which offers a more visually intuitive and database-like experience for managing structured data inside Obsidian. He shares his personal workflow improvements, highlights the plugin’s features, and offers tips for users considering making the switch. ## 📖 Main Content: Remkus details his love for Dataview, a plugin that lets users create dynamic views based on metadata and frontmatter in Obsidian. However, he found the experience sometimes clunky and not very "visual." Enter **Bases**, a newer plugin that transforms data handling into something more akin to Airtable or Notion, with actual database views inside Obsidian. ### Key highlights: - **Dataview benefits**: - Powerful querying capabilities. - Flexible but code-heavy. - **Limitations**: - Steeper learning curve. - Less visual and approachable for non-coders. - **Bases advantages**: - Grid-like, visual database UI. - Easier data manipulation and editing. - Supports creating custom views (tables, boards, lists). - **Migration process**: - Not automated; requires manual setup but worth the effort. - Enables deeper connection between notes and databases. Remkus shares concrete examples from his own vault, emphasizing improved clarity and faster decision-making when managing large information sets. ## 🗒️ Notes - **Obsidian Dataview plugin** - Excellent for advanced queries. - Ideal for tech-savvy users. - **Bases plugin** - Friendly to visual thinkers. - Bridges gap between text-based notes and database-style organization. - **Workflow changes** - Moving from static queries to dynamic, editable interfaces. - Better overview of metadata and linked files. - **User advice** - Start small with a few bases. - Revisit frontmatter structures to ensure smooth transitions. - Embrace iterative improvement. ## 📖 References: - [From Dataviews to Bases in Obsidian – Remkus de Vries](https://remkusdevries.com/from-dataviews-to-bases-in-obsidian/) - [Obsidian Bases plugin](https://github.com/oleeskild/obsidian-bases) ## 🗣️ Paraphrase: 1. While Dataview offers robust querying for power users, Bases makes data more accessible by providing a familiar, table-like interface directly inside Obsidian. 2. By switching to Bases, users can interact with their data in a more intuitive, visual way, ultimately streamlining their workflow and making complex information easier to manage. ## 📰 Newsletter: 💌 **This Week in Tools & Workflows** Remkus de Vries takes us inside his Obsidian vault to showcase a big shift: moving from the beloved Dataview plugin to the sleeker, more visual Bases plugin. If Dataview felt like a Jedi-level puzzle, Bases might be the approachable droid you were waiting for — clear tables, drag-and-drop ease, and database vibes without leaving your notes. For Obsidian power users and beginners alike, this piece offers a fresh look at blending notes with structured data. Check it out ➡️ [Read here](https://remkusdevries.com/from-dataviews-to-bases-in-obsidian/) ## ✅ Action Items: - Evaluate opportunities to integrate Bases plugin in personal and team Obsidian workflows. - Consider workshops or tutorials highlighting the transition from Dataview to Bases for WordPress contributors and open-source documentation teams. - Share migration tips and design guidelines to encourage better structured knowledge management in WordPress community spaces. - Incorporate visual database tools to support onboarding new contributors who prefer non-code solutions. ## 🧪 Hypotheses: - Users adopting Bases over Dataview will experience higher satisfaction and lower friction when managing metadata-heavy vaults. - Visual tools like Bases can increase adoption of Obsidian among non-technical users. ### 📊 Methodology: - Conduct user satisfaction surveys pre- and post-transition to Bases. - Measure time saved during data entry and retrieval tasks. - Analyze qualitative feedback from new Obsidian users introduced to Bases first. ### ❓ Questions: - How can visual database tools like Bases encourage new contributors in open source to better document their work? - What best practices should be established when transitioning from code-heavy queries to visual tables? - Could Bases-like interfaces be integrated into other open-source documentation tools? ### 🔮 Future Research: - Explore automated migration tools from Dataview to Bases. - Study long-term impact of visual-first plugins on knowledge retention and contributor engagement. - Assess scalability of Bases for very large vaults. ### 💡 Implications: Switching to more visual data handling tools may democratize advanced note-taking workflows, enabling broader adoption and smoother onboarding of diverse contributor types. ### 🧠 Learning Styles Assessment: - **Visual**: Strongly supported with grid/table views. - **Aural**: None; could include tutorial videos. - **Verbal**: Clear explanations; could include more narrative examples. - **Physical**: Low; suggest adding exercises to build bases step by step. - **Logical**: High; logical structures and data connections are explicit. - **Social**: Could add community examples or shared templates. - **Solitary**: Supports individual experimentation and iterative setup. - **Naturalistic**: Not addressed; could add nature metaphors to illustrate systems. ### 📊 Accessibility Assessment: - **Screen reader compatibility**: Need to confirm plugin accessibility for screen readers. - **Keyboard navigation**: Important to verify for Bases grids. - **Contrast/readability**: Check UI color choices and text contrast. - **Text resizing**: Ensure responsiveness in the plugin UI. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Cultural Relevance**: Neutral; could highlight global user examples. - **Inclusive Language**: Friendly and open. - **Neurodiversity Support**: Visual approach supports non-linear thinkers; could simplify instructions further. - **Representation**: Could share diverse user testimonials. - **Psychological Safety**: Supports experimentation; encourage more explicit invitations to try without fear of failure. ### ✅ Logical validity: - **Positive reasoning**: Builds clear case for usability benefits. - **Fallacies**: None detected; arguments are transparent and experiential. - **Tone**: Friendly, personal, and informative. ### 🔍 DARVO Analysis Prompt: - **Deny**: None; acknowledges Dataview strengths. - **Attack**: No hostility toward Dataview or its users. - **Reverse Victim and Offender**: None; no shifting blame. - **Conclusion**: No DARVO elements; content is honest and constructive. ### 🔍 SEO Evaluation: - **Keywords**: Strong ("Obsidian," "Dataview," "Bases"); naturally used. - **Meta description**: Effective; suggest refining to highlight benefits. - **Title tag**: Clear and targeted. - **Headers**: Good; could add more keyword variations. - **Content length**: Solid; consider adding screenshots or GIFs - Summary: I’ve talked about this before, but in case you didn’t know, I use Obsidian as my main Notes app. It’s like any Notes app, but on steroids. And I do mean, proper roids like Test + Deca. It’s wild what you can do with it. Obsidian allows me to have a second brain that is […] - URL: https://remkusdevries.com/from-dataviews-to-bases-in-obsidian/ Background pattern I’ve talked [about this before](https://remkusdevries.com/apple-notes-on-steroids/), but in case you didn’t know, I use Obsidian as my main Notes app. It’s like any Notes app, but on steroids. And I do mean, *proper* roids like Test + Deca. It’s wild what you can do with it. Obsidian allows me to have a second brain that is aiding every single thing I want to record, remember, or list up. For many of my templates, I am using a Community plugin called [DataView](https://blacksmithgu.github.io/obsidian-dataview/). It allows you to do what the name says: create all kinds of fancy ways to view data. It’s pretty great, but it has its limits in its complexity and performance hits. So when Obsidian announced [a new feature called Bases](https://help.obsidian.md/bases) as a tool to display data stored inside Obsidian, my interest was piqued. I hadn’t found time, beyond exploring the simple things for bases, just yet, but today I switched a section inside my Daily Notes template from DataView to Bases. #### DataView -> Bases At the bottom of my Daily Notes template, I display all the Notes I’ve created that particular day, as well as the Notes I’ve touched. Now, I’m not going to bore you with what my DataView + Templater code looked like to make this happen. I’d rather just show how this works with Obsidian’s Bases. ##### Step 1: Create a Shared Base File Create a new file named, for example, `daily-activity.base` in your vault. Add the following content: ``` views: - type: table name: Files Created Today filters: and: - file.ctime.date() == this.file.ctime.date() - type: table name: Files Modified on This Day filters: 'file.mtime.date() == date(this.file.name.slice(0,10))' ``` This Base defines two views: * **Files Created Today**: Lists files whose creation date matches the creation date of the current file (i.e., the Daily Note). * **Files Modified Today**: Lists files whose modification date matches the creation date of the current file. By using `this.file.ctime.date()`, the filters dynamically reference the date of the Daily Note in which the Base is embedded. ##### Step 2: Embed the Base Views into Your Daily Note Template In your Daily Note template, embed the views from the `daily-activity.base` file as follows: ``` ### 📄 Files Created Today ![[daily-activity.base#Files Created Today]] ### 📝 Files Modified Today ![[daily-activity.base#Files Modified on This Day]] ``` When you create a new Daily Note, these embedded views will display the files created and modified on the same day as the note. ##### Additional Tips * **Date Format Consistency**: Ensure your Daily Notes are named using the YYYY-MM-DD format. This naming convention aligns with the date comparisons in the Base filters. * **Excluding the Daily Note Itself**: If you prefer to exclude the Daily Note from the lists, you can modify the filters in the Base file to add a condition that excludes the current file. Be aware that this only works in Obsidian 1.9.x, and at the time of publishing this blog post, this version of Obsidian is only available if you’ve paid for [a Catalyst license](https://help.obsidian.md/catalyst). It will become available in the public and free version soon enough, though., From DataViews to Bases in Obsidian, Remkus, 01jz5rhtf2zk20q0cc7vhg08w7.