• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Stop wasting time looking for files and revisions. Connect your Gmail, DriveDropbox, and Slack accounts and in less than 2 minutes, Dokkio will automatically organize all your file attachments. Learn more and claim your free account.


Group 6: Dimensions

Page history last edited by pcampbell708@... 11 years, 6 months ago

return to Group 6 Main




The following image from MindMeister identifies the principle dimensions that are important for the group's use cases.  The top three dimensions are Domain, Purpose, and Security.





 Protects the users by:

  1. Authentication using password against unauthorized posts or document updates. The users are provided with secured log in, so the right users have access to critical information and can make the right modifications.

  2. Access Control List. The users are provided with Access Control List feature which allows the user to create a lists of users to access some parts in his/her wiki page such as viewing, editing, and creating new pages, etc.

  3. Blacklist. The users are provided with a Blacklist feature. This feature allows the user to create a list of URLs that are noted to be spam. So no one can add these URLs to wiki pages.

  4. CAPTCHA. The wiki site has a CAPTCHA feature which is an image that has distorted letters and numbers. The user can not save any wiki page until s/he writes these letters and numbers. This feature will prevent the Automatic Spam Bot from spamming the wiki.

  5. Secure Sockets Layer Encryption. Prevents hackers from being able to capture and view information as it passes through the Internet.

  6. Delayed Indexing. With this feature, when someone wants to make search using a search engine, the results of his/her search will not include wiki pages that just been lately edited. This feature aims to prevent spamming.

  7. Host Blocking. To prevent hackers from accessing a wiki page. The user can block any IP to not access his/her wiki page.






Domain (Internal or External wiki):


Wikiʼs domain is not limited; it could be extended depending on the underlying needs that trigger adopting such tool as a collaboration media. For internal collaboration and communication within an organization, setting up an Internal Wiki would be a big advantage to it, where it offers a unique environment for synthesis of ideas and thoughts among the employees; also it could serve as a company intranet through which the corporate documents could be published in one accessible location, and meeting notes and agendas could be organized, as well it could be used as a project management tool. Nevertheless, itʼs possible to move beyond the organization boundaries into the web, External Wikis are open to the public, where web users can modify, add insights into wiki pages, or they only can view and read these pages.  


For internal wikis, it would be easier to manage and secure the site through company standards and policies, unlike external wikis, where there should be a greater consideration for inaccuracies or misleading changes, especially from users outside the organization, in such cases additional security features have to be added to protect the site content and enhance the safety, and this might pose an extra cost.


Irrespective of the wiki domain, Wiki sites could be constructed at any number of levels, for small and large groups.     



Purpose of the Knowledge Repository: 


The purpose of an organization's repository will dictate the importance of many other sub dimensions.  If its primary purpose is to publish relatively static knowledge from disparate areas or individuals within the organization, then content organization features will be high priority.  If the knowledge to be shared is strictly operational documents such as procedures, standards, training material, then the domain of the repository tool and the associated security would be confined to the organization’s intranet.  Static information could also be published on the internet.  This would introduce additional security requirements, but editing capabilities could still be restricted to users within the organization.


But if the repository's primary purpose is to facilitate collaboration for developing the content, then other affordances such as simultaneous update ability will be very important.  For example, internal operational documents could be initially developed by a team.  The same holds true for collaboration on content over the internet.


If one of the purposes for implementing a repository is to encourage a culture change towards the sharing of knowledge, then features associated with anonymity or securing departmental information might gain importance.  And if the organization is exposing it’s repository to the internet, then security becomes even more important.


Free vs. Not-Free:


Free: The tool is free and the organization does not need to spend extra money (i.e. maintaining the web page, support needed, extra features, etc.).


Not-Free: Any cost an organization or a group is paying for such as wiki tool, support, maintaining, web space, training, licenses, etc.


Comments (1)

Dr. Ruth Ter Bush said

at 10:47 am on Jan 27, 2009

Unfortunately, cost is rarely a good dividing dimension. It is important, and can be a critical factor, but it is rarely helpful for Use Cases as we all want to reduce costs. Look for ways in which all your factors interact. This is where your use cases will be found. I suspect there are a couple of other important dimensions.

You don't have permission to comment on this page.