JD x Tagging

J.D Concepts 14 Build your system
1

Continuing the discussion from Tags: Multiple Systems or Expanding Area? (in Obsidian):

My earlier discussions about headers and EtE led me to rethink my approach to tagging. @torbengb was right, there has to be a simpler way. A much simpler one.

My New Approach

I overhauled how I use tags in combination with JD. Tags often proliferate with slight variations, so a controlled vocabulary is essential. Glossaries are usually alphabetical, but grouping tags helps keep them manageable, this is where JD comes in.

I use category 91_Tag-Glossary to define groups, facets, or parent tags, e.g.:

91.10_Workflow

And sub-notes to define child tags within the group, e.g.:

91.10+_Closed
91.10+_Todo
91.10+_Work-in-Progress

Each tag group has a JDex number, but individual tags within the group do not. Since the vocabulary is controlled, each tag is unique and acts as an index, e.g.:

10_Todo

I include the ID in the tag name to make it searchable by parent tag. This requires me to think ahead about which groups, facets, or dimensions I want to use. (You can add synonyms to the tag note to support searching within the glossary.)

Application in Obsidian

Below I present my tag tree in Obsidian. A0–A9_<area>/AC_<category> are tags used to organize index files. Category91_Tag-Glossary includes all notes on groups and tags. Tagging is where I actually apply tags, such as Tagging/12_Hookmark, to content in Obsidian.

00-09_System/
10-19_Life/
20-29_Career/
30-39_Media/
90-99_Meta/
├── 90_Orga/
├── 91_Tag-Glossary/
Tagging/
├── 12_Bridge/
├── 12_Hookmark/
├── 12_MOC/
├── 15_Excalidraw/

General Tips on Tagging

  • Strike a balance between generality and specificity. Your tags should not apply to 50% of your content. It’s better to be too specific than too broad.
  • Use tags to highlight essential details, not just any detail. Ask yourself how interesting the content will be to your future self when searching by this tag. Rate your own imaginary user experience, only accept high ratings.
  • Review your tags and check for overuse or underuse.
  • Prefer existing tags whenever possible. Always check for similar tags already in use before introducing new ones.
  • Avoid tags that duplicate information already present in the title or other metadata.
  • Apply multiple tags to an item. A mix of subject matter tags (content), structural tags (format), and contextual tags from different facets, will help you search with high precision.
  • Use short tag names, no longer than three words. You can combine multiple tags later during search.
  • Don’t use redundant tags. A controlled vocabulary should prevent that.

Your Opinion

Do you find the approach useful in some regard? Can, should it be simplified further? Is it generalisable? Love to hear your thoughts on it.

Sources

1 Like