Every tool has its proper uses and its limitations, and that is certainly true for VDOT OneSearch, the library's federated search tool, which allows patrons to search up to 25 databases at once in real time, merging relevant results in a unified interface.
But as the adage goes: When your ONLY tool is a hammer everything starts looking like a nail! But there are some scenarios where you might not want to use OneSearch:
1. When you only need to search one database...go to that database and conduct your search from the "native interface." It won't take you any more time to do so, and will give you far more control in the search process, meaning you're less likely to miss relevant results.
2. If you have ample time to search and want to be really thorough... especially if you are only searching a few databases, you're best bet is to allocate your time to searching each database individually and merging the results manually.
3. If you have a really complicated search, OneSearch may not work as well as the native interface. Why? It's strength its its ability to pass a "simple" search on to many databases and retrieve the most relevant results quickly...but it loses that strength when searches get complex. In most cases, the native interfaces of the databases being searched by OneSearch have more complicated filters and limiting options.
4. If you need to search a database that is not in the list of 25 sources that OneSearch can search, then it is not a valid option. Again, go to the database you need to search if you can get to it yourself or contact the library for support.
Questions? Contact the library.
