diff --git a/apps/website/content/obsidian/use-cases/_meta.ts b/apps/website/content/obsidian/use-cases/_meta.ts index a05edbcf1..3d232508d 100644 --- a/apps/website/content/obsidian/use-cases/_meta.ts +++ b/apps/website/content/obsidian/use-cases/_meta.ts @@ -7,7 +7,6 @@ const meta: MetaRecord = { "Synthesize Insights from the Literature", "share-your-ideas-and-research": "Share your ideas & research", "track-your-projects-and-experiments": "Track your Projects and Experiments", - "experiment-tracking": "Experiment Tracking", }; export default meta; diff --git a/apps/website/content/obsidian/use-cases/build-utilize-personal-knowledge-base.mdx b/apps/website/content/obsidian/use-cases/build-utilize-personal-knowledge-base.mdx index 57d1a0a20..494f1027f 100644 --- a/apps/website/content/obsidian/use-cases/build-utilize-personal-knowledge-base.mdx +++ b/apps/website/content/obsidian/use-cases/build-utilize-personal-knowledge-base.mdx @@ -1,5 +1,5 @@ --- -title: "Build and Utilize a Personal Knowledge Base" +title: "Build and utilize a personal knowledge base" date: "2026-06-29" author: "" published: true @@ -32,7 +32,7 @@ For Obsidian (& Roam), the answer is **yes**. Your discourse nodes can coexist w ### Vault organization -If you are a **"folder-centric"** Obsidian user, we recommend keeping your discourse graph an folder within your vault. +If you are a **"folder-centric"** Obsidian user, we recommend keeping your discourse graph a folder within your vault. graph view @@ -127,7 +129,7 @@ First, paraphrase the key insight of the note and record the source of the insig _CLM node with SRC node attributing a blog_ -In the above image, you can see the a second related Claim and its Source has already been extracted from the same web clipping. If you decide to pursue this topic further, you've already identified another Source node to investigate (Klein _et al._) +In the above image, you can see that a second related Claim and its Source has already been extracted from the same web clipping. If you decide to pursue this topic further, you've already identified another Source node to investigate (Klein _et al._) Adding `[[wiki-links]]` to key terms will keep your new node in conversation with the rest of your vault as you build your graph. This can help you to find appropriate [discourse relations](/docs/obsidian/core-features/creating-discourse-relationships) later. @@ -167,6 +169,8 @@ You can jumpstart the process by identifying [candidate nodes](/docs/obsidian/co width={786} height={795} className="docs-bordered-image" + sizes="500px" + style={{ width: 500 }} /> _So much room for activities!_ @@ -205,7 +209,7 @@ This habit of intentional reading is a great way to nudge yourself toward [contr className="docs-bordered-image" /> -If you're using a highlighter like [memex](memex.garden) or the [Obsidian web clipper](https://obsidian.md/clipper), you can +If you're using a highlighter like [memex](https://memex.garden) or the [Obsidian web clipper](https://obsidian.md/clipper), you can 1. highlight the relevant text 2. bring it into your vault via the tool's import feature or copy-paste @@ -239,7 +243,7 @@ Similarly, plugins like [Zotsidian](https://github.com/Qiwei-Zhao/zotsidian) ena className="docs-bordered-image" /> -After you've captured capture a few ideas, you can mark those that you might want to add to your graph later as [candidate nodes](/docs/obsidian/core-features/node-tags). The _progressive formalization_ ethos of the discourse graph protocol also applies to the process of deciding how to direct your attention: you can have a number of leads on potential projects active at once, and decide which ones to curate further later. +After you've captured a few ideas, you can mark those that you might want to add to your graph later as [candidate nodes](/docs/obsidian/core-features/node-tags). The _progressive formalization_ ethos of the discourse graph protocol also applies to the process of deciding how to direct your attention: you can have a number of leads on potential projects active at once, and decide which ones to curate further later. bases and datacore + +_The template depicted here includes one Base and two Datacore features: an aliasing widget and a log widget_ + +### Bases + +Bases are Obsidian's native database layer. They can be used to filter your notes by frontmatter property. They do not require any code to maintain, but they cannot be used to peer into note content: this limitation makes the design of your notes' frontmatter content especially important. + +source base + +_Source Base_ + +### Choices, choices + +So when should you use Bases vs Datacore? The following table can help you develop a sense for the appropriate tool: + +| Task | Tool | +| ---------------------------------------------------------------- | -------- | +| Kanban active lab Projects by Status | Bases | +| Source/Evidence intake triage | Bases | +| Count EVD per CLM | Bases | +| simple self-serve dashboards | Bases | +| Modeling Supports/Opposes as reified, queryable relations | Datacore | +| Reading Evidence bundles nested as sections in one file | Datacore | +| Anything using inline (`::`) fields from a synced/exported vault | Datacore | +| Custom widgets | Datacore | + ## What else would you like to do? - [Synthesize Insights from the Literature](/docs/obsidian/use-cases/synthesize-insights-from-literature) diff --git a/apps/website/content/obsidian/use-cases/share-your-ideas-and-research.mdx b/apps/website/content/obsidian/use-cases/share-your-ideas-and-research.mdx index ab49111f9..f9eea2969 100644 --- a/apps/website/content/obsidian/use-cases/share-your-ideas-and-research.mdx +++ b/apps/website/content/obsidian/use-cases/share-your-ideas-and-research.mdx @@ -30,7 +30,7 @@ We've just added a feature to allow you to share "live" nodes with your collabor -_While the data speaks for itself_ +_... while the data speaks for itself_ ### Arguing with your graph @@ -148,7 +148,7 @@ Your discourse nodes should be formulated as concisely as possible (remember nod -Learn more about creating and tracking experiments [here](/docs/obsidian/use-cases/experiment-tracking). +## How to use Experiments + +The **Experiment** is a container for your day-to-day work exploring a **Hypothesis.** It consists of an **intervention** and a **metric** used to track the result of that intervention. The **Result** is a statement of your observations regarding that intervention in terms of the appropriate metric. + +Making an experiment page helps you track multiple days' work and reflect on your progress towards your experiment target. +Ideally the target is a **Hypothesis** you are testing, and the experiment page is a space to document and reflect on **candidate results** for that hypothesis. + +### A quick word on candidate nodes + +**Candidate Results** are preliminary observations attached to a particular experiment. They might be first impressions formed from a certain data artefact. Use this tag to mark candidate results: + +**Candidate Issues** surface potential problems or future experiments. Use this tag to mark candidate issues: + +When you're more confident in the observation, you can use the "Create Discourse Node" popup to convert the candidate result into a proper Result. This will affect where the Result appears in queries and its appearance on your Project Canvas. It will also give you a warm sense of accomplishment (this can be done to mature all candidate node types). + +### Creating experiments + +You can create a new experiment by + +1. Creating a new note and applying the Experiment Template from the Templater menu in the left sidebar + +templater flow + +2. Navigating to your "Experiments" base in the "Bases" folder and selecting "+ New" + +bases flow + +3. Using any of the methods to create nodes (Remember, an Experiment is a type of **Source**) + +### Experiment relations + +As a **Source** node, the **Experiment** has a special relationship to **Result** nodes: the **Experiment** _produces_ **Results**. + +Conversely, each Result in your graph should reference an Experiment. + +The Experiment also has a relationship with the **Issue** node, as Experiments _suggest/produce_ **Issues** that may later be developed into Experiments. + +iss-exp relations + +### Transforming an Issue into an Experiment + +If you decide an Issue captures something worth doing, you can easily change it into an Experiment: the **Issue** template is identical to the **Experiment** template, so you can either duplicate the node and change the name and metadata to use your preferred EXP syntax (e.g. "@measurement -") or simply edit the title of the Issue in place. + +issue example ## What else would you like to do? diff --git a/apps/website/public/docs/obsidian/bases+datacore.png b/apps/website/public/docs/obsidian/bases+datacore.png new file mode 100644 index 000000000..283268138 Binary files /dev/null and b/apps/website/public/docs/obsidian/bases+datacore.png differ