You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the application currently only supports searching by scientific names it might be a good idea to support common names too. Common names are already saved to the database and mostly searchable from a source's web interface.
Both common names and scientific names could be queried from the same function as a common name query would also return matching scientific names and vice versa.
It might be a good idea to provide interfaces specific to either common names and scientific names too as they might decrease response times.
When returning scientific names for common names a second type parameter makes sense so either one can be filtered after using the shared interface.
The text was updated successfully, but these errors were encountered:
An attempt was made about two years ago on feature branch reverse_common_names_search but it was neither merged nor documented. Implementations will be evaluated and added soon.
While the application currently only supports searching by scientific names it might be a good idea to support common names too. Common names are already saved to the database and mostly searchable from a source's web interface.
Both common names and scientific names could be queried from the same function as a common name query would also return matching scientific names and vice versa.
It might be a good idea to provide interfaces specific to either common names and scientific names too as they might decrease response times.
When returning scientific names for common names a second
type
parameter makes sense so either one can be filtered after using the shared interface.The text was updated successfully, but these errors were encountered: