You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can simply define a hierarchical tag in the form of lvl1/lvl2/lvl3. lvl1/lvl2 will be a sub-level of lvl1, and similarly, lvl1/lvl2/lvl3 will be a sub-level of lvl1/lvl2. For example:
==However, lvl1/lvl2 and lvl2 will be considered as two different tags==. For instance, work/notes, personal/notes, and notes are not related to each other.
2. Tag Relationship Graph
The concept of a "Tag Relationship Graph" is similar to the current graph of bidirectional links in Markdown, but it is for tags (not documents).
The tag relationship graph believes that tags should not be in a tree structure (parent-child relationship). Each document's tags should remain simple. sucn as pet/dog/husky, it declares three tags pet, dog, and husky, and also declares the relationship between the tags (pet is the parent of dog, and dog is the parent of husky). We should separate the responsibility of "tag relationship declaration." We create an empty document that only contains metadata declarations, such as dog.md:
---type: tagtags:
- husky
- border-collie---
As for another example mentioned earlier, work/notes, personal/notes, and work/projects, you could declare them as three separate tags work-notes, personal-notes, and work-projects. At the same time, create an empty document with only metadata work.md:
---type: tagtags:
- work-notes
- work-projects---
Furthermore, you can choose whether to create note.md based on your needs:
Finally, it would be even better if we could automatically generate "tag relationship metadata documents" by simply dragging and dropping tags directly in the graph interface.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
"Hierarchical Tags" or "Tag Relationship Graph"
1. Hierarchical Tags
You can simply define a hierarchical tag in the form of
lvl1/lvl2/lvl3
.lvl1/lvl2
will be a sub-level oflvl1
, and similarly,lvl1/lvl2/lvl3
will be a sub-level oflvl1/lvl2
. For example:==However,
lvl1/lvl2
andlvl2
will be considered as two different tags==. For instance,work/notes
,personal/notes
, andnotes
are not related to each other.2. Tag Relationship Graph
The concept of a "Tag Relationship Graph" is similar to the current graph of bidirectional links in Markdown, but it is for tags (not documents).
The tag relationship graph believes that tags should not be in a tree structure (parent-child relationship). Each document's tags should remain simple. sucn as
pet/dog/husky
, it declares three tagspet
,dog
, andhusky
, and also declares the relationship between the tags (pet
is the parent ofdog
, anddog
is the parent ofhusky
). We should separate the responsibility of "tag relationship declaration." We create an empty document that only contains metadata declarations, such asdog.md
:As for another example mentioned earlier,
work/notes
,personal/notes
, andwork/projects
, you could declare them as three separate tagswork-notes
,personal-notes
, andwork-projects
. At the same time, create an empty document with only metadatawork.md
:Furthermore, you can choose whether to create
note.md
based on your needs:Finally, it would be even better if we could automatically generate "tag relationship metadata documents" by simply dragging and dropping tags directly in the
graph
interface.Beta Was this translation helpful? Give feedback.
All reactions