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

From zooid Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
__NOTOC__
{{AAType
 
|Image=Dan_Li.jpg
= Overview =
|Location=Montréal
 
|Arts=Visual Arts
<div style="float: right; margin: 15px">
|Type=Person
http://farm3.static.flickr.com/2666/4027443168_879c7b7ccf.jpg
}}
</div>
Dan Li is a professional artistic painter. She was born in China. She has studied arts in China and in France. She likes the impressionism and the contemporary art. In her recent works, she is more interested in the mixed technique.
 
Prepared for http://semantic-mediawiki.org/wiki/Spring_2010_SMWCon
 
== Who is a non-technical person ==
 
* Their focus is not technology, but they can contribute
* '''Never learned programming concepts'''
* Didn't realize Wikipedia can be edited
* Maybe used a web content management system, blog, Facebook
* Busy with their own concerns
 
== Why non technical people ==
 
* Under-served and under-represented
* Helps understand many issues of usability
* Create a more comprehensive Web with more voices, organized semantically
 
== 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''' — ''Results indicate that first impressions are most influenced by the visual appeal of the site. Users gave high usability and interest ratings to sites with high appeal and low usability and interest ratings to sites with low appeal. User perceptions of a low appeal website were not significantly influenced by the site’s usability even after a successful experience with the site.'' — http://www.surl.org/usabilitynews/112/aesthetic.asp
# 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 ==
 
<blockquote>
...the student population is about evenly divided between technologists who care about aesthetics and artists who aren't afraid of machines, which makes it a pretty good place to see the future. — [http://www.shirky.com/writings/situated_software.html Shirky]
</blockquote>
 
# 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
## Help organize masses of data
# 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
## Focused on small groups '''[http://www.shirky.com/writings/situated_software.html Users By The Dozens]'''
### Connect them in the future?
# Lots of value of working with cross-sector interests
 
= 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, editing each others pages, creating more converts
# Creating templates/queries/classes
# Understanding of good class design, inferencing, distributed data, licensing
# Reuse ontologies and web-based content
# Distributed applications, creating standards
 
== Examples ==
* [https://intranet.fungalgenomics.ca/intwiki/Main_Page Genomics Lab] multiple sites (private and public) (programmers)
* [http://www.innovationcell.com Hospital research group] (open minded, dedicated co-developers)
* [http://www.quescan.info Special interest group] (tasked group)
* [http://www.asiancanadianwiki.org Arts group] (maybe — get-togethers, dedicated contributor)
* [http://oq.zooid.org Non profit group] (maybe — heavy use of forms)
 
= 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
 
== Examples ==
 
* General spread to community workers (they know easier specialized systems, didn't help guide structure enough)
* [http://wfg.zooid.org Gardening site] (chose to get programmers to build custom system around Wordpress)
 
= How =
 
<div style="float: right; margin: 15px">
http://zooid.org/~vid/pics/ced/marchwikiparty/small_03072009374.jpg
</div>
 
* Lots and lots of guiding
* Reassure - built on Mediawiki, always exportable
* Inspire - self empowerment, learning culture, creating, leading, "coolness" (graphs), "where the web is going," open source and transparency, participatory web
* Blow past increasing complexity of security to simpler wiki model (all private or all public)
* Threaten - others are doing it, loss of leadership
* Really enforce importance of discussion tab, history, diff, learning from others ('''view source''').. site evolution as an interest, lead of Mediawiki
 
* Magic — Exhibit example of copying filtered data and pasting to spreadsheet
** Too much magic (hypergraphs) is confusing and doesn't work everywhere
* The importance of design
** promote the cues of Wikipedia but provide something original
 
* Appoint leads based on interests, give them responsibilities
* Peer helpers — spread the virus
* Focus on people's abilities - detail oriented, annotator, gardener, storyteller, communicates with offline world, etc
* Translators for those who can't directly contribute
 
* 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, sites related to organization
** Good distributed examples would help too
 
 
<div style="magin: 15px">
http://wiki.zooid.org/images/innocell-wp.png
</div>
 
<br class="cleared" />
 
= 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. SMW is building blocks, play-doh. 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
* SMW site will need a UI (immediate functions) inside a UI (MW)
* Learning curve is constant on wordpress, gets steep fast using SMW
* '''Can recreate a blog in SMW but tasks are more manual'''
** But you work in a reusable semantic space
 
= Summary=
 
* Some successes with non technical users, usually individuals within orgs
* Patience, constant guidance, listening to requirements are most important
* Build up big expectations but focus on immediate goals
* Some SMW facilities such as task oriented guides would help a lot
** Slick rich page editors - links and annotations - would help a lot
** 'Class' editors work with existing elements
** Visual form editor
 
== Questions ==
 
* What are the best extensions to make the site easy to use?
* Can SMW be a good "universal platform?" — is information a nail?
 
= Notes =
 
==Notes from conference==
 
* Business people love reports
* Authoring tools - ease of tagging
** Problems with easy to use rich text editors mangling output
* Stop saying "semantic" — "knowledge engineering"
** Bad perceptions about 'wiki,' they get messy - call it "knowledge management"
* Need more white papers instead of mountain of data
* Find meaningful ways to connect to well known solutions (SQL, etc), use it as an integration platform
* In gov't — "people don't want to collaborate" wan to install wiki but still use Word
* Burden of proof, show how easy it is, fast examples
 
<headertabs />

Revision as of 21:03, 23 May 2010

I attended http://semantic-mediawiki.org/wiki/Spring_2010_SMWCon at the MIT CSAIL Lab in sunny Boston and microblogged (on Twitter) comments on most sessions; my talk is at Encouraging Semantic Mediawiki use with non technical people‎.

State of the software - Yaron Koren

  • First challenge for smw: visibility
  • Second challenge for smw: communication ... duplicate effort
  • "no brick walls separating users from developers," everyone welcome to contribute
  • Third challenge, less important, funding ... too much money can hurt a project
  • "Semantic" is an abused word, use alternatives.. platform.. bur semantic will be the breakthrough?

Welcome address - David Karger

  • @karger - many tools are wrong, developers 'guessing' - smw lets users emerge their data/structure, see more tools like smw
  • Philip of @Ontoprise plan fine access controls; rich editor w annotations, queries; social/dashboard; wikibooks; facet browse, rules

Halo: Current status and future developments in 2010 - Philipp Zaltenbach

  • @Ontoprise dev'ing linked open data #LOD between sites — integrate DBPedia (WP), etc; q about dependencies on their proprietary sw
  • side skype chat discussing problems with rich text editors that mangle output, same problem for many systems

Mashup of LexWiki and WebProtege for collaborative ontology authoring - Guoqian Jiang

  • Guoqian Jiang @MayoClinic Lexwiki collab ontology dev ('propose' tab), curate, integrity; SMW to scale/distrib experts, hierch probs


The Unbearable Lightness of Wiking - A Study of SMW Usability - Jie Bao

  • Jie Bao SMW usability (map.rpi.edu, data.gov) UI trumps low level abilities; forms limited; page model restrictive; devs prefer dev
  • RDF model 'deeply right' for flexbl DB. Fixes: small cadre dev semantics, most use; inline triples; support mult POV; SMW != RDF

Applying SMW on the Wikia environment - Timothy Quievryn

  • Timothy Quievryn SMW impact on @wikia (mostly entertainment); Forms great advance, biggest wikis use it; soon all, dynamic games?

WikiTags: Connecting SMW with MS Office users - Jesse Wang

  • Jesse Wang connects SMW to MS Office for user workflow, usability: uses MS SMartTags. Browse values, easy Outlook export nonfree

Flexible, purposive SMW use - Clarence Dillon

  • Clarence Dillon @DeptofDefense Flexible, purposive SMW use: mil takes 5 years to roll out; hesitate to collab.
  • "Power corrupts; PowerPoint corrupts absolutely"
  • simpler comm model for mil w SMW. huge money/time savings. spread via peer pressure. organic, private wikis, gov2gov, triage, social
  • social networking critical. remote data, vocabularies. encouraging not using Office at all, directly in wiki. wikipatterns
  • avoid noisy data w forms, "nobody above Major/above 35 uses it" (with exceptions) intel. comm. "learn to collab or lose job"

SIMILE, Exhibit, Wibit, Datapress, and Dido - David Karger

  • @karger SIMILE, Exhibit, Dido: structured data in embedded novel interfaces for everyone in author society — lenses, views, facets
  • @karger "You only need one person to be interested in something for it to show up on the Web" Ontario breweries 1914-1915
  • online course catalog in 4 days, took 6 months to get data from registrar; easy reuse data; datapress embed in wordpress cross site
  • Dido inline view/data editor ­— no need to learn schemas, "Make the data look the way you want" separate representation from backend

The future of Semantic Forms - Yaron Koren

  • Yaron Koren @wikiworks Next steps for Semantic Forms better integrated; easier SMW class maint; sep model/view, device UIs; use XML?
  • wiki markup vs xml, issues moving away from wiki model to create richer, simpler UIs, markup too complicated: a crossroads

Handling n-ary data - Yaron Koren

  • No great answers for n-ary data in SMW — no rich page editing, problems with page model?


Créer la version française

File:Lata Pada - Kshetram21.jpg
Type


Home page

http://artsalive.ca/en/dan/meet/bios/artistDetail.asp?artistID=15

Location

Toronto


Lata Pada is a Canadian choreographer and Bharatanatyam dancer of Indian descent. Pada is the Founder and Artistic Director of Sampradaya Dance Creations, a dance Company that performs South Asian dance. She is also the Founder and Director of Sampradaya Dance Academy, a leading professional dance training institution that is the only South Asian dance school in North America affiliated with the prestigious, UK-based Imperial Society for Teachers of Dancing.Pada founded the dance company in 1990 because she wanted to showcase Bharatantyam dance as an art form throughout the world.

Pada, who attended Elphinstone College in Mumbai, trained under the gurus Kalaimamani Kalyanasundaram and Padmabhushan Kalanidhi Narayanan.Pada lives in Mississauga, near Toronto. Pada married geologist Vishnu Pada when she was 17 years old.

In 1985 Lata Pada and her family decided to take an extended vacation to India. On June 23 of that year Vishnu Pada and daughters Arti and Brinda died in the bombing of Air India Flight 182. Lata Pada was not aboard since she left on an earlier date to tour India for Bharatanatyam recitals in Bangalore and across India; Lata was in Mumbai rehearsing for her tour, while her husband and daughters stayed behind in Sudbury, Ontario because Brinda was graduating from high school; afterwards the three flew on Air India 182. Lata Pada became a spokesperson for the families of the victims. After the crash she created the dance piece "Revealed By Fire" in remembrance of the incident. Pada received a master's degree in fine arts from York University in 1997.

Pada married Hari Venkatacharya in September, 2000. Venkatacharya is an entrepreneur and was Managing Director of Nytric Business Partners and is the Immediate Past President of TiE Toronto. He also serves on the Boards of the Ontario Science Centre and Fields Institute for Research in Mathematical Sciences. They both met while founding the South Asian advisory committee at the Royal Ontario Museum in 1995, where they raised over $3 million Canadian dollars for Canada's first permanent South Asian Gallery.

In December 2008, she was made a Member of the Order of Canada for her contributions to the development of Bharatanatyam as a choreographer, teacher, dancer and artistic director, as well as for her commitment and support of the Indian community in Canada. Lata was also recently appointed as Adjunct Professor in the Graduate Faculty of Dance, York University, Toronto.


This article based on content from http://www.wikipedia.org. Original version: http://en.wikipedia.org/wiki/Lata_Pada
Retrieved from "https://wiki.zooid.org/index.php?title=Encouraging_Semantic_Mediawiki_use_with_non_technical_people&oldid=3296"