# Tags SOP > [!overview] > updated:: [[2023-06-08]] | Tag | Type | Description | HEX | | ------------ | ------- | --------------------------------------------------------------- | -------- | | #demo | Passive | Used to denote notes safe for public demos. | — | | #followup | Active | …I should follow up on this note. There’s an action item here. | \#e94830 | | #hide | Passive | Used to hide notes from [[Graph View SOP]]. | — | | #index | Passive | Nested. Used to designate connector notes. | — | | #location | Passive | Used to group geographic information. | — | | #priority | Active | Used to denote hotter actions or ideas. | — | | #question | Active | …I have a question. It may become a seed or research topic. | \#228195 | | #reference | Passive | Reference material. Often linked to [[Zotero]]. | — | | #research | Active | Follow up for future research. Used for [[Supercharged Links]]. | \#eaad12 | | #seed | Active | There’s a seed of an idea here. | \#78d5e1 | | #time-period | Passive | Nested. Used to group time periods. | | --- ## What is a tag in my workflow? I have two types of tags: active and passive. ### Active Tags **Active tags** are action indicators. They are intended to be disruptors by strategic use of colour through the [[Supercharged Links]] plugin and some custom CSS. I *want* to surface that content, whether it’s a #question I had while reading, or something I want to #followup on. I use #research to define interesting topics I want to delve further into, and #seed for ideas that have sparked and would be interesting to write on or explore through design. ### Passive Tags **Passive tags** are information indicators. For instance, #index shows notes that act as big connectors in my vault such as course syllabi or [[Dataview]]-based notes for D&D that give me information at a glance. A tag like #hide gets used on my [[Graph View]], but it is a silent tool in my system. #### Geographic I've started to use geographic-based tags in my workflow, thanks to [[Obsidian Leaflet]]. This creates a nested tag for when a relevant continent, country, region (e.g. province or state), or city comes up. This is used in anything from mapping out the grocery stores in my new neighbourhood, to making notes about [[San Francisco, cisterns|cisterns]] in [[San Francisco]] that were influenced by the [[San Francisco, 1906 earthquake|earthquake in 1906]]. Countries follow [ISO 3166-1 Alpha-3 codes](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3) (e.g. CA, US), and the principal subdivision follows the second half of the ISO 3166-2 code (e.g. ON, CA) Example tag: - \#location/NA/CAN/ON/Toronto - \#location/NA/USA/CA/San-Francisco - \#location/EU/GBR/London #### Time Period Similar to [[Tags SOP#Geographic|my location-based tags]], I use nested tags for grouping information by time period. Typically I stick with decades or years, but if it's relevant, I include named eras or wars if I read or interact with data with enough frequency to warrant it. Examples: - Decades: \#time-period/1900s-1990s/1910s - Named eras: \#time-period/named/EU/1789-1914_Long-19th-century/1901-1914_Edwardian-era - Wars: \#time-period/wars/1914-1918_WWI --- ## What isn’t a tag in my workflow? - **\#calendar** and nested tags like **\#calendar/daily**, **\#calendar/weekly**, **\#calendar/monthly**, and **\#calendar/annual** - It wasn’t serving a need, since I can use a [[00 Meta/03 Resources/03.04 Classifications/Metadata/type]] `key: value` pairing and strategic use of folders. It added clutter to my tag pane. - **\#status** and nested tags like **\#status/process** - I used this for a while but prefer using them as a [[00 Meta/03 Resources/03.04 Classifications/Metadata/type]] `key: value` pairing. It allows me more flexibility with the [[MetaEdit]] and [[00 Meta/05 Obsidian/05.03 Community Plugins/Kanban|Kanban]] plugins and continues to work nicely with [[Dataview]] - \#resonance - It didn't stick. --- ## The Great ReTaggening I am a recovering tag person from my Evernote years where I had over 1000 tags when I left. As a result, I am re-evaluating my approach to tags as my workflow evolves in Obsidian. ### To Go Away (Low priority) - All \#status/process » I prefer this as a `key: value` pairing for Kanban purposes