掲示板 Forums - Possible bugs after the word merger

After login into renshuu today I was greeted with the word merger page, and I chose the custom option which allowed choosing which words to retain instead of merging them. I ran into some potential bugs while doing my daily reviews, I dont know if there are more since this was the first daily reviews after the merger I did and these were just the ones that popped-up during the reviews:

Above you see a kanji that I believe is in my schedules Advanced Kanji N1 but which I do not yet know as I only have it on my dashboard and haven't actually started studying it yet (still doing the N1 words list), on the bottom of the picture there's the word きずつく with the kanji 傷 in the quiz itself for the schedule, this is in the newly remade N3 words schedule that I have started doing since the new grammar companion linked schedule was released a few weeks ago, so it is a "new" word so to speak for me and I have had it a couple of times already without the kanji reading of course, but the quizzing of it was odd this time as it gave me a multiple choice for the word in the kanji form as one of the answer options even though I do not know the kanji yet since I haven't studied it. I searched all my Kanji schedules and it wasn't found in any of them, other than the Advanced Kanji N1 schedule which is on my dashboard but which I havent started studying yet, yet the quiz treated it as if I would know it already.

The other possible one that popped up was:

This was in my Pre-Advanced Words (N2) as 有り難い, which I am pretty sure I unchecked from the merger list, however it is only presenting it to me with the kana form, and even if my memory fails me it should have retained the mastery levels unless I misunderstood something about the word merger. I tried searching the form 有り難い from the schedules but there is only the kana form as above that remains in my schedule, I also lost 5 words from the schedule after the merger from 1744 to 1739 which I understand should be from the removal of possible duplicates but I am unsure about it.

Sorry for any misunderstandings on my part but I thought this might be useful information if it is indeed some form of a "bug".

I ran your account through a word/kanji rebinding - please let me know if it appears to be better for you.

Let's drill in on a single example and focus on fixing that, and then we'll move to the next. Otherwise, my brain melts.

So, with 捉える, can you confirm for me whether or not the kanji is marked as known in your account?

Ok, thanks!

So, no kanji knowledge on that kanji, which would make it default over to the kana vectors, which is what I see in the screenshot you posted above.

The merge tool did take a backup of all pre-merged data, so should we find out that something was lost, there is a way to get back to it.

However, looking at とらえる, I can see significant high kanji-based vectors, so you were studying it with the kanji on. I believe this is what happened. You were previously studying it on a rarer form of the term that used a different kanji. That is NOT the commonly used kanji for the term, but the previous one used a kanji that you did know.

So, when it got merged into the new term, it did carry over those kanji masteries, but since the new version uses a kanji you are not familiar with, it appears as if it is starting from scratch.

Thanks for looking into this

As I previously mentioned I suspect that the possible bug that was affecting the checkboxes previously a while back in my settings with the writing styles not registering the changes despite saving might be acting up on the merger page in the same manner, or I just might have messed something up myself while saving the changes for the custom option for the merge. If it is at all possible to check if there were any changes on merging from me opting out on them that were saved would be great and could shine some light on the issue. There were quite a few that I opted out from merging but for the past few days there has been a few more examples where the merge has happened despite me remembering on opting out on them (like for example 有り難い, or possibly 河 ) which has lead me to believe that any of the changes I made for the merge might have been discarded.

For example:

I used to have this in the 是非共 form in my N2 schedule, this time it kept the masteries which really isn't the issue for me even if it had dropped them as I dont mind reviewing the words even more as it's just extra learning for me. The problem really is just the lost forms for these words that I would have liked to have kept alongside the new more common ones in the schedules.

I'd be just as happy if I could even get a list of the words I had with the old forms before the merge that were to be merged with the new ones so I could add those forms back myself if at all possible while also keeping the new more common forms now in those schedules as it's just more learning for me and it's always a plus in my book. Again, thank you so much for taking the time to look into this

Not sure if this was caused because of the merger, but it started after it was implemented. Yesterday (11/17-18) and today, my みなの日本語 vocab schedule gets stuck and shows that I have 11 words left to review, but won’t load when I click the study button. Happens on mobile, can’t recall if on desktop.

Restarting the app doesn’t help.

Sarah: please contact me via DM.

Rahkojumi: I believe you're misunderstanding the top part of the tool.

The one for renshuu schedules are forced over - you cannot choose to have the rare form of the word remain in your schedule (at least, not via the merge tool) and not use the common term - the system would continually see a conflict between the lists that the schedule is comprised of, and the schedule itself. So if a renshuu schedule has a rare term, it was replaced with the common one.

Now, after the merge has been run, you can re-add that rare term if you'd like, and because it is added as an individual term, it will not conflict with the underlying lists. However, because this usage path is probably <.1% of users, it was not provided as an option in the merge tool, as I did not want to make it more complex than it already was. It was ultimately a dirty-but-best-possible-option to implement a one-time fix due to data issues I introduce into renshuu 15 or so years ago, and will never need to be revisited again. I do feel bad for the trouble it has caused some users, but it had to be done, and I had already done as much testing as I could with those that chose to use it during the testing period :(