Tag Archives: coop

MediaWiki

Converting Documents into Wiki Pages

In addition to an overall organizational structure, a wiki also should have some organization within its individual pages. The use of headings, subheadings, bold, bullet points, and the like make an individual article or page easier to scan, navigate, and read. Most of the internal page organization can be easily accomplished through the use of formatting and Wiki Markup. However, a problem that I’ve noticed is that a lot of users do not write their content directly in the UBC Wiki; instead they most likely use a word processor to draft and format their text and then copy and paste that text into the wiki. Unfortunately, word processor formatting does not often transfer well into MediaWiki. Thus, the user has to take additional time to reformat their content on the wiki. Often, though, they just leave their content as is, which can look pretty bad and be hard to parse.

I wanted to quickly point out a couple of tools make getting content from a document into wiki page a bit smoother. The first is an extension for Open Office, the free, open-source word processor program which is a pretty great alternative to MS Word. The Sun Wiki Publisher extension allows a person to type up a document in Open Office just as they would normally, and then save it in a MediaWiki format. All formatting, such as links, bullet points, and headers, is automatically converted to Wiki Markup. In my basic testing, this extension works really well and can handle even moderately complex tables.

I have yet to find anything that works as well for Microsoft Word. The easiest strategy seems to be to save the document as an HTML file and then to copy and past the HTML into an online Wiki Syntax converter and then copy and paste that output into the wiki. Novak recently recommended this HTML to Wiki converter and it works well, especially if you are using HTML directly from a website (which is how this UBC Wiki page was created). Unfortunately, when converting from Word to HTML to Wiki Mark-Up, the process is not quite as smooth and some reformatting or tweaking of the Wiki Markup seems to be necessary. Still, its better than having to create a table from scratch or insert a ton of links into a list.

I’ve created a couple of Help pages on these topics: Converting Documents to Wiki Syntax and Converting HTML to Wiki Syntax.

Update:: Brian points out in the comments saving a Word document into HTML and then converting it doesn’t work all that well. I agree and I’ll keep looking for better solution.

Standard
UBC Wiki

Quick Thoughts About Purpose & Community

I’ve been thinking a lot about the purpose of the UBC Wiki. Wikipedia has a pretty narrowly defined purpose: it is an encyclopedia. Only content that fits with their mission of being an encyclopedia is allowed to remain.  Inherit in that mission is the idea that an encyclopedia is read by a lot of people and that any content will be read and edited by larger community. This purpose provides Wikipedia with a focus which helps it to be organized and to grow.

So, what is the purpose of the UBC Wiki? According to the masthead, the UBC Wiki is a space for use by students, staff, and faculty for whatever purpose, whether it be teaching and learning, research, or community engagement. The UBC Wiki has, by design, a pretty unfocused definition that doesn’t limit how people can use the site.  Thus some people use it as an individual work space and some use it as a community resource for knowledge sharing.

The advantages of using the wiki as an individual space is that people can use the wiki pretty much how they want, it is clearly filling a need, and the wiki is a great tool for group collaboration. The disadvantage, however, is that people tend to get frustrated when when content they see as “theirs” gets renamed or edited and this might cause them to never use the wiki again. Likewise, people might be hesitant to edit or add to content that they think of as “yours”.

As a community resource, the wiki has the potential to really facilitate knowledge sharing across the departmental, faculty, and other boundaries that all universities have. However, in order to for the wiki to be a community resource, information on the wiki must be accessible. This means not only does the info need to be somewhat organized but also there needs to be a change in how people are thinking about the wiki: yes, it can be a personal work space but it is also a community shared space.

I think the UBC Wiki can work both as an individual tool and as a community resource. The different namespaces allow the UBC Wiki to serve both purposes. However, I think for the namespaces to work, users need to have a better understanding of both purposes.

I guess this is all a long way of explaining that the I changed the wording in the masthead from saying that the UBC Wiki is a space to saying that it is a shared space.

Standard
UBC Wiki

Wayfinding on the Wiki

Wayfinding, as Wikipedia succinctly summarizes it, refers to the user experience of orientation and choosing a path within the built environment and to the set of architectural and/or design elements that aid in that orientation. While signage is an important aspect of wayfinding, wayfinding principles should also be part of the structure of an environment, whether that environment is informational or physical. A classic, if not somewhat simplified example of wayfinding in the real world, is when hospitals colour code their separate wards, so that pediatrics might have blue walls while neurology has green. A person visiting the pediatric ward who turns a corner and finds themselves in a green hall should intuitively understand that they have gone the wrong way.

One of the clear issues on the UBC Wiki is that users do not necessarily grasp that there are separate namespaces for different types of content and thus get “lost” when adding new pages. To try make this structural division more intuitive, wayfinding tools can be built into the site structure. One easy method is to follow the hospital example and do a slight bit of colour coding. To this end, on the main page of the wiki, I took the text description of the different namespaces and put them into coloured boxes:

I then repeated the colours on the homepages for the Course and Documentation spaces to reinforce the idea that, just like different wards in the hospital, these are different areas with slightly different purposes.  I don’t think too much colour is necessary, but a little might help users understand the site better.

I’ve also begun experimenting with how “signage” can be used on the wiki.  For example, I’ve begun putting book icons on pages related to Wiki Books.  Right now I two different versions – A small, relatively unobtrusive sign:

