rasmuse
11/10/2020, 5:30 PMrasmuse
11/10/2020, 5:33 PMkevins8
11/10/2020, 5:33 PMkevins8
11/10/2020, 5:33 PMrasmuse
11/10/2020, 5:34 PMkevins8
11/10/2020, 5:34 PMrasmuse
11/10/2020, 5:34 PMkevins8
11/10/2020, 5:35 PMkevins8
11/10/2020, 5:35 PMrasmuse
11/10/2020, 5:35 PMrasmuse
11/10/2020, 5:36 PMkevins8
11/10/2020, 5:37 PMrasmuse
11/10/2020, 5:37 PMuser
11/10/2020, 5:44 PMnsb7
11/10/2020, 5:55 PMnamespace: true set. this means match everything that is one level underneath.
>
> so id: projects would match projects.foo
>
> so your DIY schema as it is now would match projects.{child}.tech.{child}.iot.{child}.diy.{child}
>
> ---
>
> generally when it comes to categorical data, I would recommend keeping a short hierarchy and using tags to filter. so projects.foo and add a [[tag.tech]] in the frontmatter or the body of the content instead.
@User Thanks for the response. I am just moving from OneNote so not yet caught up on this way of doing it with short hierarchy, I will give it a try and see if it works for me else I will play again with the schemarasmuse
11/10/2020, 6:45 PMuser
11/10/2020, 7:02 PMrasmuse
11/10/2020, 7:04 PMuser
11/10/2020, 7:05 PMrasmuse
11/10/2020, 7:07 PMReductioMeta
11/11/2020, 12:37 PMkevins8
11/11/2020, 3:05 PMnsb7
11/11/2020, 4:38 PMnamespace: true set. this means match everything that is one level underneath.
>
> so id: projects would match projects.foo
>
> so your DIY schema as it is now would match projects.{child}.tech.{child}.iot.{child}.diy.{child}
>
> ---
>
> generally when it comes to categorical data, I would recommend keeping a short hierarchy and using tags to filter. so projects.foo and add a [[tag.tech]] in the frontmatter or the body of the content instead.
> @User @User Thanks again , I simplified the hierarchy and added tags as you suggested and also got the template workingU de Recife
11/12/2020, 8:29 AMkevins8
11/12/2020, 2:48 PMU de Recife
11/12/2020, 4:16 PMjasonlarkin
11/13/2020, 1:04 AMkevins8
11/13/2020, 1:27 AMjasonlarkin
11/13/2020, 1:27 AMkevins8
11/13/2020, 1:30 AM