Wildbook 10.14

Wildbook 10.14: location roles and match fixes

Wildbook 10.14 is a small bug-fix release. Location-based roles now work everywhere in Wildbook, instead of only on the classic pages. The rest of the release fixes zooming on the Match Results page, matches started from a project page, and one untranslated label.

Access by location

• Location-based roles now work on the React pages, in search and through the API. A role named after a location ID (IoT uses names such as Indonesia and ORP-Pakistan) lets its holders view and edit encounters at that location and anywhere below it. Until now only the classic pages honoured those roles, so the same user saw the "start a collaboration" prompt on the React encounter page, and the encounter itself showed as inaccessible in search. A role on a child location still grants nothing on its parent. (#1755, fixes #1549 and #1244)

• Changing an encounter's location now requires permission to edit that encounter. Any user with the researcher role could previously move any encounter. (#1755)

Match Results page

• Zoom stays where you are pointing. The wheel zooms about the pointer and the toolbar buttons zoom about the middle of the pane. Zooming used to slide the animal out of frame, often by several hundred pixels at the page's initial magnification. (#1751, fixes #1747)

• The "This Encounter" label over the query image is now a link to that encounter, opening in a new tab. On a page showing several algorithms, each section links to its own query encounter. (#1706)

Identification

• Matches started from a project page now finish. "Start Match" ran the comparison and then threw the results away, so the page sat on "Match results are still being processed" and never gave up. Starting the same match from an encounter page always worked. This has been broken since 10.10.0 on installations whose IA.json uses MiewID or another vector-based configuration. Results are now saved as each annotation finishes, so one failure no longer discards the matches that already ran. (#1762, fixes #1761)

Other fixes

• The existing-keyword dropdown in the image modal's tags panel shows its label instead of the raw text SELECT_EXISTING_LABELLED_KEYWORD. (#1767)

For administrators

• There is no database schema change in 10.14, and no ml-service upgrade is required.

• Admins can grant only the location roles configured for the site. Add your location names to the roleN properties in commonConfiguration.properties; those entries are the checkboxes appadmin/users.jsp shows when assigning roles. The shipped file lists only the five reserved names (admin, researcher, rest, machinelearning, orgAdmin), and those are never read as locations.

• Search results pick up the new grants on the next background permissions pass, which is forced at least every 45 minutes by default (backgroundPermissionsMaxForceMinutes in OpenSearch.properties). Creating or deleting a role schedules the same pass. Editing locationID.json needs a restart.

• Matches already stuck on a project page do not recover on their own. Start them again after deploying the new WAR. (#1762)

Thanks to @goddesswarship for reporting all four issues fixed here, and to @naknomum for reviewing every pull request in the release.

Full changelog: Wildbook 10.14 milestone