Encouraging Semantic Mediawiki use with non technical people: Difference between revisions

Revision as of 22:35, 20 May 2010

to solve their problem, usually a "one of those" web site with some special requirements
something that looks good - design is still paramount
to learn about the participatory web
to create reusable data?
to have more control over their own site but keep things simple
1. usually they don't want to 'innovate,' just do what everyone else is doing
to work with someone they trust

avoid per client custom code, fit things into the developing picture
promote digital literacy — filling out forms isn't it, stop treating computers as a typewriter
1. reference-able statements, reusable data under fair terms of re-use
get people to consider issues of site design and how to organize information without overburdening
promote transparency and co-development
1. help flatten organizations and their external relationships
grow my own skills based on relevant requirements

Traditional executive — "everyone else is doing it," inexpensive solution
- ideally they will participate but getting them to can be difficult
- may be more cautious about full commitment - license, security, who can access and edit
Creative group or individual — may be inspired but needs constant guidance
Worker bee — tasked to use the wiki
- may be less receptive to wiki ideals, make it straightforward
Outside contributors - often a stated goal of projects, have their own objectives
- flexible to meet random demands
- fair re-use terms

In order:

Commitment vs follow through
- Constant attention, guidance
Tangly mess
- Better use of SMW features, more forms, patience for gardening
Misunderstood requirements, not really listening to what they want
- Learning experience

Lots and lots of guiding

Inspire - self empowerment, less dependence, creating, leading, "where the web is going," open source and transparency

Threaten - others are doing it, loss of leadership

Blow past increasing complexity of security to simpler wiki model (all private or all public)

Really enforce importance of discussion tab, history, diff, learning from others.. site evolution as an interest

Appoint leads based on interests, give them responsibilities

Peer helpers — spread the virus

Translators for those who can't directly contribute

Profiles of uses

The importance of design

Magic — Exhibit example of copying and pasting to excel using semantic web data

Compare to Wordpress — "Raskin vs Englebart," dashboard + specialized appliance model vs learning to use a computer

Wordpress is task driven. Forms for every day tasks. Need to map MW extensions.

Every day tasks —

@@ Line 27: / Line 27: @@
 # avoid per client custom code, fit things into the developing picture
-# promote digital literacy — filling out forms isn't it, stop treating computers as a typewriter
+# '''promote digital literacy — filling out forms isn't it, stop treating computers as a typewriter'''
 ## reference-able statements, reusable data under fair terms of re-use
 # get people to consider issues of site design and how to organize information without overburdening
-# help flatten organizations and their external relationships
+# '''promote transparency and co-development'''
-# promote transparency and co-development
+## help flatten organizations and their external relationships
 # grow my own skills based on relevant requirements