I am new to the Obsidian community and this is my first post. So, I am very humbly offering my thoughts here as a point-of-view. I do so because I have a keen interest and hope for using obsidian as a knowledge-content management “tool” in a workflow spanning from post-capture of a reference source into ref mgmt syst (Zotero in my case), to the point of publishing articles, books and web content — all with content continuity.
I come from the Scrivener, Notion, Roam Research worlds as a reference point with great hope Obsidian intends to become such a tool on the longer end.
My attraction to Obsidian is its plain text, local file, interlinking knowledge graph design center for all the many reasons these are valuable, and these are the decisive reasons that warrant the investment of time differentially into learning, using and helping to advance the dev of Obsidian.
The paramount goal for me, and perhaps others here, is to end up possess a “knowledge-content creation workflow management system” on the long-end. The attraction to Obsidian in it having the base attributes mentioned above, and the potential for becoming such a system spanning functionality from content capture, to coding (classifying, tagging), content revision and maintenance, content inter-linking, content exploration, analysis and publishing.
This would mean Obsidian supporting a workflow that can would:
- continuously build up a universally useful and accessible inter-linked, content-classified personal-professional knowledge-graph, and in so being
- provide a tool useful for doing productive knowledge processing, content creation in service to our personal and career work needs
- provide note functionality across the entire knowledge-content workflow from ideation to content analysis, creation and publishing of ongoing works, in all contemporary forms.
Note taking is vital to this, but hardly a “whole-product” solution or platform.
As a result, IMHO there are a couple of points in this discussion that while notable for being valid, seem vector away from clearly inform Obsidian development objectives in regard to WHAT independent of HOW:
- Argentum, I believe you are 100% correct in saying that Obsidian should not seek to build and become a replacement for current reference management apps
- However, needing Obsidian to be a note taking and using app that is low friction, productive and value-adding in using and syncing content that exists in reference mgmt and other apps critical to meet user content-knowledge management workflow, is another matter.
- Yes, the needs of note-taking and reference management are different, but both are essential needs within any users singular but broader workflow.
Please forgive me for applying the metaphor, that if one needs and wants a hole put into something “to do their real work,” then that alone is the reason they will or should buy and use a drill. Obsidian is a drill. Therefore, creating and getting notes, citations, et al. into Obsidian is not the end goal, nor does the content used in our workflows, start or end in Obsidian.
Moving content through obsidian from external input to external use and end points of our workflow, effectively and efficiently, defines (in my view) the primary function of Obsidian or any such note-taking tool. This being even more so true for Obsidian because they are developing knowledge-graph functionality, and their revenue and business model is dependent upon the publishing end of such workflows.
In the end, I think this actually makes the point I am trying to highlight, indicating that for any next generation note taking tool to fill real world user needs, means doing so within real world user workflows. Especially those that lead to publishing. It would seem then that any such app logically be able to pull, use-modify and output not just reference management content and metadata. But, also do the same more broadly to and from apps that perform qualitative and statistical data analysis and others function needed by and before the publishing and presentation stage.