My users waste time searching for Nodes in NPM when they know something besides the nodes' names, because they'll paste in what they know and click "Search" without changing the drop-down to search that part of the nodes' fields.
For example, someone knows a node's IP address. They paste it into the Search By field and click Search. By default, Node Name was selected, and the IP address doesn't show up in the Search results.
So they have to start over by click the Back button, let the page reload, and then choose the right drop-down, enter the IP address, and click Search again. Yes, we understand this is a user training issue. But is it really? Maybe we could look at it as a limitation in NPM that might be easily corrected!
I'd like NPM to automatically search ALL the fields, or to be smart enough to recognize an IP address (or know that the info to search for matches a specific type of field) and start searching that field first.
It's computing, searching a database. Even with a thousand nodes, at computer speeds I'd expect this to be pretty fast--virtually as fast as if they'd narrowed the search by pre-selecting IP Address or some other field.
This is in NPM 7.7. Maybe it's already a feature added to newer versions?
In any case, it would be simpler, and it would save us time & frustration. If it's not too terrible a project, would you please include it in a future release?
If you Thwacksters could appreciate this simple improvement, I'd be appreciative if you'd give this an "up" vote!
Swift packets to you all!
Rick Schroeder
Top Comments