-54y 2w ??? What is this?
- Thread starter dightonjw
- Start date
Is this a legacy test? My guess is that it's the 'time past due' status field, and that the number is so high because that's the amount of time before the card was scheduled to be due again. Since it's coming up now anyway, it might be that that field is selected but in a test type that's not actually using spaced repetition, so it's a random / meaningless value.
If you email us a backup of your flashcard database, or post a screenshot of the statistics for this card in the Card Info screen, we can try to figure out more details from there.
If you email us a backup of your flashcard database, or post a screenshot of the statistics for this card in the Card Info screen, we can try to figure out more details from there.
It is a legacy test.
If it's possible to migrate all these cards to whatever 4.0 uses, I'd prefer to do that if it'll resolve these problems. What's the recommended migration strategy anyway? Start from scratch in 4.0 or somehow migrate?
Actually the recommended strategy at the moment is to keep them in Legacy. The code for that is all new in 4.0 - we reimplemented the old system with the new rule/stream-based test profile system, just as with all of our new profile types - so it's not something we're trying to deprecate or move people away from.
The only thing really 'wrong' with that field is that it shouldn't be selectable in a legacy test that isn't using spaced repetition, or it should say something generic like 'random' for random card selection. Again, if you're OK with sharing a backup of your database (or posting a screenshot of the card info) we can dig in on this end to double check that it's not some other sort of bug, but even in that case it ought to be fixable.
The only thing really 'wrong' with that field is that it shouldn't be selectable in a legacy test that isn't using spaced repetition, or it should say something generic like 'random' for random card selection. Again, if you're OK with sharing a backup of your database (or posting a screenshot of the card info) we can dig in on this end to double check that it's not some other sort of bug, but even in that case it ought to be fixable.