-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
12 changed files
with
87 additions
and
3 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
aliases: [Tagging, Tags, Tag] | ||
tags: [note/info, productivity, original] | ||
--- | ||
# Note Tags | ||
Tagging a notes can serve various functions. One should consider how they want to use tags before proceeding with their workflow. | ||
|
||
All tags will allow speedy searches based on how it's functioned to set up. | ||
|
||
[[Tags As Categories]] | ||
[[Tags As Characteristics]] | ||
[[Tags As Categories and Characteristics]] | ||
|
||
Also consider [[When to Tag]]. | ||
|
||
## References | ||
[The Difference Between Good and Bad Tags](https://zettelkasten.de/posts/object-tags-vs-topic-tags/) | ||
[Some ideas about tags, categories, and metadata for online commonplace books and search](https://boffosocko.com/2018/10/03/some-ideas-about-tags-categories-and-metadata-for-online-commonplace-books-and-search/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
--- | ||
aliases: | ||
tags: [ note/info ] | ||
--- | ||
# Tags As Categories and Characteristics | ||
Or just use both methods described above. Just know that it comes with the overhead of both and there will probably be a lot of redundancy (e.g. `#health`, `#physical_heath`, `#mental_health`, `#well-being`). | ||
|
||
**Source** | ||
[[Note Tags]] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
--- | ||
aliases: | ||
tags: [ note/info ] | ||
--- | ||
# Tags As Categories | ||
Tags might be used as a means of grouping notes together on a particular topic. For example, all notes relating to Exercise will get the tag `#exercise`. Usually notes only get one tag, but | ||
|
||
Tagging this way is useful when folders are structured in a way that doesn't immediately categorize topics, such as under the constraint of flat file systems or anything similar (e.g. [[Zettelkasten]]). | ||
|
||
The downside is that it may be more difficult to parse though notes, as these categories may potentially grow too deep. You may need to set filter your first results with something else, and if you only tag in one Category then you must manually look through the notes or search under some other constraint (e.g. path, file name, contents). | ||
|
||
**Source** | ||
[[Note Tags]] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
--- | ||
aliases: | ||
tags: [ note/info ] | ||
--- | ||
# Tags As Characteristics | ||
Tags might be used to identify traits of something. For example, some notes relating to Exercise may have some subset of the following tags: `#physical_health`, `#mental_health`, `#apperance`, `#testosterone`, `#habit`, `#ceremony`, etc. | ||
|
||
Tagging this way is useful when folders are already structured under topics, as tagging by Categories would be redundant. This also allows for more nuanced searches as you can search specific details. | ||
|
||
The downside is that notes can have an arbitrary amount of characteristics that tags can define, causing the tag pool to potentially grow too wide. Additionally, there's nothing preventing you from combining tags into one characteristic (e.g. `#physical_health + #mental_health = #health`). This may create excess overhead and redundancy and will require additional maintenance, more so than tagging by Categories. | ||
|
||
> If you've ever used an image booru, this is how their tagging works. | ||
**Source** | ||
[[Note Tags]] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
aliases: | ||
tags: [ note/info ] | ||
--- | ||
# When to Tag | ||
There is an arbitrary threshold on when a note should have a certain tag. The measurement that's used against this threshold is **Tag Power**. A tag is considered powerful enough to be added when the note related, either trivially and directly, to this tag. | ||
|
||
Say for example we have relatedness `A~B~C~D`. | ||
`D` usually should only be tagged with `C`. | ||
`B` should can have tags `A` and `C`. | ||
|
||
> This is similar to how one may link notes. | ||
### Expansion on Related Tags | ||
`#scrum` is a direct descendant of `#agile` (`#agile` $\leftarrow$ `#scrum`). A note based on scrum is trivially related to `#scrum`, should also have `#agile`. | ||
|
||
However, a note based on agile will have `#agile`, but should not have `#scrum`. | ||
|
||
The only exception is when a note is dedicated to talking of both topics on equal footing. `#gamedev` and `#photograpgy` are not immediately trivially related, but the exception allows it such that for both tags under the context of `Photography and Texture Mapping to Character Models`. | ||
|
||
> **Tags should not be used to show relatedness between notes.** | ||
**Source** | ||
[[Note Tags]] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters