Notes with Adjectives

In language, we use adjectives as descriptors that provide additional context for nouns.

Often we prefix a noun with an adjective to be more specific as a qualifier. For example, a note might be more specifically described as a concept note, person note, event note, or place note; that provides more context about the object represented than a general, base, or default note.

Adjectives provide a descriptive label for the qualities or characteristics associated with a note in its metadata properties or template structure.

Note types

What's the difference between a default, map, view, app, effort, or output note? Usually these different types of notes have unique metadata and template structure.

It's helpful to think about a model of our knowledge graph as a network of various types of notes and their relationship connections.

For example, I might start with a spark for an idea that develops and triggers an effort on Obsidian Integration with actions that connect different apps in my PKM environment, producing an output as a website post to share with others.

I use maps and views to help me manage these various types of notes in this workflow as a LYT pipeline with my thinking and processing between encountering a spark and expressing an output.

Views (metadata tables)

Some views like collections might be considered attribute notes because they present table views of notes based on similar properties (describing their attributes), such as views for Movies, Books, or Contacts that contain one or more Dataview queries.

Other views might be considered state notes since they capture a condition like note status or workflow state, such as New Drafts, or Recent Notes, based on Database queries that reflect specific metadata values for properties, tags, and/or fields.

Verbs (process/actions)

Some notes are more verb-centric since they might document processes or actions. For example, process notes outline sequences of steps or workflows, or action notes describe methods, procedures, or techniques.

These can be quite helpful to capture your learning while exploring new topics, record observations about results from tiny tests like shortcut automation, and documentation like a user guide for yourself to help you remember configuration settings or how to do something in the future.