A comparison of success rates between sessions with promotions (promoted sessions) and search sessions without promotions (standard sessions) is presented as Figure 18.6. The results show that during the course of the 10 week trial, on average, sessions with promotions are more likely to be successful (62%) than standard sessions (48%) containing only Google results, a relative benefit of almost 30% due to the community-based promotion of results. In other words, during the course of the trial we found that for more than half of the standard Google search sessions users failed to find any results worth selecting. In contrast, during the same period, the same searchers experienced a significantly greater success rate for sessions that contained community promotions, with less than 40% of these sessions failing to attract user selections.Within an enterprise these results can have an important impact when it comes to overall search productivity because there are significant savings to be made by eliminating failed search sessions in many knowledge-intensive business scenarios. For example, a recent report [30] by the International Data Corporation (IDC) found that, on average, knowledge workers spend 25% of their time searching for information, and an enterprise employing 1,000 knowledge workers will waste nearly $2.5 million per year (at an opportunity cost of $15 million) due to an inability to locate and retrieve information. In this context any significant reduction in the percentage of failed search sessions can play an important role in improving enterprise productivity, especially in larger organisations.
18.4.4 Discussion
The model of collaborative web search presented here is one that seeks to take advantage of naturally occurring query repetition and result selection regularity among communities of like-minded searchers. In this case-study we have focused on one particular type of search community in the form of a group of employees. Obviously this is a reasonably straightforward community to identify and it is perhaps not surprising that we have found a high degree of repetition and regularity to take advantage of during collaborative web search. Nonetheless, this type of community, where groups of individuals come together to perform similar information finding tasks, is a common one, whether it is employees in a company or students in a class or researchers in a research group. There are of course many other types of community. For example, we have already mentioned the scenario where a group of visitors to a themed web site can be considered to be an ad-hoc search community. More generally, it is interesting to consider the open question of community discovery and identification, and there is considerable research at the present time devoted to exploring various approaches to automatically identifying online communities; see for example [11, 5, 21, 106, 105]. And as we develop a better understanding of the nature of online communities in the new world of the social web it may be possible to offer a more flexible form of search collaboration, facilitated by a more flexible and dynamic definition of search community.
18.5 Case-Study 2 - Web Search. Shared.
The previous case-study looked at a community-oriented view of collaborative web search, where the search activities of like-minded communities of searchers were used to influence mainstream search engine results. In this section we describe an alternative model of collaborative web search, as implemented in a system called HeyStaks, that is different in two important ways. First of all, HeyStaks adopts more user-led approach to collaborative web search, one that is focused on helping users to better organise and share their search experiences. HeyStaks does this by allowing users to create and share repositories of search experiences as opposed to coordinating the participation of search communities. Secondly, we adopt a very different approach to search engine integration. Instead of the proxy-based approach described in the previous case-study, HeyStaks is integrated with a mainsream search engine, such as Google, through a browser toolbar, which provides the collaborative search engine with the ability to capture and guide search activities. Finally, we will also summarize the findings of a recent live-user study to investigate the nature of search collaboration that manifests within HeyStaks’ user population.
18.5.1 The HeyStaks System
HeyStaks adds two basic features to a mainstream search engine. First, it allows users to create search staks, as a type of folder for their search experiences at search time. Staks can be shared with others so that their searches will also be added to the stak. Second, HeyStaks uses staks to generate recommendations that are added to the underlying search results that come from the mainstream search engine. These recommendations are results that stak members have previously found to be relevant for similar queries and help the searcher to discover results that friends or colleagues have found interesting, results that may otherwise be buried deep within Google’s default result-list.
As per Fig. 18.7, HeyStaks takes the form of two basic components: a client-side browser toolbar and a back-end server. The toolbar allows users to create and share staks and provides a range of ancillary services, such as the ability to tag or vote for pages. The toolbar also captures search click-throughs and manages the integration of HeyStaks recommendations with the default result-list. The back-end server manages the individual stak indexes (indexing individual pages against query/tag terms and positive/negative votes), the stak database (stak titles, members, descriptions, status, etc.), the HeyStaks social networking service and, of course, the recommendation engine. In the following sections we will briefly outline the basic operation of HeyStaks and then focus on some of the detail behind the recommendation engine. Consider the following motivating example. Steve, Bill and some friends are planning a European vacation and they know that during the course of their research they will use web search as their primary source of information about what to do and where to visit. Steve creates a (private) search stak called “European Vacation 2008“ and shares this with Bill and friends, encouraging them to use this stak for their vacation-related searches.
Fig. 18.8 shows Steve selecting this stak as he embarks on a new search for “Dublin hotels“, and Fig. 18.9 shows the results of this search. The usual Google results are shown, but in addition HeyStaks has made two promotions. These have
Results (
Thai) 1:
[Copy]Copied!
การเปรียบเทียบอัตราความสำเร็จระหว่างช่วง มีโปรโมชั่น (ส่งเสริมรอบ) และค้นหาเซสชัน โดยโปรโมชั่น (รอบเวลามาตรฐาน) จะแสดงเป็นรูป 18.6 ผลลัพธ์แสดงว่าระหว่างสัปดาห์ 10 ทดลอง เฉลี่ย ช่วงกับโปรโมชั่นมีแนวโน้มที่จะ ประสบความสำเร็จ (62%) มากกว่ามาตรฐานรอบ (48%) ประกอบด้วยเพียง Google ผลลัพธ์ สวัสดิการญาติเกือบ 30% เนื่องจากชุมชนส่งเสริมผลการ ในคำอื่น ๆ ในระหว่างการทดลองเราพบว่า มากกว่าครึ่งหนึ่งของ Google มาตรฐานค้นหา เซสชันของผู้ใช้ไม่สามารถหาผลลัพธ์ใด ๆ คุ้มค่าเลือก ในทางตรงกันข้าม ในช่วงเวลาเดียวกัน ผู้เดียวพบอัตราความสำเร็จมากกว่าอย่างมีนัยสำคัญสำหรับเซสชันที่มีอยู่ชุมชนส่งเสริมการขาย ต่ำกว่า 40% ของการดึงดูดผู้ใช้เลือกช่วงเวลา ภายในองค์กรผลลัพธ์เหล่านี้สามารถมีผลกระทบสำคัญเมื่อมันมาเพื่อค้นหาประสิทธิภาพโดยรวมเนื่องจากมีการประหยัดที่สำคัญจะทำการตัดไม่สามารถค้นหาเซสชันในสถานการณ์ธุรกิจเร่งรัดความรู้มากมาย ตัวอย่าง รายงานล่าสุด [30] โดยบริษัทข้อมูลนานาชาติ (IDC) พบว่า เฉลี่ย ความรู้ผู้ปฏิบัติงานใช้ 25% ของเวลาการค้นหาข้อมูล และองค์กรที่ใช้แรงงานความรู้ 1000 จะเสียเกือบ 2.5 ล้านดอลลาร์ต่อปี (ที่มีโอกาสที่ต้นทุนของ $15 ล้านบาท) เนื่องจากไม่สามารถค้นหา และดึงข้อมูล ในบริบทนี้ ลดเปอร์เซ็นต์ของรอบเวลาการค้นหาล้มเหลวใด ๆ สำคัญสามารถเล่นมีบทบาทสำคัญในการเพิ่มประสิทธิภาพองค์กร โดยเฉพาะอย่างยิ่งในองค์กรขนาดใหญ่ 18.4.4 DiscussionThe model of collaborative web search presented here is one that seeks to take advantage of naturally occurring query repetition and result selection regularity among communities of like-minded searchers. In this case-study we have focused on one particular type of search community in the form of a group of employees. Obviously this is a reasonably straightforward community to identify and it is perhaps not surprising that we have found a high degree of repetition and regularity to take advantage of during collaborative web search. Nonetheless, this type of community, where groups of individuals come together to perform similar information finding tasks, is a common one, whether it is employees in a company or students in a class or researchers in a research group. There are of course many other types of community. For example, we have already mentioned the scenario where a group of visitors to a themed web site can be considered to be an ad-hoc search community. More generally, it is interesting to consider the open question of community discovery and identification, and there is considerable research at the present time devoted to exploring various approaches to automatically identifying online communities; see for example [11, 5, 21, 106, 105]. And as we develop a better understanding of the nature of online communities in the new world of the social web it may be possible to offer a more flexible form of search collaboration, facilitated by a more flexible and dynamic definition of search community.
18.5 Case-Study 2 - Web Search. Shared.
The previous case-study looked at a community-oriented view of collaborative web search, where the search activities of like-minded communities of searchers were used to influence mainstream search engine results. In this section we describe an alternative model of collaborative web search, as implemented in a system called HeyStaks, that is different in two important ways. First of all, HeyStaks adopts more user-led approach to collaborative web search, one that is focused on helping users to better organise and share their search experiences. HeyStaks does this by allowing users to create and share repositories of search experiences as opposed to coordinating the participation of search communities. Secondly, we adopt a very different approach to search engine integration. Instead of the proxy-based approach described in the previous case-study, HeyStaks is integrated with a mainsream search engine, such as Google, through a browser toolbar, which provides the collaborative search engine with the ability to capture and guide search activities. Finally, we will also summarize the findings of a recent live-user study to investigate the nature of search collaboration that manifests within HeyStaks’ user population.
18.5.1 The HeyStaks System
HeyStaks adds two basic features to a mainstream search engine. First, it allows users to create search staks, as a type of folder for their search experiences at search time. Staks can be shared with others so that their searches will also be added to the stak. Second, HeyStaks uses staks to generate recommendations that are added to the underlying search results that come from the mainstream search engine. These recommendations are results that stak members have previously found to be relevant for similar queries and help the searcher to discover results that friends or colleagues have found interesting, results that may otherwise be buried deep within Google’s default result-list.
As per Fig. 18.7, HeyStaks takes the form of two basic components: a client-side browser toolbar and a back-end server. The toolbar allows users to create and share staks and provides a range of ancillary services, such as the ability to tag or vote for pages. The toolbar also captures search click-throughs and manages the integration of HeyStaks recommendations with the default result-list. The back-end server manages the individual stak indexes (indexing individual pages against query/tag terms and positive/negative votes), the stak database (stak titles, members, descriptions, status, etc.), the HeyStaks social networking service and, of course, the recommendation engine. In the following sections we will briefly outline the basic operation of HeyStaks and then focus on some of the detail behind the recommendation engine. Consider the following motivating example. Steve, Bill and some friends are planning a European vacation and they know that during the course of their research they will use web search as their primary source of information about what to do and where to visit. Steve creates a (private) search stak called “European Vacation 2008“ and shares this with Bill and friends, encouraging them to use this stak for their vacation-related searches.
Fig. 18.8 shows Steve selecting this stak as he embarks on a new search for “Dublin hotels“, and Fig. 18.9 shows the results of this search. The usual Google results are shown, but in addition HeyStaks has made two promotions. These have
Being translated, please wait..