RSS
 

Archive for the ‘Wiki Specifics’ Category

digitisation wiki: content and structure

18 Sep

There are a whole bunch of different ways of structuring a Wiki. This came as something of a surprise to me when I first got involved with a Wiki, because I was used to Wikipediaon there, there is basically nominal structuring, in that it is sub-divided by language, but thereafter you just type a query into a search box and away you go.

When I started creating and contributing to a Wiki for another online community, I realised there was no way a relatively small group of users could create enough entries for a purely key-word search methodology to work; people wouldn’t know what to search for, and if they just typed anything in there might not be a corresponding entry (not a problem with Wikipedia, obviously, as there is an entry for pretty much anything and everything). So we had to create some kind of structure, by creating an entry for each letter of the alphabet and listing all the sub-entries that began with that letter, so people could see relatively what articles were available. We also drew attention to specific content with a ‘Featured Article’ section on the homepage, linking to a different entry each week.

I would not want to repeat the ‘alphabetical’ structure again, as it was basically rubbish. Far too limiting, not particularly reliable, and all but useless unless you already knew roughly what you were looking for. There was no real categorisation or themes for entries. So the Digitisation in HE Wiki needs to do better than that.

A Wiki homepage has to serve many functions. Obviously it anchors the entire site, so it needs to clearly brand the Wiki and outline its purpose. A more detailed explanation can created as a separate entry, because people judge whether they are going to stay on website based on less than 10 seconds’ skim-reading and they don’t want lengthy prose at this stage. As the legendary Jakob Nielsen says in this classic article

If a website is difficult to use, people leave. If the homepage fails to clearly state what a company offers and what users can do on the site, people leave. If users get lost on a website, they leave. If a website’s information is hard to read or doesn’t answer users’ key questions, they leave.

The homepage for this type of Wiki also needs instructions on how to sign up, how to join the community, and at least a link to a guide on creating and editing entries. And it needs to offer an indication of how the content is structured.

My intention with the Digitisation Wiki is to use a classic hierarchical parent-child relationship between subjects, with the Homepage at the very top, and then a small number of broader categories, all of which will subdivide into subjects (themselves able to sub-divide again as appropriate). I am, it must be reiterated, completely open to suggestion on this and indeed any other aspect of the Wiki. The goal is to end up with a resource fit for everyone’s purposes. But a rough outline might look something like this:   

(Example structure for the Wiki)

(Example structure for the Wiki)

Those bottom categories would splinter off in to as many different sub-sub-sections as people wanted. So the Homepage can provide links to each of the four (or how ever many we end up with) major themes, and from there you would find further links to the sub-categories, and then from there you’d find the list of articles relevant to that topic, case-studies, etc etc.

I would also like to build in some kind of Question & Answer platform, although I’m yet to look into how that could be done. But if people have queries not covered by the existing content of the Wiki at any given time, a Q&A section would be a good way to build the online community, and flag-up entries which it would be beneficial to create.

In the very long-term, if the Wiki expands beyond its original remit to include other types of digitisation beyond scanning from print (digitising various multimedia platforms such as audio, or images for archiving purposes, or slides, etc etc) then all the categories below the Homepage could move down one, and the new meta-categories could be slotted in.

[Incidentally, a great example of a successful and well-structured Wiki, is the Library Success wiki, created by the ever-resourceful Meredith Farkas.]  

I’d be interested in your views on all of this, even if you’re an Information Professional with no connection to digitisation but who does use or have experience with Wikis. Let me know what you think.

- thewikiman

{lang: 'en-GB'}
Print Friendly
 
 

wiki-software and wiki-hosting

20 Aug

Back to the Wiki theme for this post, after a couple of diversions.

There are a massive amount of options for creating a Wiki, the two most important being the software and the hosting. If you have a practical background in MySQL or PHP then you can do this stuff yourself, but for the rest of there are wiki hosts and wiki software.

Wiki Software

Wiki-hosting sites will offer some kind of software built in. So the question of which host to choose is bound up with the question of which software you want; obviously you need to know which of those your priority is and act accordingly. For the purposes of the Best Practice Wiki it is, of course, a bit of both – I want software that is friendly enough to use so people aren’t put off from contributing, but I also want decent hosting which won’t suddenly disappear, or bombard users with adverts.

Anyone who has ever contributed to a Wiki will know how important the software is. We’re used to having both simple and complicated instructions acted upon by word-processing programmes etc, with the minimum of fuss. It is unbelievably annoying if you are trying to edit or contribute to a Wiki and the software is anything less than intuitive.

An important feature for many users is WYSIWYG – which means What You See Is What You Get editing (we’re encouraged to pronounce this ‘wiziwig’ but I just can’t bring myself to do so). As you can guess, this basically means anything where the end result looks exactly the same or at least very similar to how it looks when you are editing it. Absolutely loads of wiki-software offers WYSIWYG editing, so you’d need a really good reason to go with another type where pages looked significantly different when being edited to when they’re live.

I’ve used MediaWiki for another Wiki in the past, and found it fantastic to use – better than any other software I’ve encountered. It is clean, simple and intuitive, and I’ve set up a test Wiki as a precursor to the Best Practice Wiki which has convinced me that it’s easy to set access controls and so on. Anyone who has ever edited Wikipedia will be familiar with it as it is what the great Wiki behemoth itself uses (although Wikipedia has been in the news recently as apparently less and less casual users are seeing their edits endure, as a kind of editing aristocracy is taking over and rather going against the ‘everyone can contribute’ ethos on which it is founded). MediaWiki is the daddy, and it is the software I’d like to use for the Best Practice Wiki. It is also free, and Open Source - you can pay hundreds of pounds or dollars a month to use some Wiki-creation software.

You can view a comparison of Wiki Software on Wikipedia for more information, although be aware that, due to its inherent Wiki-ish nature, it is open to a certain amount of abuse from firms basically advertising their own software by editing the entries.

Wiki Hosting

As I’ve made my decision with the software as the main driver, I now have to find a wiki-host that supports MediaWiki. I could try and get some server space at the University of Leeds (where I work) but after talking it over with our head of e-Strategy, Bo Middleton, we’ve decided against this. She’s not keen because the only Wiki’s hosted at Leeds are very limited-user and aimed at just in-house use, and I’m not keen because I don’t want the Best Practice Wiki to be affiliated with any one institution. It isn’t a ‘Leeds’ Wiki, and everyone should be encouraged to contribute to it.

I’ve heard great things about WetPaint, which I know offers WYSIWYG editing and other HEIs have used it successfully for Wikis, but as it doesn’t offer MediaWiki I’ve ruled it out. Similarly, Peanut Butter Wiki (better known as PBWorks) is extremely highly regarded as a host, and offers excellent Wiki software too. But it also offers both free and paid-for hosting, and I’m always wary of that – things which may start off free could potentially move to the paid-for packages later if they need to boost revenue once they’ve hooked you in. And most importantly to me, it doesn’t offer MediaWiki. In order for this Wiki to work, people have to be comfortable creating and editing content, and for me the best way to ensure this is to use the most fool-proof and instinctive software.

There are paid for hosts, advertising-supported hosts, and just completely free hosts. An example of a completely free host is Wiki Spot, which offer free wikis for non-profit ventures and communities with no advertising at all. This seems ideal, but their example Wiki’s look unattractive and pretty dated, so I’m wary of the software. The options left are to pay, which I’m unwilling to do, or put up with advertising, which is a necessary compromise. However after an exhaustive comparisons of all the different hosting companies, I’ve found one where the adverts are minimal and won’t disrupt use. I’ve opted for is wikkii.com. It is free, it offer MediaWiki software, and their revenues come from very minimal advertising. On the test version I set up, small adverts sometimes appear down the right hand side of the page, and it’s very unobtrusive. It also has unlimited disc-space and unlimited bandwidth, which could prove absolutely crucial if the Best Practice Wiki takes off. The URL of the Best Practice Wiki would be whatever we choose to call it, then .wikkii.com. So for example, http://digi.wikkii.com.

[There is a comparison of Wiki Farms available via Wikipedia, but it doesn't look very reliable and is heavily flagged as having 'disputed partiality' etc. A better place to go is wikibooks.org - see this comparison guide for free and paid-for Wiki hosting.]

What do you think?

This blog serves as a sort of guide for anyone thinking of doing a similar thing (I’m doing the homework so you don’t have to…) but also a sounding board – do you agree with the choices I’ve made above? Do you have experience with other hosting sites you think could do a better job, or do you feel I should do everything possible to avoid any kind of advertising?

I’d love to hear what you think, so leave me a comment and we can get some discussion going. Nothing is set in stone yet, so you may even change my mind!

- thewikiman

EDIT (15/09/09): Since writing this post, I’ve discovered WikiMatrix which is an absolutely brilliant resource; a thoroughly comprehensive comparison of all wiki options. If you’re planning on starting a Wiki, go there first to find the right option for you…

 

{lang: 'en-GB'}
Print Friendly