I’d love to add in that there are many use cases in which it would be useful for #hashtags to be recognized in other properties. For instance:
-
What if I want to categories my tags into groupings, e.g. “
subjects: #philosophy, #science
”, and thenrelevant-authors: #Kant, #Hume
-
I’d love to have some properties be filled out with hashtag values, like “
status: #status/incomplete
”. This allows me to use the same tags that I might use inside the note to tag a paragraph as incomplete. -
There are some tags that are in orthogonal spaces to the typical tags. Again for these, it would be good to group them into their own properties. For instance, I store “mental models” as tags. For each note I have a list of mental models used in the YAML code:
Mental-Models-Used: #MentalModels/Munger/Scaling #MentalModels/Physics/GravityWells
Previously I used YAML Anchoring (a pretty advanced feature) to feed everything into the Tags field, but anchoring is not officially supported in 1.4.
To work around, I must:
- Always add a space when entering tags via the Property UI as it will not allow a # to begin a text value.
- If searching for a tag, I use the following method:
#tagname OR tag:#tagname
- If wanting to autocomplete the tag name for other properties, I must enter it via modifying the file source.
- And lastly, I must give up on the tags used in properties in being displayed on connectivity graphs or tag lists.
I add this to the discussion because the original request for the feature was in a very specific use case, but I’d like to highlight that the request is far more reaching. Thanks!