AnkiWeb
- Rating
- 2 (π 2 Β· π 0)
- Updated
- 2020-12-23
- Anki versions
- 2.1.24~
- Description language
- en
AnkiWeb addon 1665261045
Sorts new cards by configurable rules such as seen siblings, card position, note creation, modification date, or random order.
Open on AnkiWeb GitHub Ask about alternatives
abandoned
| Min Anki | Max Anki | Updated |
|---|---|---|
| 2.1.0 | 2.1.23 | 2020-02-16 |
| 2.1.24 | + | 2020-12-23 |
Loadingβ¦
Prioritizes unseen new cards from notes with already introduced siblings at the front of the new queue via a one-time command, ordered by lapse count and latest review.
Automatically unsuspends sibling cards when prerequisite cards reach set intervals or review counts, with leech protection and manual catch-up.
Suspends new sibling cards until their older siblings mature, then restores them on the next deck browser render, with configurable rules.
Buries related non-sibling cards using configurable similarity, prefix, contains, or cloze rules, though it does not work with the V3 scheduler.
Closes gaps in new card positions, preserves equal duplicates, resets nextPos, shows confirmation, and is undoable without modifying review cards.
Moves one or multiple browser cards up or down with configurable hotkeys, inverts order via right-click, and jumps to first/last visible new-card row after sorting by due or position.
The order in which I see new cards matters A LOT in my learning process. And I believe that anki does not offer enough freedom with this. This add-on wants to correct that. For example, it offer the following possibilities.
Anki allows you to randomize the order of cards. However, it ensures that when you see a new card of a note, all other new cards of the same note are shown soon after. Indeed, since their content are related, Anki believes that it's best if there is not too much time between the first review of two cards of the same note.
Except that actually, it does not work this way. Once you randomize a deck, the order of new card does not take into account which cards have a seen siblings, and which ones have note. So, if you want to randomize, but see siblings of seen card first, now you can.
The configuraton to enter is "seen first", "note random", "card position"
(The exact meaning of this configuration will be explained in the
"Configuration" section).
Maybe actually, you really want to see all cards in random order. You
don't want to see siblings together, you may want sometime to see 2nd
card before first one... In this card, use the configuration "card random".
I've got a note type where the first card is "easy", the second card is "harder" and so on. So you may want to see all first cards, then all second card when the first cards have been seen.
The configuration for this is one of:
"card position", "note creation" if you want to see notes in the order in
which they were added"card position", "note random" if you want to always see notes in the same
order, but a random order"card position", "card random" if you want to see cards in random order
(but still all first cards first, and so on...)Actually, even "show new card in order added" does not show new card in order they are added. Let me explain. It mostly shows cards in order in which there note are added. If a note (or note type) is edited so that new cards are edited, then the new card is dealt as follow:
This makes no sens to me. And you can now really sort cards using the
configuration "note creation", "card position"
This add-on is still experimental. Do a back up of your collection and check your result before actually doing real change to the order of new cards.
The order is computed taking into consideration the cards and notes which currently exists. It does not takes into consideration cards which will be added later. You need to sort again when you add new card. So this add-on is mostly interesting if you believe you won't need to add things to the deck regularly.
The configuration is given by a list of parameter, separated by
commas. (Technically, this is a json list, where the enclosings [
and ] are omitted.)
Sorting is done according to first parameter. In case of equality
according to second parameter. And so on. A paramater is either a
string "rule", or a pair ["rule", true]. If it is a string, the
sort is as follows:
Note that there are no equality in the two last cases; the order is complete, so it's useless to add more parameters after "card creation" or after "random".
If the parameter is a pair, the second element must be "true" (without the quotes) and it means this order is reversed.
Let's explain the examples given above.
The configuration "seen first", "note random", "card position" means
that cards with a sibling already seens are shown first. Then the
order of all cards are randomized. (But even if the order is
randomized, if a card has a seen sibling, it'll be first in the random
order). Then for different cards of the same note, the first card will
be seen before the second one, etc...
The configuration "card random" simply states that all cards are
randomized.
The configuration "card position", "note creation" means that all
first cards are seen, then all second cards, ... And since there may
be multiple first card, we see the one of the oldest note first, and
then the one of the second oldest note, ... and only when all of those
first cards are seen, the second card of the oldest note is seen. etc...
A value "special sort" is added to each deck object and to the configuration of the collection, to recall the last value used for each deck and for the collection.
None
A beautiful graphical interface
| Key | Value |
|---|---|
| Copyright | Arthur Milchior arthur@milchior.fr |
| Based on | Anki code by Damien Elmes anki@ichi2.net |
| License | GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html |
| Source in | https://github.com/Arthur-Milchior/anki_sort_cards |
| Addon number | 1665261045 |
| Support me on | ![]() |