You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Anki workflow is currently "one deck, hierarchical tags".
I have a lot of notes that would be useful to share with people, but I don't want to export notes such as "names of my colleagues" or "where did I meet this person". I tag those with a "_secret" tag.
It would be nice if I could make CrowdAnki only export notes matching a certain tag (e.g., "_public"), and ideally to also split cards into repos based on the tag hierarchy instead of the deck hierarchy.
For now, when I want to share a deck with people, I just create a new deck, move all the relevant cards there, then share it in AnkiWeb and then move them all back. That work good enough.
I don't really think my use-case is important enough that someone should implement this (wave hi Vlad :), but I'd just like to put this issue here to have something to refer to in case more people have a similar workflow or in case I end up contributing a patch :)
The text was updated successfully, but these errors were encountered:
My Anki workflow is currently "one deck, hierarchical tags".
I have a lot of notes that would be useful to share with people, but I don't want to export notes such as "names of my colleagues" or "where did I meet this person". I tag those with a "_secret" tag.
It would be nice if I could make CrowdAnki only export notes matching a certain tag (e.g., "_public"), and ideally to also split cards into repos based on the tag hierarchy instead of the deck hierarchy.
For now, when I want to share a deck with people, I just create a new deck, move all the relevant cards there, then share it in AnkiWeb and then move them all back. That work good enough.
I don't really think my use-case is important enough that someone should implement this (wave hi Vlad :), but I'd just like to put this issue here to have something to refer to in case more people have a similar workflow or in case I end up contributing a patch :)
The text was updated successfully, but these errors were encountered: