Accessing dataview API or database outside of obsidian #1811
rufuspollock
started this conversation in
General
Replies: 2 comments 1 reply
-
Not exactly what you are looking for, but in case others stumble here looking for similar solutions: on macOS / iOS there is Actions for Obsidian which can access Dataview to get Lists and Tables. |
Beta Was this translation helpful? Give feedback.
0 replies
-
An update from our end: we ended up building our own lightweight standalone (SQL-based) API for markdown files called MarkdownDB: |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
UPDATE: 2023-10-11: we ended up building a simple standalone (SQL-based) API for collections of markdown files called MarkdownDB - see https://markdowndb.com
First, massive appreciation for this plugin. 🙏
I'm trying to understand if one can use dataview indexing and database outside of Obsidian (more context below). Talking here about reading i.e. accessing the index and doing queries. Not about any rendering of dataview blocks etc..
Related to that, trying to understand a bit more about overall design/architecture of dataview and how it would support this or not.
Note: have done quite a bit of digging around the code and the discussions before asking - apologies if we missed something obvious! 🙏
Three main questions
More specific related sub-questions are things like:
Asides / Bonus
Comments
We have done a bit of digging around the code. So far, our investigation suggests this is not possible e.g. core functions like parsePage seem to depend on being passed items from obsidian core database e.g.
CachedMetadata
. Is that right?Our Context
To give context, we're working on Flowershow, which is an open source tool for publishing markdown and digital gardens especially obsidian. Our tool is React/NextJS based and renders to static content.
When rendering your digital garden to html we need to build an index of the content to prep for rendering.
At the moment, we're having to "reinvent the wheel" in terms of creating our own "content layer" API over the markdown content.
Obviously, obsidian and especially this plugin already do an excellent job of indexing markdown content and extracting metadata including backlinks. We'd love to reuse that work rather than have to rewrite.
In a perfect world, we could reuse obsidian and dataview API outside of obsidian to directly access the indexed content and metadata.
Bonus: if we could access dataview somehow we could even render dataview queries on publishing which would be awesome (see our issue) 🚀
Beta Was this translation helpful? Give feedback.
All reactions