Not sure if this question is better suited for a different StackExchange site but, here goes:
I have a search page that searches a number of different type of things. All (at the moment) requiring a different input field for each type of search. For example, one might search for a school or district name, a class name, a staff member email address, etc. I have 9 different 'type' of searches each with their own input field on the search page. I've already concatenated one of these (a username and UID search) but I'm wondering if it makes sense both design (user friendly) and performance wise to bring these all into one input field (and therefore one singular search)
These different types are of course a number of different tables, so it would have to query a number of different times for each type, just for one search.
Any ideas? or should I just keep it how it is? I could add a drop-down menu to choose a different 'type' of search but that seems just as messy. I'm already doing this for my navbar when not on the main search page (which also happens to be the home page)
My project is written in Python with the Pyramid framework.
答案 0 :(得分：0)
我可以看到这个被发布到UX SE（我认为是ux.stackexchange.com？）网站，或者他们可能已经有一个问题触及这样的事情了。但我个人可能会倾向于使用不同类型的下拉选择器，或保持单独的搜索。而且我认为我更倾向于下拉框 - 这对我来说对于搜索界面来说似乎并不合理。
我想一个问题是 - 是否有任何期望在同一搜索中想要多个表中的结果？如果是这种情况，我可以看到实现统一搜索的想法，即使它意味着查询多个表。或者某种添加剂界面，您可以在其中选择要查询的表格。
答案 1 :(得分：0)
如果应用程序发生变化，您的搜索界面会发生什么变化？这是一个非常重要的方面。你又添加了另一种搜索类型吗？
搜索返回查询字符串上的匹配项。结果集可以包含不同类型的不同实体。然后您的搜索/结果集界面可以根据实体类型或实体方面应用过滤（例如：Ebay，亚马逊）
向Solr / elasticsearch和附加项目学习。分面搜索是用户最近习惯使用的内容。与编写跨越多个表的复杂查询相比，分离数据存储（RDBMS）和全文搜索引擎的概念更加强大和可扩展。任何较大的互联网公司（Ebay，Facebook，亚马逊，Instagram）都可以讲述使用模式的故事。将存储与搜索分开可提供可扩展性和灵活性。
不是编写查询/搜索代码，而是更好地学习如何从任何数据存储中提供这些搜索引擎。这是更强大和更强大的很有趣，我保证。