DOCSLIB.ORG

The History, Application and Future Potential of Wiki‟S an Interactive Qualifying Project Report

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The History, Application and Future Potential of Wiki‟S an Interactive Qualifying Project Report The History, Application and Future Potential of Wiki‟s An Interactive Qualifying Project Report Interactive Qualifying Project Report completed in partial fulfillment of the Bachelor of Science degree at Worcester Polytechnic Institute, Worcester, MA Submitted to: Professor Fred J. Looft (advisor) Professor Xinming Huang (co-advisor) QIAN WEI [email protected] STEFAN GIUSTI [email protected] February 27th, 2009 ___________________________ Advisor Signature ___________________________ Co-advisor Signature Abstract: This report discusses the future of collaborative work and wiki systems, with a strong focus on educational impact of collaboration. This report shows the research done by the team on current wiki systems and course management software. The research is used to determine guidelines for the proper implementation of collaborative systems as well as provide specific innovations for collaborative systems. The report is meant to pave the way for more efficient and streamlined course management systems to improve higher education. ii Acknowledgements We would like to thank Professor Fred J. Looft and Professor Xinming Huang from Department of Electrical and Computer Engineering, Worcester Polytechnic Institute for their guidance, instruction and help. Also, we wish to express our gratitude to Sir Robert Brown, Manager of Computational Facilities and Administrator of Computer System of Department of Electrical and Computer Engineering, Worcester Polytechnic Institute for the technical support during the past twenty-one weeks. Your time and efforts are greatly respected and appreciated. Our group would like to graciously thank Xin Geng and Gao Wei for their great help and invaluable insights. iii Authorship Page This report was co-authored and edited equally by each contributing author. The group assumes all the responsibility for the authorship and editing of this report. Qian Wei Stefan Giusti iv Table of Contents Abstract: ........................................................................................................................................................ ii Acknowledgements ...................................................................................................................................... iii Authorship Page ........................................................................................................................................... iv List of Tables and Figures ........................................................................................................................... vii Executive Summary ................................................................................................................................... viii Chapter 1: History of the Wiki and its Origins ........................................................................................... 1 1.1 Introduction ................................................................................................................................... 1 1.2 What is a Wiki? ............................................................................................................................. 2 1.3 The First Wiki ............................................................................................................................... 3 1.4 The Wiki Compared to Other Websites ........................................................................................ 4 1.5 Wiki Characteristics ...................................................................................................................... 6 1.6 Summary ....................................................................................................................................... 6 Chapter 2: Capabilities and Existing Applications of Wiki Systems .......................................................... 7 2.1 Introduction .................................................................................................................................. 7 2.2 Social Implications of Wiki Systems ............................................................................................ 7 2.3 The Capabilities of Wiki Systems ................................................................................................. 8 2.4 Existing Wikis and Their Applications ....................................................................................... 10 2.5 Wiki Applications ....................................................................................................................... 16 2.6 Conclusions ................................................................................................................................. 19 Chapter 3: The Potential of Wiki Systems ................................................................................................ 20 3.1 The Potential of Wiki Systems ................................................................................................... 20 3.2 Project Statement ........................................................................................................................ 20 3.3 Goals and Objectives ................................................................................................................. 21 3.4 Conclusions ................................................................................................................................ 21 Chapter 4: Survey of MyWPI Reactions ................................................................................................... 22 4.1 Introduction ................................................................................................................................ 22 4.2 Survey Expectations .................................................................................................................... 22 4.3 Do the Participants Use MyWPI? ............................................................................................... 24 4.4 Do the Participants Believe Note Sharing is Beneficial? ............................................................ 27 4.5 Suggestions on Current MyWPI System..................................................................................... 30 4.6 Conclusion .................................................................................................................................. 30 Chapter 5: Collaboration in the Ideal Course Management System ......................................................... 31 v 5.1 Introduction ................................................................................................................................ 31 5.2 A Wiki as a Collaborative Writing Tool ..................................................................................... 31 5.3 Discussion Threads on Course Documents ................................................................................. 33 5.4 Wiki as a Scheduling Tool .......................................................................................................... 35 5.5 Features for More, and Meaningful Contributions ..................................................................... 35 5.6 Conclusion .................................................................................................................................. 37 Chapter 6: Conclusions and Recommendations ........................................................................................ 39 6.1 Introduction ................................................................................................................................ 39 6.2 Conclusions ................................................................................................................................. 39 6.3 Recommendations ....................................................................................................................... 40 References ................................................................................................................................................... 41 Definitions .................................................................................................................................................. 43 vi List of Tables and Figures Table 2.1 14 Table 2.2 16 Table 2.3 17 Figure 1.1 3 Figure 1.2 4 Figure 2.1 11 Figure 2.2 11 Figure 2.3 12 Figure 2.4 15 Figure 2.5 15 Figure 2.6 16 Figure 4.1 24 Figure 4.2 25 Figure 4.3 26 Figure 4.4 27 Figure 4.5 28 Figure 4.6 29 Figure 5.1 33 Figure 5.2 34 Figure 5.3 36 Figure 5.4 37 vii Executive Summary Wiki, a new web concept, has provided a unique way for people to share information. The first wiki was created by Ward Cunningham in 1994. Ward, as a Smalltalk programmer, intended to use the web to allow every programmer to manage and share their ideas. Wiki systems have been improved dramatically in the following years. A wiki is different from other websites in that it allows anyone to edit the content. Like other web sites, a wiki page can contain hyperlinks which direct the current page to another page. Hyperlinks also enable cross referencing between numbers of pages, which makes wiki pages organized and connected. In addition, the history reversion function from the wiki system allows any page to be reverted to a previous version. Due to these characteristics, wiki systems are usually good for people collaborating on a certain subject. Today, the most well-known wiki site is probably the Wikipedia.org, a free online encyclopedia which allows anyone to edit its entries. Beyond
Load more

