-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Match should check if there is duplicate bookmarks #304
Comments
I don't remember seeing that happen! i think the second is a good choice: avoiding duplicate bookmarks in match. one way would be to solve this when we're assigning words to exercise types. |
I think the easiest would be to do at the API level, so whenever we do the priority_bookmarks call, we just filter any duplicated words. However, I think when we call for "similar" bookmarks we don't check for repeated words. So maybe this could be an issue in multiple choice? Rare, but could happen. |
That should be fine. Should be very rare. And in the future we might move away from a separate call to similar words as suggested in another convo these days! |
Alright! Should I make this as part of the changes to the work schedule? I will add a line that filters out any words that are repeated? |
Sure!
m.
… On 19 Feb 2024, at 13.39, Tiago Ribeiro ***@***.***> wrote:
Alright! Should I make this as part of the changes to the work schedule? I will add a line that filters out any words that are repeated?
—
Reply to this email directly, view it on GitHub <#304 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADRNBZB4B5HUEC4HIJFBYDYUM2VPAVCNFSM6AAAAABDO7NQQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSGI3DQMJXGE>.
You are receiving this because you commented.
|
When a user has translated the same word in different contexts a situation like this can happen:
Since the match is done by ID it means in this situation, it's a 50/50 if the user will get it correct.
This could be fixed in 2 ways, either:
I would go with the second one.
The text was updated successfully, but these errors were encountered: