After spending a little time yesterday trying to add links to my weblinks directory and then filing them under my Drupal book pages, I think it's time to start using a wiki. After using the IAWiki and an AIfIA wiki over the past few years, I decided about a year ago to get my organization using a wiki for our internal staff documentation. I've been finding it so much easier to do simple dashing off notes in a wiki, but I also find them pretty good for more complex documents such as for product requirements gathering, meeting notes, etc. I really like Drupal's book module -- it integrates so well with the other node types -- but, I find that it just requires too many steps to for me utilize it well. I found myself spending time creating book pages to organize my topics, then inputting a lot of metadata into the weblink or blog entries to make them findable in the index, then finally "administering"
each node to attach it to a book page. Way too many steps for me to work effectively.
I had seen a few posts on Drupal.org about wiki modules in the past year, but none of them seem to be producing a wiki module that allows you to use WikiWords or some similar method to produce new nodes. So I attempted to use the book module instead for my PKM. After attempting for a while to bring together a lot of loose ends in my KM notebook, I've decided to abandon it and go build it in a wiki. I'm going to be using PHP Wiki PmWiki. I don't think this means I'll be forgoing using my weblinks module (the thing that produces the "recent links" on my homepage), but I will be doing more organizing rather than stream of consciousness posting on the wiki. We'll see how this experiment goes.
P.S. A few people have suggested desktop wiki clients. I've tried both am very impressed by them as early version software. Perhaps the best feature offered by these desktop clients is Exporting.
* Mac: VoodooPad
* Windows: WikidPad
Comments
03/18/04 @ 20:12
See my comments
03/18/04 @ 20:49
See my response there too. :)
03/19/04 @ 13:28
And another one.
03/19/04 @ 14:38
These comments referring to comments are quite strange. Oh, and I don't have trackback working here because I'm running 4.3.2 and am waiting to update to 4.4 before I install it.
03/19/04 @ 20:38
I've been using a wiki on my laptop running at localhost to take notes for work. It's really useful when I'm starting a new project and I haven't a clue what's going on yet. I can't make the connections so early on so I sort of let the wiki do it for me. It works well. I'm dealing with being in a new environment with a lot of strange acronyms being thrown at me. Just having a wiki to keep up with those is useful.
03/19/04 @ 23:35
I agree completely, Tanya. After using a wiki for the AIfIA documentation I got convinced that it was the easiest way to keep track of project notes, so I ported all of my organization's project documentation to it, with hopes that everyone would maintain/update their own docs. I was previously responsible for maintaining all of our groups project documents, and we didn't use a publishing system for it. I toyed around with using a light publishing system, but found that if I evangelized and gave enough tutorials, people would see the benefit in keeping their own documents up to date. Two years later and the people in my organization using the StaffWiki use/update it more on a weekly basis than I do.
So I'm loving Wikis for project work. But what I'm struggling with now is how best to keep my notes for stuff that I'm exploring, learning about, and still forming ideas around. I tend to keep my papers/presentations organized in outlines -- noting the key points I want to make and filling in. So I'm wondering if the NetNewswire/OmniOutliner approach will work for my notetaking and for incubating the new ideas.
03/23/04 @ 09:42
I have started down a similar path, but am using VooDooPad for Mac. I am only a few days into this endeavor, but it seems to be doing the trick for me. I have been frustrated with file structured systems and needed metadata for files as well as a means to group ideas and link to files in these groupings. The VooDooPad is allowing me to do this. This can be exported to HTML, but I am not so sure I want to do this.
03/23/04 @ 11:11
Thanks, Thomas. I'm going to try it out. Looks very simple to use and better integrated with my way of working: dashing off notes, dragging and dropping stuff into an app. I'm hoping this will work well with NetNewswire as well. Makes me want to consider having a PowerBook again, but I shudder at the thought of having to carry around my ThinkPad and a PowerBook. That's why I thought a wiki on a public server would be the best option initially.
Your frustration with having to organize your notes is exactly what I've been groaning about. The problem with my Drupal blog/weblink/notebook structure is that while some classification can be done at the point of entry, I often need to reorganize after the fact. The tools to do this are decent, but don't make for quick and easy shifting of nodes (blog entries/links) into piles. This is why I liked the idea of a wiki or OmniOutliner or something. This is making me think a little of hypercard. What I'm doing really, is what I do at my desk -- sorting stuff into temporary piles before I solidify my thoughts in a notebook. But the advantage of using a blog for this recording/organizing of thoughts is that it it becomes hidden and prevents my learning in a social context where people find and comment on what I've written. I've been thinking about writing about this and may do a longer blog entry related to this.
03/24/04 @ 12:03
I installed and tried VooDooPad last night. Was actually quite simple to use once I stoped the links from opening new windows so it functioned more like a web browser. It looks like a very nice application and includes some great exporting features: Word, HTML, RTFD, XML. The XML option looks particularly intersting to me as it would provide a means for flowing into other applications as preparation for such things as presentation or paper writing.
I found this tool did not do a lot of the things I wanted it to do. It is an early release, however, so I'm going to keep coming back to see what features get added. Particularly of interest to me is a better way to modify the templates for created pages. You can modify the default text that appears, but it would be nice, for instance, to be able to provide a footer, change the font and style of the header, etc. A simple GUI for selecting stylesheet elements would be a good improvement as well. I don't want to have to use a font menu for specifying things such as headings. And at a broarder level, using a desktop application means that I have to have access to the single machine running VooDooPad. I'm often not in one place and I no longer have a PowerBook, so what do I do when I'm using my IBM ThinkPad at the office and need to jot down some notes. There's always paper I suppose.
I'll be looking for the next releases to see how this improves. For now, I'm still trying to use a wiki.
05/28/04 @ 15:33
TrackBack from Brilliant Corners:
05/29/04 @ 09:24
I've been using a Wiki for general notetaking (and todo lists!) for around 6 months now, I find it incredibly useful. Runs on a local server.
My original plan was to build in a load of RDF-based facilities for more effective knowledge management (it's home-baked code), but I haven't had time to make anything useful. I rigged it up so that the data is maintained as plain text files, so it'd be easy enough to move it somewhere else if I wanted (my aim is to have it persisted as XHTML, but that's another story ;-)
It also lacks a decent way of recording links. Neither really matters though - it's very, very quick to make notes and look things up.
---
Raw : http://dannyayers.com
06/05/04 @ 01:31
I'm curious how you decided on which wiki package to use, or what went into your decision-making.
I've used PHPWiki for a number of projects in the past and have experimented with PmWiki and (the somewhat bewildering) TikiWiki.
What brought you to PmWiki over the others?
06/07/04 @ 12:18
I think it may have been the configurability of PmWiki themes or something. Don't remember exactly what all the reasons were. I also liked not having to use up a MySQL database for the wiki.
06/22/04 @ 14:56
TrackBack from Business Logs:
Post new comment