Best way to ensure imported notes stay in a given deck?

Problem: If I import a .txt file with a #deck header, then imported cards whose IDs (=first columns) match cards in other decks, update the cards in those decks (and do not create new cards in the specified deck).

Potential solutions:

  • Manually: Match scope = Notetype and deck
    • Downside: Must be activated manually each time.
    • Upside: simple
  • File header: use #deck column and add an additional column.
    • Would this work?
    • Upside: Importers don’t have to remember to change the match scope.
    • Downside: makes files bigger
  • File header #columns:DeckPlusFront;Front;Back
    • I qualify the ID (= Front) by putting the deck’s name in front of it.
    • Would that work automatically without the user having to intervene manually? In other words: Would DeckPlusFront be used for duplicate checking and Front as the front of each card – automatically?

Would it make sense for Anki to support a file header #match scope?

Just to establish baseline terminology – you are importing notes (not cards), Anki creates cards from them based on the instructions in the note type, and those cards (not notes) are placed in decks.

You said the problem, but you didn’t say what outcome you want instead.

If your goal is to create duplicate notes with their cards in the specified deck, can’t you already control that with the import options?
image

Or is your goal to update an existing note and move its cards to different deck?

1 Like

Well thankyou for this solutions i’m going to try these

1 Like
  • I’ve done more experiments and, for now, manually setting “Match scope” to “Notetype and deck” does what I want (#1 of the potential solutions).

  • Just as I can use a text file header to pre-set/pre-populate the import option “Deck”, I’d love to also be able to pre-set the import option “Match scope” – so that cards from an imported file don’t accidentally change cards in other decks.