hope it works after you added those files

Hmm - I have put a note at each node - it is empty except for the front matter - but still full of + icons and only the little book icon at the DAY level for each month.

Reload index?

Yep - reloaded index each time.

Hmmmm

this is strange

and the schema file is OK to be daily.schema.yml?

yes, it works on my newly initialized dendron vault

maybe just copy and paste my schema that works for me and see if it works

version: 1 schemas: - id: daily title: daily desc: "Daily Note" parent: root children: [journal] - id: journal parent: daily title: journal desc: "" children: [year] - id: year parent: journal title: year pattern: "[0-2][0-9][0-9][0-9]" children: [month] - id: month parent: year title: month pattern: "[0-9][0-9]" children: [day] - id: day parent: month title: day pattern: "[0-9][0-9]" template: id: template.daily type: note

I deleted the

namespace: true

in the day section, this schema works perfectly after the deletion of that line

Nope - only the lowest level node in the tree has the icon - all others have a + mark. I have verified that I have .md files for daily.journal.md, daily.journal.2020.md, daily.journal.2020.12.md and daily.journal.2020.11.md. and so on. Still plus signs. Sigh. I guess it is fine - I mean nothing is broken, I can create notes, no errors pop up - but I was hoping to dig in and get all of my schema's correct.

maybe you need to restart code but you probably already did that

Yeah. I am doing some experiments with a new vault. Thanks for verifying that I wasn't doing anything overly wrong - removal of the namespace: true and have a note at each "node" were great hints - and if everything works "perfectly" I should expect a little book icon at every single node.

OK - so things are working in a brand new vault. I had moved vaults around inside of internet explorer. I already had the root node files - empty except for front matter content - but they were created in another vault. I found in my new vault as I slowly brought files over that if I brought an existing node note - like - daily.journal.2020.11.md over from the existing vault a little + sign appears instead of a book icon. I then DELETED this note, then clicked the +, a new note was created, and then the book icons appeared. So I think I have the issue sorted out - thank you.

Ok - question. I have a schema with multiple children, say [note, team, fso]. For each of these I want them to next have year.month.day. For YEAR what would the "parent" be? Can I say parent: [note, team, fso]?

you don't need to specify the parent

Do you see anything obviously wrong with this?

version: 1
schemas:
- id: work
  title: work
  desc: "Daily Note"
  parent: root
  children: [note, saas, zone, training]

- id: note
  parent: work
  title: My Note
  children: [year]

- id: saas
  parent: work
  title: SaaS Stuff
  children: [year]

- id: zone
  title: Zone
  children: [year]

- id: training
  title: Training
  children: [year]

# This is a long date
- id: year
  title: year
  pattern: "[0-2][0-9][0-9][0-9]"
  children: [month]

- id: month
  parent: year
  title: month
  pattern: "[0-9][0-9]"
  children: [day]

- id: day
  parent: month
  title: day
  pattern: "[0-9][0-9]"
  children: [text]

# The end of the note
- id: text
  parent: day
  title: text

that should work in my eyes

This results - there are notes freshly created at each node, but notice no + or book icon for anything under note or saas (training and zone are empty at the moment)

sorry then I have no idea how to do it

Thanks for trying. Maybe @User can take a look at some point.

Almost solved. Apparently whatever the LAST child is that is what gets the little book icon. You can ONLY have ONE. In this case only saas notes have the book icon, note entries do not. But if I delete saas from the schema then the book icons appear for note entries. I would say - this could be something to look into @User One possible solution - create a different date.schema.yml for each note. IE: date_note.schema.yml, and date_saas.schema.yml and so on - one for each node, then import them in the imports: section, and then refer to the specific yml file for each node. Its "janky" but I have my little book icons lol. work.schema.yml:

version: 1
imports:
  - date
schemas:
- id: work
  title: work
  desc: "Daily Note"
  parent: root
  children: [note, saas]

- id: note
  parent: work
  title: My Note
  children: 
    - date.date

- id: saas
  parent: work
  title: SaaS Notes
  children: 
    - date.date

then date.schema.yml:

# This is a long date
version: 1
schemas:
- id: date
  title: year
  pattern: "[0-2][0-9][0-9][0-9]"
  parent: root
  children: 
    - month

- id: month
  parent: date
  title: month
  pattern: "[0-9][0-9]"
  children: 
    - day

- id: day
  parent: month
  title: day
  pattern: "[0-9][0-9]"
  children: 
    - text

# The end of the note
- id: text
  parent: day
  title: text

the reason your not seeing book icons next to the years is because we don't currently show them when you specify the

pattern

field 😅 this is a bug. could you file a bug report here so we can fix that going forward? https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title=

I will submit this. But - I have found a workaround. I have several different DATE_n.schema.yml files, where n is unique. In the main schema I import all of them, and then for each main NODE - like training, saas, note, etc I use a unique DATE_n.file. See the image - I can get it to work. So I am not sure the issue is the icon doesn't appear when there is a pattern - it does - the issue is you cannot refer to the SAME .yml file multiple times - they need to be unique files. In the image both fso and note are beneath work. Notice I have the icons everywhere except for the lowest node which is just free text.

Here is an example - if you use unique .yml files for the dates the tree is clean and full of book icons 🙂

haha, yeah, that's another way to get it done 🙂

😊 do you think refactoring down to ONE date.schema.yml file that can be reused inside a single schema file as well as other schema files is in the cards for the future?

yep, that’s definitely preferred. in the future, we’ll also introduce a schema registry where you can share and use schemas published by others

> schema registry that sounds interesting