And a larger banner that stretches across the page (reduced in size here to make it fit on the blog):

I think that both signs call attention to the book creator and help users find it better than just a link would.  It is my hope that by including wayfinding elements into the UBC Wiki, users have a better understanding of both the structure of the wiki and some of its features.

Standard
UBC Wiki

General Thoughts on Correcting the Course: Conundrum

Here are some preliminary thoughts on correcting what I have begun calling the Course: Conundrum (the creation of course specific pages in the main space of the wiki instead of into the Course namespace).

In general, I really like the Course namespace. Organizing course pages via the namespace gives the wiki some structure while nicely incorporating the course information into the overall UBC Wiki knowledge base.  For example, a course such as Econ101 could be included into the category of Economics, thus allowing users to discover a broad range of information and partake in knowledge sharing about economics at UBC (and this type of organization ties in nicely with the concept of open education).  

The course namespace keeps the wiki “neater” by providing it with some organizational structure: a page entitled “Assignments” on the main space of the wiki would be assumed to be a general information article; in the course space, it would indicate assignments related to a specific course. 

However, as I might have mentioned, users are not using the Course namespace.

So far, I see three obvious solutions to organizing course material on the UBC Wiki:

  • Educate the users on how to organize their course pages on the Course namespace through better documentation, tutorials, and direct communication
  • Scrap the Course namespace and allow users to organize their course material on the main space of the Wiki as they see fit
  • Remove course work from the UBC Wiki altogether; provide independent installations of mediawiki for each class or instructor who requests it

Here are some quick thoughts on the above options.

Option #1 – Education

I do not believe the reluctance to use the Course namespace is due to users not wanting to use it. Instead, it’s because:

  1. They don’t know about the Course space
  2. They don’t know how to put things into the Course space
  3. It takes more effort

Education is the key to overcoming all three of these barriers.  Better documentation and tutorials would explain to users just what the space is for and how to use it (and that it really isn’t much more effort).

To date, I’ve been focusing on this option.  For example, I’ve better organized the Course space homepage and I’ve creating help pages such as How to Use the UBC Wiki for Course Work.  Another form of education that I’ve started doing is dropping people notes on their user talk pages about why we moved their page to the course space and pointing them to the new documentation.

In the near future, I hope to make some screencasts demonstrating things like how to move pages to the course space or how to use subpages. Clarifying the purposes of the separate namespaces on the wiki homepage is also something I hope to get done soon. I think time will quickly tell if this method is working.

Option #2 – Scrapping the Course Space

Could we get rid of the Course namespace altogether? Wikipedia, rather famously, doesn’t use many namespaces for their content. Instead, the try to keep their organizational hierarchy as flat as possible by having their main content organized only through the use of specific and precise article titles. The UBC Wiki could go this route as well. For example, instead of having a course organized into the course space (such as “Course:Econ101”), it could just go into the main space (such as “Econ101”). Additional course sub pages could just be added with specific titles (“Econ101 Assignments” instead of “Course:Econ101/Assignments”). The health librarianship wik is organized this way as well. Here’s an example of how they have organized a course page.  Notice that related course pages are not necessarily organized as subpages.

The advantages of this type of organization, I suspect, is that it is easier for users to grasp.  It makes more sense to create a course page called “Econ101” and “Econ101 Assignments” than it does to organize these pages into namespaces and subpages. The disadvantages, I suspect, is that the flat hierarchy has less structure and in a large multi-purpose, multi-user wiki, like the UBC Wiki may one day be, things could get messy fast.  For example, what is the current UBC Wiki page on the Report Card about?  What is the context of the information on that page? Namespaces and subpages force structure and organization on content and thus make information easier to understand and access.

I think a flat hierarchy could work.  However, at this time I think it would require as much educational efforts and the moving/renaming of pages as using a namespace.

Option #3 – Independent Wikis for Course

Rather than have course pages on the UBC Wiki, individual wikis could be created for each course (as requested by instructors).  This would give instructors much more control over their course pages but at the loss of greater knowledge sharing and open education. I don’t really have much to say on this topic other than to note that some places are doing it this way. For example, here’s Stanford University’s MediaWiki web service page and here’s the Simmon College library school’s MediaWiki request page.

Standard
UBC Wiki

Categorization Manipulation

One of the main tools to organize a wiki is categories. Mark Choate, in his book Professional Wikis, describes adding categories to a wiki article as a parallel to adding tags to a blog article or a photo: tags and categories are “both keywords that are used to describe or group a page into some conceptual category or topic”. The advantage of using categories as a type of folksonomy, Choate states, is that one user might categorize an article one way while a another chooses an entirely different approach. Thus, when many people add pages to a category, different points a view are represented by the links and someone reading the wiki may discover connections between topics that they might not have thought of themselves.

Unfortunately, the current state of the UBC Wiki is that users are not currently adding categories to their pages. The majority of pages in the UBC Wiki (before this Gardening Project began) had no categories or links to other pages in the wiki. Thus, each article was isolated, even if there were other articles on related topics.

I’ve begun adding some basic categories to articles that currently exist on the wiki. Some nice examples of how useful a categories might be can be found in the Economics and Physics categories. In each category, you can find specific topics as well as pages on some courses, student groups, and departments.

It is my hope that as key categories become more built out, users will become more familiar with the concept, recognize the usefulness of categories, and begin adding categories themselves.

Standard