Model-aware wiki analysis tools: The case of HistoryFlow
|Model-aware wiki analysis tools: The case of HistoryFlow|
|Author(s)||Diaz O., Puente G.|
|Published in||Proceedings of WikiSym 2010 - The 6th International Symposium on Wikis and Open Collaboration|
|Keyword(s)||analysis tools, collaboration, information visualization, interoperability, MDE, model-driven, visualization, web 2.0, Wiki (Extra: Analysis tools, collaboration, Information visualization, MDE, model-driven, Web 2.0, Wiki, Information analysis, Information systems, Visualization, World Wide Web, Interoperability)|
|Article||BASE, CiteSeerX, Google Scholar|
|Web||Ask, Bing, Google (PDF), Yahoo!|
|Download and mirrors|
|Local copy||Not available|
|Remote mirror(s)||Not available|
|Export and share|
|BibTeX, CSV, RDF, JSON|
|Browse properties · List of conference papers|
Model-aware wiki analysis tools: The case of HistoryFlow is a 2010 conference paper written in English by Diaz O., Puente G. and published in Proceedings of WikiSym 2010 - The 6th International Symposium on Wikis and Open Collaboration.
Wikis are becoming mainstream. Studies confirm how wikis are finding their way into organizations. This paper focuses on requirements for analysis tools for corporate wikis. Corporate wikis differ from their grow-up counterparts such as Wikipedia. First, they tend to be much smaller. Second, they require analysis to be customized for their own domains. So far, most analysis tools focus on large wikis where handling efficiently large bulks of data is paramount. This tends to make analysis tools access directly the wiki database. This binds the tool to the wiki engine, hence, jeopardizing customizability and interoperability. However, corporate wikis are not so big while customizability is a desirable feature. This change in requirements advocates for analysis tools to be decoupled from the underlying wiki engines. Our approach argues for characterizing analysis tools in terms of their abstract analysis model (e.g. a graph model, a contributor model). How this analysis model is then map into wiki-implementation terms is left to the wiki administrator. The administrator, as the domain expert, can better assess which is the right terms/granularity to conduct the analysis. This accounts for suitability and interoperability gains. The approach is borne out for HistoryFlow, an IBM tool for visualizing evolving wiki pages and the interactions of multiple wiki authors.
- This section requires expansion. Please, help!
Probably, this publication is cited by others, but there are no articles available for them in WikiPapers.