这是一个使您理解的棘手问题,但让我尝试一下.
This is a tricky question to make you understand but let me attempt it.
今天,我的页面中有8个不同的portlet,并且在触发全局搜索框时,我触发了8个GSA查询,以将每个结果集显示在相应的portlet上.
Today, I have 8 different portlets in my page and when global search box is triggered I fire 8 GSA queries to show each result set onto the respective portlet.
每个GSA调用之间的区别是集合名称
The difference between each of the GSA call are the collection names
现在,我想不出一个解决方案,可以用一个呼叫替换8个不同的GSA呼叫.
Now I could not manage to think of a solution to replace 8 different GSA calls with one call.
每个集合至少包含10万个文档,每个请求/调用的GSA搜索响应所能提供的最大结果仅为1000和100.因此,对我而言,完全无法解析整个XML集并以编程方式将它们分组.
Each collection has atleast 100k documents and the max result a GSA search response can give is only 1000 and 100 per request/call. So it is quite impossible for me to parse the entire XML set and programmatically group them.
我知道用8个不同的查询显示8个不同的portlet是一个糟糕的设计,因此我不会从这个角度寻求帮助.设计的健壮性是一个假设.您能想到什么创造性的方法来解决这种逻辑吗?预先非常感谢,并感谢您阅读我的问题.
I know it is a poor design to show 8 different portlets with 8 different queries so I'm not looking for help from that angle. The design is robust is an assumption. Could you think of anything creative to address this logic? Thank you very much in advance and thank you for reading my question.
推荐答案在单个页面上的8个不同的Portlet中显示8个不同的结果集听起来像是一种非常不愉快的用户体验.
Displaying 8 different result sets in 8 different portlets on a single page sounds like a fairly unpleasant user experience.
如果重新设计它是一个选择,那么这听起来像是多面搜索效果很好的情况.
If redesigning it is an option then it sounds like a situation where faceted search would work well.
如果您使用动态导航,并且可以将8个集合分成8个方面(如果您使用实体识别以基于URL模式标记内容),您将获得更好的用户体验,允许用户自己向下钻取特定区域,而不用对其进行轰炸8种不同的结果集.
If you use Dynamic Navigation and can split your 8 collections up in to 8 facets (easy if you use Entity Recognition to tag the content based on URL patterns)you'll get a much better user experience, allowing users to drill down in to specific areas themselves rather than bombarding them with 8 different result sets.
更多推荐
GSA中的结果分组
发布评论