Has this been addressed by any devs yet?

2 Likes

Happy to support this feature, it would be a great improvement.

This feature seems to have a lot of support. Are there any plans to actually implement it?

3 Likes

You do it with aliases. @thoresson For Zettelkasten usecase, with the core plugin Zettelkasten prefixer, you can add this to the template:

---

aliases: ["{{date:YYYYMMDD}}{{time:HHmm}}"]

---

edit: One problem with this is if you try to make multiple Zettelkasten notes at the same time. The plugin “Zettelkasten prefixer” is smart enough to change the name. For example creating a note at 2021-08-23 04:40, gives you a file 202108230440, creating another note immediately creates 202108230441. But both are still created at 2021-08-23 04:40, so the template still adds the same alias aliases: ["202108230440"] in the YAML front matter.

2 Likes

People who zettel, can you leave the filename as the title and put the zettelkasten code as a first line or perhaps an alias or metadata in the text?

I like the neatness of titles being filenames. Part of the point of Obsidian is dealing with bare text files. This FR seems like it complicates that structure.

This is what I was suggesting in this feature request. Joplin simply grabs the first few words or header of your note and auto generates the title.

Isn’t that my proposed solution? “Zettelkasten prefixer” plugin creates a file with name YYYYMMDDHHmm, which you can edit. You can designate a template for the note creation. Adding

---

aliases: ["{{date:YYYYMMDD}}{{time:HHmm}}"]

---

will create the correct alias. So both 202108230440 Note Title and 202108230440 links to the same document.

1 Like

Oh yes, I see that now. Sounds good to me.

But as I have warned, if you try to create multiple Zettelkasten notes at the same time/minute, they will share different Zettelkasten ID but the same alias.

For example, you create the 2 notes at 2021-08-23 04:40, the plugin will title them 202108230440 and 202108230441 (auto +1 the ID for uniqueness). But my proposed solution will create the alias to 202108230440 for both notes. Which is wrong.

Basically we can only wait until one of the Zettelkasten plugins implement this correctly. Until then you can use my proposed solution, either by not creating multiple notes at the same time/minute, or by extra manual editing. Or perhaps understanding the Templater plugin.

edit: As mentioned on another thread, just add the seconds. So YYYYMMDDHHmmss and "{{date:YYYYMMDD}}{{time:HHmmss}}" as alias.

I would love to have this feature.

2 Likes

The Switcher++ plugin might be able help here. It allows you search by headings contained in the note instead of only filename from the quick switcher, which gets us a step closer.

1 Like

+1 This would be great! :slight_smile:

An enthusiastic +1 for this. After I started using Obsidian, I was surprised to discover this functionality didn’t already exist, especially given the number of users who are creating Zettelkasten in Obsidian.

4 Likes

Please please please add this feature! +1

+1 Absolutely a must-have! I use Zettelkasten prefixes and that makes e.g. the graph view very “full” because of all the numeric prefixes.

1 Like

+1 great idea!

+1. Really valuable idea.

Add more 1 vote.

Very useful feature.

+1 This would be a lifesaver and allow for much more descriptive filenames while keeping in-line links simple and readable.

+1. Really valuable idea.

+1

This is a critical feature in order for our team to fully take advantage of the linking and graph capabilities. We trying to adopt Obsidian as an editor for our documentation website which is hosted on a git repo and runs a build process to output a static site.

The challenge is that default HTML looks for an index file in a directory. This forces us to name the primary file within the directory index. As you can imagine, the graph view (while beautiful) is mostly unusable as over 80% of nodes return index.

Additionally, the unlinked mentions become wildly inaccurate as it returns so many instances of unrelated index files.

Given that this is the #2 most requested feature and viewed thread, has this been added to the product roadmap?

1 Like