Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Woogle -- On Why and How to Marry Wikis with Enterprise Search


Published on

Enterprise Search engines are strong in locating existing documents and information in an organization while Wikis are designed to capture new information in a lightweight and collaborative fashion. Conversely, Wikis are rather bad in locating information (especially from external documents) while Enterprise Search does not address the provision of new information and socializing around information needs. Therefore we argue that both systems focus on specific parts of the organizational information process, which should indeed be combined in order to improve enterprise information exchange. We discuss “Woogle” as a concept to integrate Enterprise Search into Wikis and describe its reference implementation “Woogle4MediaWiki”.

Published in: Technology, Education
  • Login to see the comments

Woogle -- On Why and How to Marry Wikis with Enterprise Search

  1. 1. On Why and How to Marry Wikis with Enterprise Search Hans-Jörg Happel, FZI Karlsruhe, 26.03.2009 2nd Workshop on Integrated Knowledge Management Systems (IKMS2009) at 5 th Conference on Professional Knowledge Management, Solothurn (Switzerland), 2009
  2. 2. Agenda <ul><li>Marrying Wikis with Enterprise Search </li></ul><ul><li>Architecture & Implementation </li></ul><ul><li>Evaluation </li></ul>
  3. 3. Search and knowledge sharing are mutually intertwined (1) <ul><li>Search is an inherently social activity </li></ul><ul><ul><li>40,4% of users interact with others before and during search; 58,7% share information after search [EC08] </li></ul></ul><ul><li>Knowledge sharing typically depends on a trigger </li></ul><ul><ul><li>„ If asked for the information, participants would be willing to share most of the knowledge they accumulate in everyday life. However, they currently lack the tools to do so without exerting extraordinary effort” [DKT08] </li></ul></ul>
  4. 4. Search and knowledge sharing are mutually intertwined (2) <ul><li>However, this is typically not addressed by search and knowledge sharing tools  A fundamental gap between creating and accessing information exists </li></ul><ul><li>Research question: How to create a feedback loop to better connect information provision and access? </li></ul><ul><li>Idea: Combine the synergetic features of Wikis and Enterprise Search </li></ul>
  5. 5. Idea: Marry Wikis and Enterprise Search (1)
  6. 6. Idea: Marry Wikis and Enterprise Search (2)
  7. 7. Woogle: Design principles <ul><li>Improve information access </li></ul><ul><ul><li>Introduce better IR functions to Wiki </li></ul></ul><ul><ul><li>Provide integrated search </li></ul></ul><ul><li>Improve information provision </li></ul><ul><ul><li>Seamless transition from information seeking to information provision </li></ul></ul><ul><ul><li>Provide different modes of information provision </li></ul></ul><ul><ul><li>Guide information provision by aggregating information needs („need-driven knowledge sharing“) </li></ul></ul><ul><li>Improve collaboration </li></ul><ul><ul><li>Give queries a first order representation </li></ul></ul><ul><ul><li>Provide means for communication and awareness </li></ul></ul>
  8. 8. Need-driven knowledge sharing Collect information needs (e.g. from query logs) Calculate aggegate unsatisfied information needs Identify private files worth sharing („Inverse Search“ [Hap08b]) Combine Wikis and Search („Woogle“)
  9. 9. Woogle: Implementation <ul><li>Woogle is available for two environments </li></ul><ul><ul><li>MediaWiki: complete implementation replacing the built-in search </li></ul></ul><ul><ul><ul><li>WoogleNative: full PHP; only for MediaWiki content </li></ul></ul></ul><ul><ul><ul><li>WoogleRemote: using TeamWeaverIS Java backend as a web service; can index various different data sources </li></ul></ul></ul><ul><ul><li>Atlassian Confluence: prototype currently under development </li></ul></ul>
  10. 10. Anatomy of Woogle4MediaWiki External data sources can be accessed Collaborative description of the information need Notifications concerning search activities Discussion page Directly create new knowledge from the search dialog Search has a URI and can be linked from within the Wiki (one page per search term) Chose from different sources and/or content types Additional clues with meta-information about a need http://myHost/wiki/Woogle:SOAP
  11. 11. Evaluation plan <ul><li>Woogle will be evaluated in two steps </li></ul><ul><ul><li>Qualitative interviews/heuristic evaluation with a limited number of people (currently ongoing) </li></ul></ul><ul><ul><li>Online field experiments in real world environments (log analysis plus questionnaire) </li></ul></ul><ul><ul><ul><li>In internal projects </li></ul></ul></ul><ul><ul><ul><li>Industrial environments (additional partners sought! ) </li></ul></ul></ul><ul><li>Woogle has an instrumentation mode and advanded privacy settings for evaluation purposes </li></ul>
  12. 12. Related work <ul><li>Collaborative IR/“Social search“ </li></ul><ul><ul><li>Focus on synchronous collaboration </li></ul></ul><ul><ul><li>Do not address information provision </li></ul></ul><ul><li>Wiki & Search (Wikia Search, Google SearchWiki) </li></ul><ul><ul><li>Primarily focus on ranking/result annotation </li></ul></ul><ul><ul><li>Focus on the Web </li></ul></ul><ul><li>Q/A systems (e.g. Yahoo Answers) </li></ul><ul><ul><li>Lack „consensual spirit“ of Wikis </li></ul></ul><ul><ul><li>Do not consider external results </li></ul></ul>
  13. 13. Summary <ul><li>Woogle is a novel approach to combine Wikis and (Enterprise) Search </li></ul><ul><ul><li>Search becomes collaboratively customizable </li></ul></ul><ul><ul><li>Additional content can be added in a piecemeal fashion </li></ul></ul><ul><ul><li>Wikis become information hub by considering external results  improved bootstrapping? </li></ul></ul><ul><li>Next steps </li></ul><ul><ul><li>Evaluation is forthcoming – evaluation partners sought! </li></ul></ul><ul><ul><li>Possible extension concerning SMW (c.f. [Hap08a]) </li></ul></ul><ul><ul><li>Additional „social search“ features (e.g. social ranking) </li></ul></ul>
  14. 14. Literature <ul><li>[DKT08] Dearman, D., Kellar, M., and Truong, K. N. 2008. An examination of daily information needs and sharing opportunities. In Proceedings of the ACM 2008 Conference on Computer Supported Cooperative Work (San Diego, CA, USA, November 08 - 12, 2008). CSCW '08. ACM, New York, NY, 679-688. </li></ul><ul><li>[EC08] Evans, B. M. and Chi, E. H. 2008. Towards a model of understanding social search. In Proceedings of the ACM 2008 Conference on Computer Supported Cooperative Work (San Diego, CA, USA, November 08 - 12, 2008). CSCW '08. ACM, New York, NY, 485-494. </li></ul><ul><li>[Hap08a] Hans-Jörg Happel: Growing the Semantic Web with Inverse Semantic Search. In Proceedings of the 1st Workshop on Incentives for the Semantic Web (INSEMTIVE '08) </li></ul><ul><li>[Hap08b] Hans-Jörg Happel: Closing Information Gaps with Inverse Search. In Proceeedings of the 7th International Conference on Practical Aspects of Knowledge Management (PAKM2008) </li></ul><ul><li>[Mor08] Morris, M. R. 2008. A survey of collaborative web search practices. In Proceeding of the Twenty-Sixth Annual SIGCHI Conference on Human Factors in Computing Systems (Florence, Italy, April 05 - 10, 2008). CHI '08. ACM, New York, NY, 1657-1660. </li></ul>