掲示板 Forums - way to estimate review terms for tomorrow
Top > renshuu.org > Questions about renshuu
if i complete my reviews i end up learning a lot of new terms but then sometimes i do too many and tomorroe have so many review. is there way to estimate how many reviews coming tomorroe so i can stop myself from learning too many new terms? 
If you open any schedule, it should give you the number of terms you'd get for review over the next week (Daily study goals).
Note that those are "terms", so if you study multiple vectors that number won't correctly reflect the number of reviews. It's also not possible to get the total across all schedules.
Generally, when you learn a new term it will come up for review immediately (the next day). You can actually see the number go up for each new term you learn. E.g. if I learn a new kanji for that schedule, that 5 will become a 6.
Now for what you can potentially do with the API: The "schedule" endpoint does give you "upcoming", so you can easily get the total. Still not perfect, since it doesn't account for vectors.
If you take a look at terms, they do give you the next time (as a date) they'll come up for review (by individual vectors). This seems very annoying to work with though. I'm just letting you know it's available.
PS: I always have this setting on for all of my schedules: "Don't learn new terms until daily review is finished". It allows you to complete all of your reviews without worrying about new terms.
wow! thank you, Georgi!! u answered questions of mine b4 ,too so thanks! when i played with api two weeks ago, I didnt notice this! I think when I get some time maybe I will just hook a call to api through tampermonkey to display list or heatmap of the upcomings (process + dom inject), depending on size of pulled object. most likely will tie to a button so to only do it once a day or something on manual user click to so as not hammer the api. forget if there is prefilter in query for serverside offloading prior to return object on large lists like only return if < 7 days then construct table or heatmap across traversal of that prefiltered list.
I like how they can be broken down by vector, too.... i need to make that vector-aware "real review number" adjustment script, too (as in, instead of showing user number of due terms, shows also in parentheses the number of reviews across all scheduled vectors to give user more realistic picture without user needing to multiply by vector approximate product in head).
thx for tip 2 about using review first before learn new which i have checked already
thank you! 
Top > renshuu.org > Questions about renshuu