Open m-hope opened 5 years ago
Tested the following:
Created a profile Acanthocarpus preissii matching the name on creation. name did not appear in autocomplete I typed the full name in and it was matched the profile created with occurrences on map and images all correct nomenclature was populated Created a profile Acanthocarpus Testing1 as an unmatched profile chose not to match it to a name selected to specify hierarchy selected species selected to specify parent entered Acanthocarpus (no autocomplete) checked name (found name) created profile with -- many occurrences (I assume is this is providing all occurrences with acanthocarpus in name?) -- no images (correct as expected) -- no nomenclature (correct as expected) -- hierarchy is correct In the above profile I used the edit name option to match to Acanthocarpus Preissii opened profile in edit selected edit name selected check name selected search for a match typed in Acanthocarpus and selected Acanthocarpus preissii from autocomplete which is working selected update name Profile updates with: -- images -- map not updated -- nomenclature not updated (I think this is correct as NSL would have no listing for this name although it has been mapped to Acanthocarpus preissii?) -- Note: if you remove the matched name and save and then match the name again the map works ok. tested this with Eucalyptus erythronema subsp. erythronema with same result - everything worked ok except the map updating once a profile with an unknown name was matched to the subspecies name
To do: create bug for occurrence map to update when matched to a name
Hi @m-hope - I will create the 2 tickets mentioned above and aply the testing complete label.
Generally speaking this works... auto-complete names are presented and can be selected (and when selected will allow the manually profile renaming function to work correctly. However, the display of the autocorrect names in the drop down list is erratic. Eg: if the user types "Acacia", then random acacia's are displayed and often (eg: for "Acacia victoriae") the list will only display the required species name when it is typed in completely and correctly. The normal expectation would be that as you type "Acacia v" that the auto-correct list would display all acacia species beginning with "v" at the top of the list.
Have logged this as a new (minor) issue #670 and therefore happy to close this issue.
As tested in #591, when a profile is being manually matched to a name, the value in the field is ignored and the profile is essentially unmatched: Ie:
This occurs in any place that uses the "Search for the name you wish to match to" field, including:
Note the "Search for the name you wish to match to field" does not have auto-correct working... this may be related to the issue.