ResumenMarieke

[|Tags en Del.icio.us de la autora] La autora realiza una valoración de la implantación real de los wikis en el sector público (edicación y bibliotecas) y de si existe una posibilidad de equilibrio entre la calidad que deben ofrecer los sitios de Internet público y las características de los wikis Digital natives have arrived to University and some of them are even already teachers. All Web 2.0 apps are mainstream. But, is there a balance between quality and the openness of these technologies? Are we already on the way? There is a new move in the wiki field with a wide range of software available, specific search engines, comparative tools as Wikimatrix or "specific wikipedias" for travel, medical topics... A Google search matches quite a lot hits of wikis but a closer look reveals that there is not too much activity in them. However, it's also true that there may be much more wiki action buried down in the Internet hastack in access-restricted sites. Anyway, we are not in the wiki revolution. The article offers a list of wiki sites by topics: The question is to know if a wiki is successful if many people read it or if there is a lot of contributors. A good perspective is to think that a tool is working correctly if it if it reaches the objectives that it's intended for. Therefore, collaboration can be only a strategy and not a goal. And it's maybe not necessary that everybody edit the content. Remains one question: does a wiki have a single vision (not in the article) a cooperative vision or a genuine collaborative vision. The main question: why, if wikis are a good collaboration tool, they are not used? There is enough open source solutions to make interesting to go on proprietary (maybe this is not so true if we want really WYSIWYG products). The questions are to decide if we put on our servers or use an external service, decide on permissions, URL, security issues... After this, a small team has to set the first look and select the features needed. Second step, to add some tutorials and some content, an index at least: there's nothing more discouraging for potential contributors than an empty wiki. Third, try to coach an small team to contribute. It's important to think on the possibilities on migrating some time after and the impact on users who have to learn a new system. Some wikis don't have a HTML editor and learning the wikisyntax is not easy for everybody. The wikiconcept has still a way until it reaches the level of regular computer users. Some organisational concerns: On top of all this problem, the main one remain to get collaboration. The notion of property is still very strong, people associate web pages with their creators. The 1% rule states that there is not that much active users. Wiki uses for e-learning The possibilities of wikis match with the current pedagogical thinking that advocates active learning and asserts that learning is inherently social. Wikis can be used to: Power has to be handed to the students. There can be tensions using wikis between [|An open wikibook on Using wikis on education] The key factor for the success of a wiki is the community. Before launching a wiki it is necessary to think if the community wants to converse, or is able to converse offline. After this it will be necessary to support and encourage them.
 * Wiki or won't he (Marieke Guy on Ariadne November 2006)**
 * Public Sector Wikis: Not very public?**
 * **Voluntary and government sites**: There are some examples of healthy wikis led by volunteers and another one only supported by a person. Government led wikis seem to be not really running
 * **Library wikis**: Some interesting experiences in the States, and some resource sites too like the [|Library Success].
 * Higher and Further Education Wikis: [|OSS Watch wiki] is a resource where the input comes from the the organization, although it has been an interesting community building tool. Same for [|DigRepWiki], a wiki of JISC on Digital Repositories. There is some other examples of Wikis with information about universities. Other two examples are used as opencourseware tools and have an important community behind.
 * Wikis and quality**
 * Some considerations for the launching**
 * Barriers for the use of wikis**
 * Cultural barriers**
 * Giving control may be seen as threatening by organisations
 * Problems of non-identification of the organization with the user's contribution
 * Copyright and IPR issues
 * Human resources for training, support, moderation
 * Vandalism (human or spam) and the system of moderation: some people is responsible or the community. In the former, the wiki can give means to the users to alert the moderators
 * Wiki cases studies**
 * **Interoperability focus community wiki**: 1)to think first if the audience is ready 2)to select right the features 3)to try to add some tags and sindication features 4) the main conclusion: a wiki needs a mid-wife, a champion and a minder (a hard work if you have only a small amount of one person's time available).
 * **Web Dev**: an example of an internal wiki. Main lesson, unless there is somebody that champion it, it will never work. But if the thing runs, it runs very well
 * work on collective writing
 * as a tool for making presentations
 * as shared repository of resources
 * the individual and the group
 * people creating the wiki and people using it
 * teachers and learners
 * Conclusions**