In which Wildbook did the issue occur?
Whiskerbook
What operating system were you using? (eg. MacOS 10.15.3)
Windows 10
What web browser were you using? (eg. Chrome 79)
Latest Chrome
What is your role on the site? (admin, researcher, etc)
Orgadmin
What happened?
Hi
First of all, I would like to point out that I am working on the English version and not in French.
The list of viewpoints proposed when making an “add annotation” now contains French terms in addition to English terms, which nevertheless correspond to the same thing (example: “droite” and “right”). I don’t know how the software will understand this if someone chooses “droite” and someone else chooses “right” :
Good question. I’m used to seeing Spanish viewpoints in Flukebook when I’m viewing the site in English, but since you mentioned this is a recent change, I’ll check if this is intentional.
It turns out this was not intentional and you helped us to clean up the nonstandard viewpoints in Whiskerbook as well as Flukebook. They should appear correctly now. Thanks!
It looks like a Whiskerbook user is manually changing the viewpoint in the URL to create the French viewpoints we’ve seen. I was able to replicate this by:
Selecting a viewpoint (up) and iaClass,
Manually changing the viewpoint in the URL to a new word (tootsies)
Drawing and saving my annotation.
Then when you go back to the encounter and select the option to add a new annotation, you can see the previously added word in the list of viewpoints:
I don’t think we can figure out who is doing this, but it’s a good idea to remind users not to do this while we figure out how to prevent it in the meantime.
Oh, interesting! That is definitely more plausible. I had Google translate the page to French, selected “monter” from the viewpoints, and saw it reflected in the URL.
Ok, we’ve cleaned up the viewpoint list so that it displays fixed values. Previously it would query the database for viewpoints and display what it found in the drop-down menu.
We’ve also made changes that prevent Google Translate from modifying the fields in the Viewpoint and iaClass drop-down menus since for some reason the extension was changing the value of the fields rather than just translating them.