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

Jump to navigation Jump to search

Encouraging Semantic Mediawiki use with non technical people (view source)

Revision as of 23:14, 20 May 2010

27 bytes added ,  20 May 2010
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
__NOTOC__
{{Wiki_List |
wiki_name  =                PattayaWiki  |
wiki_logo =                [[Image:NoLogo.png]] |
wiki_URL =                  http://www.pattayatalk.com/wiki  |
wiki_recentchanges =        http://www.pattayatalk.com/wiki/index.php/Special:Recentchanges |
wiki_status =              Active        |
wiki_lastreviewed  =        05-Feb-06      |
wiki_language =            English        |
wiki_editmode =            OpenEdit      |
wiki_engine =              MediaWiki |
wiki_maintopic =            Pattaya}}
==Description==
Pattaya is one of the most interesting cities in the world. It can also be a full of trials and tribulations for the unweary. Newbies and the experienced traveller alike can benefit from the information available here.


= Overview =
PattayaWiki is a project to create a free, complete, up-to-date and reliable Pattaya travel guide. So far we have 37 guides and other articles written and edited by Pattaya travellers from around the globe.


<div style="float: right; margin: 15px">
'''Additional Categories'''
http://farm3.static.flickr.com/2666/4027443168_879c7b7ccf.jpg
{{tag|Sex Tourism}}
</div>
{{tag|South East Asia}}
 
{{tag|Thai}}
Prepared for http://semantic-mediawiki.org/wiki/Spring_2010_SMWCon
{{tag|GoGo Bars}}
 
{{tag|Beer Bars}}
== Who is a non-technical person ==
{{tag|Vacation}}
 
{{tag|Holiday}}
* Their focus is not technology, but they can contribute
{{tag|Retirement}}
* Never learned programming concepts
{{tag|Singha Beer}}
* Didn't realize Wikipedia can be edited
{{tag|Chang Beer}}
* Maybe used a web content management system, blog, Facebook
{{tag|Longtime}}
* Busy with their own concerns
{{tag|Shorttime}}
 
{{tag|Luff u 2 mutt}}
== Types and motivations of participants==
 
* 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
 
<br class="cleared" />
 
= Goals =
 
== What do they want ==
 
# to solve their problem, often 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 have more control over their own site but keep things simple
## usually they don't want to 'innovate,' just do what everyone else is doing
# to work with someone they trust
# don't really seem concerned about "silo" and re-use aspects
 
== What do I want ==
 
# 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'''
## 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'''
## help flatten organizations and their external relationships
## don't be fearful and build hidden compromises, open it up
# grow my own skills based on relevant requirements
 
= Success=
 
In order:
 
# Useful one-off resource with lots of development input from stakeholders, possible to build on in future
# contributions by many types of people
# basic editing using forms
# wiki markup, categories
# sharing knowledge, creating more converts
# Creating templates/queries/classes
# understanding of good class design, distributed data, licensing
# distributed applications, creating standards
 
= Failure =
 
<div style="background: black; padding: 50px">
<center>
http://wiki.zooid.org/images/no-edits.png
</center>
</div>
 
* 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
 
= How =
 
Lots and lots of guiding
 
Inspire - self empowerment, learning culture, creating, leading, "coolness" (graphs), "where the web is going," open source and transparency, participatory web
 
Reassure - built on Mediawiki, always exportable
 
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 ('''view source''').. 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
* promote the cues of Wikipedia but provide something original
 
<div style="magin: 15px">
http://wiki.zooid.org/images/innocell-wp.png
</div>
 
Magic — Exhibit example of copying and pasting to excel using semantic web data
 
= SMW vs Wordpress =
 
Compare Wordpress vs SMW — "Raskin vs Englebart," specialized appliance model vs learning to use a computer
 
http://www.retrofacto.com/wp-content/uploads/2009/06/wordpress.jpg
 
* '''Wordpress''' is task driven software. Forms for every day tasks. Helpful to map MW, SMW, extensions but it still won't be the same.
 
Every day tasks —
* Everything oriented towards content management around blogging
* SEO, user management
* "Delete" content, one click
 
= Summary=
 
* Some successes with non technical users, but usually individuals within orgs
* Constant guidance is most important
* Some SMW facilities such as task oriented guides would help a lot
* Slick rich element editors would help a lot
* People like visualizations and they can help with shaping and debugging data
* Always focus on their goals rather than ideals, but try to explain the vision, the two should come together
* Use lots of meaningful examples
** Placeography, DiscourseDB
 
<headertabs />
Retrieved from "https://wiki.zooid.org/w/Special:MobileDiff/3247"

Navigation menu