Recommended publications
  • Common Tools for Team Collaboration Problem: Working with a Team (Especially Remotely) Can Be Difficult
    Common Tools for Team Collaboration Problem: Working with a team (especially remotely) can be difficult. ▹ Team members might have a different idea for the project ▹ Two or more team members could end up doing the same work ▹ Or a few team members have nothing to do Solutions: A combination of few tools. ▹ Communication channels ▹ Wikis ▹ Task manager ▹ Version Control ￭ We’ll be going in depth with this one! Important! The tools are only as good as your team uses them. Make sure all of your team members agree on what tools to use, and train them thoroughly! Communication Channels Purpose: Communication channels provide a way to have team members remotely communicate with one another. Ideally, the channel will attempt to emulate, as closely as possible, what communication would be like if all of your team members were in the same office. Wait, why not email? ▹ No voice support ￭ Text alone is not a sufficient form of communication ▹ Too slow, no obvious support for notifications ▹ Lack of flexibility in grouping people Tools: ▹ Discord ￭ discordapp.com ▹ Slack ￭ slack.com ▹ Riot.im ￭ about.riot.im Discord: Originally used for voice-chat for gaming, Discord provides: ▹ Voice & video conferencing ▹ Text communication, separated by channels ▹ File-sharing ▹ Private communications ▹ A mobile, web, and desktop app Slack: A business-oriented text communication that also supports: ▹ Everything Discord does, plus... ▹ Threaded conversations Riot.im: A self-hosted, open-source alternative to Slack Wikis Purpose: Professionally used as a collaborative game design document, a wiki is a synchronized documentation tool that retains a thorough history of changes that occured on each page.
    [Show full text]
  • Tiddlywiki in Science Education
    1 TiddlyWiki in Science Education Franco Bagnoli Dipartimento di Energetica & Centro Dinamiche Complesse Universita` di Firenze, I-50139 Firenze, Italy Email: [email protected] Peter Jipsen Department of Mathematics and Computer Science Chapman University, Orange, CA 92866, USA Email: [email protected] Andrea Sterbini Dipartimento di Informatica Universita` di Roma 1, I-00198 Roma, Italy Email: [email protected] Abstract— We discuss here an ongoing experiment and questions are communicated and answered by which uses ASciencePad [1], an adapted version of Tid- voice, or using e-mail, web forms and chat forums, dlyWiki [2] as a support for teaching/learning physics but seldom stored and/or converted to a structured (elementary and advanced) to engineering students. form, like for instance a FAQ table. ASciencePad is a “live math notebook” that is editable with a modern browser and includes a WYSIWYG editor This almost one-way communication is rather with mathematical formulas and SVG plots. It allows unsatisfactory, especially when teachers and stu- also the inclusion of JavaScript simulations, that can be dents come from a very different background, like easily edited by users and therefore can be used as a in our case of teaching physics for two master playground for computational experiments. Our graph level courses in environmental engineering. Stu- drawing extension allows the construction of graph maps dents’ feedback, possibly in the form of an edited of the learning paths to help the student navigate through the notebook topics. frequently asked question (FAQ) list, is a didacti- This client-side tool is complemented by a wiki-based cally valuable tool.
    [Show full text]
  • Analyzing and Visualizing the Semantic Coverage of Wikipedia and Its Authors
    Holloway, Todd, Božicevic, Miran and Börner, Katy. (2007) Analyzing and Visualizing the Semantic Coverage of Wikipedia and Its Authors. Complexity, Special issue on Understanding Complex Systems. Vol. 12(3), pp. 30-40. Also available as cs.IR/0512085. Analyzing and Vis ualizing the S emantic C overage of Wikipedia and Its Authors Todd Holloway Indiana University Department of C omputer S cience 150 S . W oodlawn Ave. Lindley Hall 215 Bloomington, IN 47405, US A P hone: (812) 219-2815 E mail: tohollow@ cs.indiana.edu Miran Božievi Wikipedia Networks Team Multimedia Institute (http://www.mi2.hr) Preradovieva 18 HR-10000 Zagreb Croatia Email: [email protected] Katy Börner* Indiana University, SLIS 10th Street & Jordan Avenue Main Library 019 Bloomington, IN 47405, USA Phone: (812) 855-3256 Fax: -6166 E-mail: [email protected] WWW: http://ella.slis.indiana.edu/~katy * To whom all correspondence and proofs are to be addressed. Keywords Network analysis, link analysis, information visualization Number of text pages: 20 Number of figures: 6 Number of tables: 3 1. Introduction ................................................................................................................................................................3 1.1 Wiki Technology and Wikipedia............................................................................................................................3 1.2 Accuracy, Bias and Persistence ...........................................................................................................................4
    [Show full text]
  • Wikis with Moinmoin Wiki Creative Group Writing
    KNOW HOW MoinMoin Wiki Building wikis with MoinMoin Wiki Creative Group Writing The members of a project team can profit from collecting their ideas, or any loose ends, in a central repository. Wikis are tailor-made for this task. BY HEIKE JURZIK ay before content manage- ment systems started to Wappear for website manage- ment, Wikis provided a kind of “open door” to HTML pages, allowing any visi- tor to click and edit the HTML content. Wiki is the abbreviation for WikiWiki- Web – “wiki wiki” is derived from Hawaiian and means “quick” or “quickly”. And the open authoring sys- restored at any time, should a page be MySQL, Oracle, or PostgreSQL. The soft- tem certainly is quick. The MoinMoin deleted or damaged by mistake. Also, ware then uses this data to create the Wiki engine is one of the better-known wikis allow you to assign special access public HTML pages. implementations of this technology. controls that can restrict editing to regis- Besides taking a look at the original Users can click to launch the embed- tered users, if required. wiki, you might like to visit what is cur- ded editor and access the content and The first wiki website was published rently the biggest wiki on the Web, the structure of the page they want to mod- by Ward Cunningham in 1995, and it is Wikipedia [3], which offers innumerable ify. Typically, an Edit link is provided to still online [1]. At the time, Cunningham articles on pages in multiple languages. make things easier. wrote an email message saying that he It is an example of how well information In contrast to “real” HTML, which had programmed a new kind of database can be organized with a wiki.
    [Show full text]
  • Developing a Web 2.0-Based System with User-Authored Content for Community Use and Teacher Education
    Education Tech Research Dev DOI 10.1007/s11423-009-9141-x RESEARCH Developing a Web 2.0-based system with user-authored content for community use and teacher education Lauren Cifuentes • Amy Sharp • Sanser Bulu • Mike Benz • Laura M. Stough Ó Association for Educational Communications and Technology 2009 Abstract We report on an investigation into the design, development, implementation, and evaluation of an informational and instructional Website in order to generate guide- lines for instructional designers of read/write Web environments. We describe the process of design and development research, the problem addressed, the theory-based solution, and the evaluation and testing of that solution. Based on our experience, we then identify sixteen guidelines for future designers and developers of read/write Web-based learning environments. The study demonstrates how read/write Web technologies can be used to address general problems that have intrinsic societal importance; examines implementation of a read/write technology in a real-life context, thereby testing distributed cognitions learning theory; informs the design of similar environments; and provides grounded theory for the design and development of read/write Web learning environments. Keywords Design and development research Á Read/write Web Á Web 2.0 Á Distributed cognitions Á Social constructivism The emergence of read/write Web (Web 2.0) technologies such as wikis, Weblogs, Real Simple Syndication, Webcasts, and interactive photo galleries, has empowered users to actively contribute to the content of the Internet. By 2003, 44% of adult Internet users had participated in the interactive capabilities of the Internet by posting in at least one read/ write Web environment (Lenhart et al.
    [Show full text]
  • Wikis in Libraries Matthew M
    Wikis in Libraries Matthew M. Bejune Wikis have recently been adopted to support a variety of a type of Web site that allows the visitors to add, collaborative activities within libraries. This article and remove, edit, and change some content, typically with­ out the need for registration. It also allows for linking its companion wiki, LibraryWikis (http://librarywikis. among any number of pages. This ease of interaction pbwiki.com/), seek to document the phenomenon of wikis and operation makes a wiki an effective tool for mass in libraries. This subject is considered within the frame- collaborative authoring. work of computer-supported cooperative work (CSCW). Wikis have been around since the mid­1990s, though it The author identified thirty-three library wikis and is only recently that they have become ubiquitous. In 1995, Ward Cunningham launched the first wiki, WikiWikiWeb developed a classification schema with four categories: (1) (http://c2.com/cgi/wiki), which is still active today, to collaboration among libraries (45.7 percent); (2) collabo- facilitate the exchange of ideas among computer program­ ration among library staff (31.4 percent); (3) collabora- mers (Wikipedia 2007b). The launch of WikiWikiWeb was tion among library staff and patrons (14.3 percent); and a departure from the existing model of Web communica­ tion ,where there was a clear divide between authors and (4) collaboration among patrons (8.6 percent). Examples readers. WikiWikiWeb elevated the status of readers, if of library wikis are presented within the article, as is a they so chose, to that of content writers and editors. This discussion for why wikis are primarily utilized within model proved popular, and the wiki technology used on categories I and II and not within categories III and IV.
    [Show full text]
  • Knowledge Management by Wikis
    Knowledge management by wikis Sander Spek [email protected] Institute for Knowledge and Agent Technology Universiteit Maastricht Abstract Wikis provide a new way of collaboration and knowledge sharing. Wikis are software that allows users to work collectively on a web-based knowledge base. Wikis are characterised by a sense of anarchism, collaboration, connectivity, organic development and self-healing, and they rely on trust. We list several concerns about applying wikis in professional organisation. After these concerns are met, wikis can provide a progessive, new knowledge sharing and collabora- tion tool. 1 Grassroots knowledge sharing During the last decades, the sharing of information and knowledge has gone through an unheard rapidisation. Both the amount of information shared, as well as the speed in which this happens, has taken a huge flight. In many fields of progress, professional organisations were more ad- vanced then ‘amateur knowledge sharers’. Remarkably, in some fields this has changed over the years. On the Internet, many succesful grassroots initiatives have popped up, that still didn’t make it to the somewhat static and controlled environment of professional business organisa- tions. Think of free-software projects, but also of free-information projects, as wikis, weblogs, and open news sites like Indymedia. (Möller, 2005) In this paper, we will examine on of the most popular and upcoming knowledge sharing enablers on the Internet: wikis. Consequently, we will discuss why wikis are not (yet) adequate for a professional environment, and what could be changed to have companies adapt the power of wiki-based knowledge sharing too. 2 Wikis Möller (2005, page vii, translated) defines wikis as “open websites that can be edited by every visitor.”1 We will extend this definition in two ways: (1) we explicitly state that modifying can also include deleting information, and (2) we mention the fact that a wiki is in fact a knowledge base.
    [Show full text]
  • Research Article Constrained Wiki: the Wikiway to Validating Content
    Hindawi Publishing Corporation Advances in Human-Computer Interaction Volume 2012, Article ID 893575, 19 pages doi:10.1155/2012/893575 Research Article Constrained Wiki: The WikiWay to Validating Content Angelo Di Iorio,1 Francesco Draicchio,1 Fabio Vitali,1 and Stefano Zacchiroli2 1 Department of Computer Science, University of Bologna, Mura Anteo Zamboni 7, 40127 Bologna, Italy 2 Universit´e Paris Diderot, Sorbonne Paris Cit´e, PPS, UMR 7126, CNRS, F-75205 Paris, France Correspondence should be addressed to Angelo Di Iorio, [email protected] Received 9 June 2011; Revised 20 December 2011; Accepted 3 January 2012 Academic Editor: Kerstin S. Eklundh Copyright © 2012 Angelo Di Iorio et al. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. The “WikiWay” is the open editing philosophy of wikis meant to foster open collaboration and continuous improvement of their content. Just like other online communities, wikis often introduce and enforce conventions, constraints, and rules for their content, but do so in a considerably softer way, expecting authors to deliver content that satisfies the conventions and the constraints, or, failing that, having volunteers of the community, the WikiGnomes, fix others’ content accordingly. Constrained wikis is our generic framework for wikis to implement validators of community-specific constraints and conventions that preserve the WikiWay and their open collaboration features. To this end, specific requirements need to be observed by validators and a specific software architecture can be used for their implementation, that is, as independent functions (implemented as internal modules or external services) used in a nonintrusive way.
    [Show full text]
  • Engineering Management Field Project
    Engineering Management Field Project The Interactive Knowledge Library: Capturing, Sharing and Synthesizing Tacit Knowledge in Engineering By Craig M. Eaton Fall Semester, 2006 An EMGT Field Project report submitted to the Engineering Management Program and the Faculty of the Graduate School of The University of Kansas in partial fulfillment of the requirements for the degree of Master’s of Science ____________________________ Charles Keller Committee Chairperson ____________________________ Craig Connell Committee Member ____________________________ Tim Wilcoxon Committee Member Date accepted:____________________________ Acknowledgements I wish to thank Ron Wood for the initial idea of looking into capturing knowledge for my project. Thanks to my sister Janette Savage for providing some useful references. Also thanks to Rich Perkins, Jan Sindt and Nitin Sanghi for the discussions on Knowledge Management. Most of all thanks to my committee, Chick Keller, Craig Connell and Tim Wilcoxon and particularly to Chick for introducing Wikis to me in a previous class. Last but not least thanks to my wife Lisa for the moral support and making me cups of rooibos tea while I worked on this. i Executive Summary The Interactive Knowledge Library is a place to capture, share and synthesize tacit and explicit knowledge. While explicit knowledge (or ‘know what’) is useful, it is tacit knowledge (or ‘know how’) that is the quintessence of knowledge, from which there is the most to be gained by sharing. The Interactive Knowledge Library provides a medium through which knowledge is expressed by enabling data and information to be set into context. A Wiki environment (e.g. www.wikipedia.org) is the best information technology solution currently available in order to enable the Interactive Knowledge Library concept.
    [Show full text]
  • Dokuwiki Download Windows
    Dokuwiki download windows DokuWiki on a Stick can be downloaded from the official DokuWiki download page. Just choose the option under “Include Web-Server”. Download DokuWiki! Here you can download the latest DokuWiki-Version. Either just MicroApache (Windows) Apache , PHP , GD2 and SQLite ​Install:upgrade · ​Upgrade · ​Hosting · ​DokuWiki Archived Downloads. To create an “on the Stick” edition of DokuWiki, visit and check the “MicroApache (Windows)” checkbox in the. DokuWiki is a great wiki engine with minimal requirements that usually gets Download the non- thread-safe version of PHP for Windows from. XAMPP is a popular WAMP stack for the Windows operating system. Download the DokuWiki zip file from (e.g. Bitnami native installers automate the setup of a Bitnami application stack on Windows, OS X or Linux. Each installer includes all of the software necessary to run. The Bitnami DokuWiki Stack provides a one-click install solution for DokuWiki. Download installers and virtual machines, or run your own DokuWiki server in the. Download the executable file for the Bitnami DokuWiki Stack from the Bitnami This tool is named on Windows and is located in the. How to install DokuWiki on Windows XP in less then 5 minutes: 1) Download and install WAMP5 (or the latest version) for Windows XP. How install DokuWiki on your server . Install DokuWiki on windows 7 localhost (XAMPP + php7. DokuWiki latest version: Free and User-Friendly Open-Source Information Storage Software. DokuWiki is Download DokuWiki for Windows. DokuWiki ist eine schlanke Wiki-Anwendung auf PHP-Basis, die ohne Datenbank auskommt und eingetragene Texte als TXT-Dateien ablegt.
    [Show full text]
  • WHY USE a WIKI? an Introduction to the Latest Online Publishing Format
    WHY USE A WIKI? An Introduction to the Latest Online Publishing Format A WebWorks.com White Paper Author: Alan J. Porter VP-Operations WebWorks.com a brand of Quadralay Corporation [email protected] WW_WP0309_WIKIpub © 2009 – Quadralay Corporation. All rights reserved. NOTE: Please feel free to redistribute this white paper to anyone you feel may benefit. If you would like an electronic copy for distribution, just send an e-mail to [email protected] CONTENTS Overview................................................................................................................................ 2 What is a Wiki? ...................................................................................................................... 2 Open Editing = Collaborative Authoring .................................................................................. 3 Wikis in More Detail................................................................................................................ 3 Wikis Are Everywhere ............................................................................................................ 4 Why Use a Wiki...................................................................................................................... 5 Getting People to Use Wikis ................................................................................................... 8 Populating the Wiki................................................................................................................. 9 WebWorks ePublisher and Wikis
    [Show full text]
  • Which Wiki for Which Uses
    Which wiki for which uses There are over 120 Wiki software available to set up a wiki plateform. Those listed below are the 13 more popular (by alphabetic order) wiki engines as listed on http://wikimatrix.org on the 16th of March 2012. The software license decides on what conditions a certain software may be used. Among other things, the software license decide conditions to run, study the code, modify the code and redistribute copies or modified copies of the software. Wiki software are available either hosted on a wiki farm or downloadable to be installed locally. Wiki software Reference Languages Wikifarm Technology Licence Main audience Additional notes name organization available available very frequently met in corporate environment. Arguably the most widely deployed wiki software in the entreprise market. A zero- Confluence Atlassian Java proprietary 11 confluence entreprise cost license program is available for non-profit organizations and open source projects aimed at small companies’ documentation needs. It works on plain DokuWiki several companies Php GPL2 50 small companies text files and thus needs no database. DrupalWiki Kontextwork.de Php GPL2+ 12 entreprise DrupalWiki is intended for enterprise use Entreprise wiki. Foswiki is a wiki + structured data + Foswiki community Perl GPL2 22 entreprise programmable pages education, public Wikimedia Php with backend MediaWiki is probably the best known wiki software as it is the MediaWiki GPLv2+ >300 wikia and many hostingservice, companies private Foundation and others database one used by Wikipedia. May support very large communities knowledge-based site MindTouchTCS MindTouch Inc. Php proprietary 26 SamePage partly opensource and partly proprietary extensions Jürgen Hermann & Python with flat tech savy MoinMoin GPL2 10+ ourproject.org Rather intended for small to middle size workgroup.
    [Show full text]