This could work like Tags > Convert Hashtags to Tags does now, except it would parse the front matter syntax which is
tag: ["tagname"] or tag: [tagname]
either seem to work in Obsidian
Use case: I use Obsidian alongside DEVONthink and this would allow me to tag using YAML Front Matter in Obsidian and easily turn them into usable tags in DEVONthink which is where I do my processing and searching for obvious reasons
I’m working around this by tagging outside of the front matter section, but I’d prefer to keep the tags hidden with the rest of the document meta inside the front matter.
PS: Obsidian is doing their own thing with Markdown. We try to follow standards and conventions when possible, even if the standard isn’t defined by anything more than the understanding and use of the majority.
I don’t know if that’s possible directly with a rule.
It certainly is with a script which could be run from a smart rule: grab the love (edit: read “line”) beginning with "tags: ", isolate the tags themselves and add them to the tags property of the record.
Just revisiting this topic. I’m new to Devonthink. Installed it two days ago, and indexed my Obsidian vault today. And realized that DT picks up #tags in text but doesn’t pick up tags in YAML frontmatter. I think that that would be a very good thing to have. But I don’t know how to script it. All and any help would be greatly and deeply appreciated.
Aren’t there multiple ways to format tags in YAML frontmatter? If all 3 formats below work:
tags: hello greeting
tags: [hello] [greeting]
tags: hello, greeting
how is Obsidian doing their own thing with respect to YAML frontmatter tags?
Secondly, as you can see from the second screenshot, YAML headers are not hidden in the Preview rendering. This doesn’t bother me particularly as I like seeing the headers, but it is a difference in treatment. It’s why I asked whether the behaviour is expected or not.
Yes, it works, but isn’t that because the only --- is treated as a simple divider? I.e. It’s not seen as a YAML block because of the absence of the first separator. (I could be wrong on this, I’m an expert in neither markdown nor yaml!)
I know multimarkdown accepts a subset of YAML metadata, but I don’t know how that translates to previews (and as I said, I actually don’t mind them being displayed).
My question was really why the properties are being ignored with the YAML headers and whether this is expected – it’s not referenced in the help as far as I can tell.