The tools and methods discussions are still ongoing on our workshop moodle platform. Here is a summary of some of the tools discussions that participants and facilitators initiated:
- What makes the Peer Assist a KS method? asks Michael.
- Two references have been shared so far: An explanatory video: http://in.youtube.com/watch?v=ObmQyW3EiiE and two stories from our KS blog: https://ictkm.wordpress.com/?s=peer+assist
Tags / Tagging
Michael gives a really nice introduction to the topic:
- A tag is a keyword or term that is given to a bit of information (a bookmark, an image, a blog entry, etc.) in order to help find it later and also to associate it with other, similar or related bits of information.
- Many of the web2.0 tools we are discussing in our workshop make use of tags. Indeed it is because of these tools that tagging has become popular and widely used.
- Tags are chosen by the individual at the time they are put into use. They are more flexible than the formal metadata and can sometimes be used as leading indicators of new concepts. However, they can also be somewhat inconsistent and lack the relationship specification of defined taxonomies.
- When many users have tagged many items within an application or around a set of items, this collection of tags becomes what is called a folksonomy (i.e. an informal taxonomy generated by the people or “by the folks”).
- Explanatory video in relation to Social Bookmarking at: http://in.youtube.com/watch?v=x66lV7GOcNU&feature=user by Common Craft
- Social Reporting is the practice of capturing and sharing the learning that happen at F2F events online for the group and possibly others not at the F2F. Nancy launched this topic as a way to suggest some practice in this area during the f2f meeting in Rome.
- Here are some tools used for social reporting: wikis to take life notes from sessions and document them; online photo galleries like Flickr to upload each day visuals of the event; Live blogging to capture impressions or results of a session; video interviews to give a voice to participants and tell their own story and perspectives on the event, a topic or a session.
- Resources: http://partnerships.typepad.com/civic/2006/10/social_media_so.html; http://socialreporter.com/ ; http://www.eudaimonia.pt/btsite/content/view/115/32/
- Jo launched this thread with the question: Can anybody share stories about success and frustration on different discussion group interfaces? Which interface and provider to choose from for best result for all participants having and “equal position” in the group and possibility to manage email to customize involvement?
- Jo took the lead to explore some of the suggested options: Yahoo groups, Google groups, Dgroups, Ning, Drupal. And it seems he really liked our Ning community that we set up in order to allow us exploration and perhaps the creation of a longer lasting bond between various workshop editions. http://ksworkshop.ning.com/
- Some of Jo’s findings: The interface is centered on the members; its a free public discussion group interface, and we get topic-related advertisements in the right-hand column of the site through Google ads; Ning group members can customize their own page to make it look different from the rest; When you ask to become “friends” with another member, you get faster access to their personal pages and blogs
- Cristina mentioned her experience with Dgroups and her move to a restricted blog on her new Drupal site, because of the complaints by her team and stakholders about the Dgroup email overload. Her challenge now: “stimulating people to visit the website and comment on the issues raised.”
Blogs and Blogging
I started a discussion on blogs:
- Nancy points to examples of blogs in development work with her delicious tag, devblogs
- Different uses of blogs. Chronological ordered and News based website for project reporting and communication (important to use tags to distinguish different aspects of the project or authors)
- When do blogs work well. Nancy shared a post from Pete Cranston to the KM4Dev community: be personal, less obviously institutional, update regularly, acknolwedeg that spending time on communicating your perspectives is valuable, have a group of bloggers for organizational blogs, be open, don’t control. “Blogs work when they are constructed and maintained so that they become part of the blogosphere, get linked to – and link to others – and generally have access to audience. Blogs designed for a bounded audience have a much harder time.” Blogs are also a welcome alternative to progress or back-to-office reports, or for specialist groupings that focus around meetings, or issues.
- Blogs versus discussion groups: Blogs are not tools for team communication. They can’t really replace email.
A wiki is a web site that allows users to add, remove, and otherwise edit and change content. At its core, a wiki is a simple online database in which each page is easily edited by any user with a Web browser
- Wikis are really rather flexible … not just as a shared document writing/editing tool, but they can be used as an entire website platform (with pages open for editing or not), as a growing knowledge base, like Wikipedia and the KS Toolkit, or even as a simple intranet. There are commercial wiki packages now that are pitched that way.
- Obstacles to broad wiki use: All members can overwrite; no track changes directly visible. Publishing of “unfinished material” => cultural shift. Needs accountability, rewarding and facilitation.
- Kay compares a wiki with her actual sharpoint application and finds it friendlier, easier, quicker
- Public / private: When do I need to make that choice? Options: open to all for viewing and editing (be aware of spam problems if you use this option); open for all to view but membership request for editing (ex: our KS Toolkit); membership request for viewing and editing (if you need a confidential space for groupwork, i.e. before publishing)
- Nancy shares some lessons learnt while doing wiki training session: Use any training opportunity to also build relationships; make sure there is hands on practice/use – don’t just talk about it; create a short “how to” document to send in advance with screen shots – but keep it simple; don’t over describe all the features the first time.
- Should we use a platform “one package solution” or should we integrate bits and pieces?
- Pete thinks that “there is no all-in-one package out there and even if such a platform existed to meet our staff needs today, this certainly is no guarantee that it will meet all of our needs tomorrow.” I think this is an important lesson for working with Open Source software as well as within the context of Web 2.0. At the end of the day, it’s all about interoperability and integration of services. If you have a system that can produce RSS and uses tags, then that content can be easily shared on other pages within your intranet. “Sharability” is a key feature.
- There is a group of intranet curios participants of this thread who meets a group of skeptical ones: No one really has an example of a successful intranet site; I am asking; How much information is there really besides financial and project management information that need to be closed and internally only? Or: “I’m also cynical enough to believe that some prefer to keep information on the intranet because there it is not likely to be questioned or challenged by “outsiders”.
Other KS methods and tools that have been suggested / discussed:
• Online collaboration
• Language translation technologies
• Participatory Impact Pathways
• River of Life % samoan Circle
• Twitter. Many set up an account and we are nor following each other 😉
• Joomla- a CMS tool for Websites