I'm afraid there is a bug. Journal files use a full date title and diary entries don't. At least that what it is for me. I want to check to reproduce with a simple workspace. If I can I'll report an issue. If you don't use separate journal notes you can use these for daily notes with the desired behaviour

@User @User currently, the journal dates will only show up expanded in the title if you use the default format

y.MM.dd

. anything else will revert to the default behavior (using the last path component)

I removed the date format setting but still see this. As I said I'll to reproduce it with a new workspace and default settings. If I can I'll file a bug if not I'll apologise for the noise

👍

Should it show up that way in the front matter?

Issue created: https://github.com/dendronhq/dendron/issues/461

no, in the frontmatter it will be the full date (eg. '2021-01-23')

(for the title field)

I use the default date format and can confirm this behaviour.

Yeah. I found your solution elegant to use the same function as one can use for linking notes. I'm not sure how aesthetically pleasing it is to if one doesn't use "pretty tags" (in order to not bother spending hours adding alias to every tag), but it sure helps a lot in having advanced features developed while not worrying about implementing that feature 100 times to different things that essentially are doing the same thing. I have to both agree and disagree with you last point in having too may ways.... as hierarchy is great if it is action oriented (like PARA) but it can lead to "did I put it under X tag or Y tag?" question when you use exclusive hierarchies to context and subject. for example, in the example I gave, it is obvious that the question cannot fall in one group or the other. in that situation if one doesn't use a sort of non-exclusive hierarchy, one will face the problem of asking themselves which category did I put this note under? I'm conviced that using your solution one will not have to give up that option. That leads me to another question, which I will ask next:

How would you deal with file name limits?

If I run into that a problem I would probably be asking myself if the filename works as a title (atleast the last part in dendrons case) or if it is more of a description and in the later case I would probably try to figure out what the title could be instead.

in the first case, what would you do?

Then I would check if I can shorten the hirachies, with the help of the schemas.

we'll be adding pretty tags option in the future which will map

#{tag}

to [[#{tag}|tags.{tag}]] yeah, in the situation that you mention, i agree that it can fall into multiple categories. the way dendron currently resolves this is using tags and in the future, giving you the option of aliases. in your case, the example with

how-consciousness-in-panpsychism-is-related-to-utiliterianistic-theory-of-normative-ethics

, this is how I would handle it: create

philosophy.papers

hierarchy and add it there as

philosophy.papers.consciousness-2-normative-ethics

inside

philosophy.philosophy-of-mind.consciousnes

and

philosophy.ethics

, I would create a wiki link to

philosophy.papers.consciousness-2-normative-ethics

this way, you have the article associated by backlins as well as a quick way of referencing the article without descending too many hierarchies. for papers, i also find its useful to add it as a [journal note](https://dendron.so/notes/5c213aa6-e4ba-49e8-85c5-1bdcb33ce202.html#journal-note) since dates are good hooks to finding past content

Yeah. Here is where I have a problem with your solution: You are sacrificing human readability for tool accommodation. When I'm thinking of a question or a specific problem I'm not searching for its relationship, I'm thinking of the question. If I have to think of the relationship or which notes I have used the mental resources which I'm trying to save by using a pkm system. And though it is not much, it is a friction. And in time, these frictions accumulate. And it results in a workflow which is hard to implement. As much as possible it should be the tools that accommodate the content not the other way around (though it is unavoidable that it would also happen the other way, and sometimes that should be by design). Now if that was just about the slug, I would not insist on it. But the way it is linked in other notes, in search, during browsation (wow) of the files, feels like more than that. Do you see my point?

heh, i think you just invented a new term 🙂 i do see your point about sacrificing human readability. in an ideal world, you would be able to query specifically for the knowledge you want. the issue is that this is the realm of google assistant/alexa/etc - ask it a qeustion, get a result. this unfortunately doesn't yet work for personal knowledge bases the hierarchy adds friction but the idea is that the friction (eg. hierarchy) is not a UX thing but the reason why dendron works with thousands of notes -> because we add this seemingly artificial hierarchal construct. the analogy i would use is excel -> while putting your numbers inside the structure of a spreadsheet might not be the most straightforward way of getting to a numerical solution, its use becomes indispensable once you deal with a significant amount of data the way to think about dendron is that its not going to help you answer questions directly, rather, it helps you organize your notes so you can reference the information you need to answer questions

I was trying to share my workspace and vaults via dropbox but this doesn't seem to handle things gracefully if I forget to close VSCode on a machine. It seems like the direction of multi vault is to set them up as submodules... except the #749641193322971238 and countless web articles hate on them.

Is this the direction multi vault support intends to implement, and does anyone have #742532267058004098, settings, or recommended plugins for managing multi vault commits?

instead of using submodules, i'm just keeping each vault as a separate git repo

dendron is smart enough to clone separate repos. its not well documented yet and still highly experimental 😅

i'm new to vscode as a long time *nix user (previously li-, currently mac U-), are those still contained in a single workspace?

I'm having difficulty making use of the

Dendron: Site Preview

- I'm on the latest version of Dendron. Dependencies get installed without errors, but then

creating preview: preview is ready

appears, a browser opens, and all the page displays is this:

Cannot GET /

Is there a CLI way of generating the site preview, and if so, is there a debug approach too?

(I also noticed, that if you use Dendron to import git repo vaults into

repos/

, that the config saved in

dendron.yml

only maintains the names of the repos, but not the git urls they were pulled down from. I ended up running two scripts: one that creates a list or repo origins, and one that will read the list of the repo origins and check it they exist in

repos/

before cloning them down if they aren't present) Side note: I found notes related to the multi-vault tracking in dendron config here: https://dendron.so/notes/45cfb9f2-46cf-4f67-a41e-834818fbd06e.html#configuration 🙂

https://dendron.so/notes/1399b5d2-28fb-4077-aa5f-c8edbe52bc5d.html#local-preview should cover this, when I had errors w/ my files in the past, they threw visibly in the console at the build step so no extra debug flags were needed.

Ah, this may be related to me doing a multi-vault scenario:

DendronError: mult notes found for root

Okay, so it seems that Dendron doesn't know what to do about there being a

root.md

existing in one vault, and another

root.md

existing in another vault I'm importing. It builds a site preview if I remove

root

from the list of

siteHierarchies

in

dendron.yml

- hmmmmm

Exactly what I needed for playing with at the CLI 🙂

I found out my problem is, indeed, having to do with a mutli-vault scenario. I'll follow-up in the #783027389919658025 channel with more questions about how to navigate this problem