WildMeOrg
ID prefix missing from match page
Background
When a location ID has a prefix assigned to it in locationID.json ("prefix": "BSN","prefixDigitPadding": 3), unknown animals seen in that location receive a suggested ID with that prefix (such as BSN001).
Current behavior
Users see different suggested IDs between the match page (/iaResults.jsp) and the encounter page's Identification section (/encounters/encounter.jsp).
The encounter page shows the correct available ID with prefix, but the match page suggests a different ID (in GiraffeSpotter) or none at all (SeadragonSearch). When you save a suggested ID from the match page, the ID with the prefix is the one that's actually assigned even though the match page shows a different suggested ID.
Expected behavior
The suggested ID on the match page (/iaResults.jsp) and on the edit Identification section of the encounter page (/encounters/encounter.jsp) are both the same.
Testing notes Test encounter: GiraffeSpotter
Encounter page appearance:
GiraffeSpotter - shows next available ID with prefix
SeadragonSearch - shows next available ID with prefix
Match page appearance:
GiraffeSpotter - shows random ID with no prefix
SeadragonSearch - no ID suggested
Encounter page after saving ID on match page:
GiraffeSpotter
Seadragon Search - No ID suggested on match page; have to manually enter or set on encounter page.
Community link https://community.wildme.org/t/new-location-request/2889/9 (resolved, but included for reference)
Additional testing needed to verify if the discrepancy only occurs when an ID prefix is defined in the location ID file.
@goddesswarship I think we were seeing a similar issue with the project IDs on that page, for testing reference?
Will re-test in more Wildbooks to verify whether this is limited to GS only.
Couldn't test in Flukebook due to maintenance, but verified against SeadragonSearch that the behavior is similar. Updated testing notes with additional screenshots and test encounter.