Specifying note title and tags in templates

[JackGruber]

@nishantwrp

Using template_title and template_tags

I think the naming template_ for special variables of the plugin is a good choice.

@nishantwrp

Should we use the actual template tags and title instead of special variables?

Not for tags, because they can no longer be made dynamic.
For the title possible, but could look a bit confused in the overview, but to make it consistent I would also put it in the YAML area and at most if none is defined use the title of the template.

[tessus]

Will something like this work now?

note_title: Sprint {{bowm}}

[nishantwrp]

By now, do you mean when this feature is implemented? If yes, then yes.

[codyburleson]

Maybe I don't fully understand, but this seems a little overengineered to me. Why not just allow variables in titles and be done with it? By simply allowing template variables (one to many) in titles, you effectively accomplish the same thing without the need for special reserved variables.

[nishantwrp]

Actually, we have to do the same tags and maybe in the future for target notebooks (you can read this). If we want to do it for title only then using the template note title seems good.

[uxamanda]

@JackGruber

For the title possible, but could look a bit confused in the overview, but to make it consistent I would also put it in the YAML area and at most if none is defined use the title of the template.

I like this as a solve - if the user doesn't have a template_title or template_tags in their yaml, it uses the one from the template itself, otherwise the yaml overrides. Although I am guessing the "template" tag itself would not be inherited

[JackGruber]

@codyburleson

Why not just allow variables in titles and be done with it?

I don't like it when all the variables appear in the template selection.
In addition, I would find it great if the templates are called differently than the created note then, especially for the dropdown selection are speaking names more meaningful.

• Project meeting
• Project ToDo
• ...

and not

• Standup {{bowm}}
• Meeting {{project}} on {{date}}
• {{project}} - {{taskdescription}}

Maybe you should consider to put the note options and the variables in their own section, so that there are no name overlaps?

variables:
  name: text
  project: enum(Project 1, Project 2)
  notebook: text
  tags: text
  test:
    label: Text for the input mask
    type: text
    ...
note:
  tags: daily, {{tags}}
  title: Meeting project {{project}} on {{date}}
  notebook: {{project}}
  ...

[nishantwrp]

Template Plugin

Release v2.0.0 Features add support for adding labels for custom variables (b138110), closes #30 allow specifying title and tags in templates (c36dea0) use dropdown instead of enum for better user experience (c009fc9), closes #7 Bug Fixes auto wrap special variable values in double quotes (720eea2) ignore eslint errors for \S (dd98f44) parser: update the regex used to find special variables (cb3d677) For reporting bugs/feature-requests or to know more about the plugin visit the Git…

[joeldebruijn]

I was looking for a way to batch/bulk create notes and read all the plugin suggestions.

Then I thought maybe if the template plugin could create a note for all permutations of a variable? For example "Day of the Week Number" creates 7 notes. Or for a range, for example "Week Number 23 to 28" creates 6 notes.

("Proceding with caution" caveats etc because it could spawn 100 notes if done wrong)

Could come in handy for this also:

Managing a daily/master todo list

I could use some ideas on how to better manage the following! I maintain one "master" todo list that I consult every morning to determine what todos I want to work on that day. Many of the todos are just plain text because there's not much detail I need written out (no dependencies that need to be done beforehand, I have all the necessary details in my head). The more involved todos will be links to notes that contain the necessary details/reference material. Because this is a very long list o…

[nishantwrp]

That’s a nice use case. But I am unable to think of a good way to implement this. I think it will be too confusing for a large number of users and yes as you mentioned it will be frustrating if it doesn’t behave the way they expected it to because it could create 100s of wrong notes.

But maybe, we can create a new plugin that works with template plugin to do batch creation. I am not sure if the commands registered by template plugin can be used by other plugins.

[joeldebruijn]

Yeah was also thinking a combo is more feasible.

A note generator for batch creation.
But being able to choose on which template it is based.

Passing on the same variables tho for titles etc still remains like you said.

[joeldebruijn]

I'm getting the same error as @dpoulton but after readfing this entire thread I'm still confused.

Created a template with the following at the beginning:

---

MaandNaam: dropdown(Januari, Februari, Maart, April, Mei, Juni, Juli, augustus, September, Oktober, November, December)
MaandNr: dropdown (01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12)
template_title: 2021{{MaandNr}} - {{MaandNaam}} - Routine

---

For non-dutch, it is trying to create a title with monthname (january to december) and month number (01 to 12).
The name is used exactly as expected but the 'text' 01 etc says invalid type and is ignored.

What am I missing?

[CalebJohn]

If that is the exact copy and pasted text, it's because you have a space between dropdown and (

MaandNr: dropdown (01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12)

should be

MaandNr: dropdown(01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12)

[joeldebruijn]

Ahhhh, thanks!!! Stupid mistake.