Here is my setup:
I have different Drafts actions to create anki cards.
This allows me to:
- add content to different decks and notetypes
- add specific tags for organising the Anki notes
- add generic content to Anki notes
Each action has only one step: Callback URL. In my case, the template looks like this:
Everything in bold is user specific for your Anki setup:
- note type (here: Einfach)
- deck name (here: Medizin)
- first fieldname (here: Vorderseite, for “front side”)
- second fieldname (here R%C3%BCckseite, the encoded form of Rückseite, meaning “back side”
- one or more tags (staging)
Documentation for AnkiMobile’s URL Scheme: URL Schemes - AnkiMobile Manual (it does not work on Anki for Windows/Mac/Linux).
I usually prepare drafts with a first line that is passed into Anki as [[title]] and the remaining content passed into Anki as [[body]].
Every Anki note created from Drafts contains the tag staging, so I can rework these notes in Anki if needed and remove the tag afterwards.
You can add several tags at once:
adds the tags
- as a hierarchical tag Wortart::Phrase
I only need to remove the tag staging in Anki, every other tagging is done from Drafts.
You can also use Drafts actions to add generic content to your Anki cards. For example, I sometimes stumble across drug trade names I don’t know. So I make a draft containing
I get an Anki card prompting me
Which drug is Hygroton? (German: Welcher%20Wirkstoff%20ist%20[[title]]%3f)
with the answer chlortalidone and a pharmacology tag already set.
You can certainly do more with Drafts and Anki. For example, instead of multiple actions with different tags, only one action and a selection list of which tags should be used.