Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs











More recommended blogs »

Here are posterous posts filed under mediawiki...

Spyros says...

Great article by LifeHacker that explains how to Customize a MediaWiki installation in such a way that it will be used as a Collaborative Web Site. I would like to implement this in an Intranet. I think that would be interesting!

Check it at: http://lifehacker.com/5396832/customize-mediawiki-into-your-ultimate-collaborative-web-site

Filed under: MediaWiki

chieftech says...

I have had a fair share of hands-on time with wikis. With that said, I’ve come to a conclusion — MediaWiki inhibits Enterprise 2.0.

I'm with Gil on this. I recognise that MediaWiki *never* claimed to be an enterprise social computing tool and that in many instances it was the bridgehead that introduced wikis inside the firewall, but it isn't really fit for enterprise purposes beyond a very narrow use case. Gil goes on to describe four inhibitors: No rich text editor, no fine grained access control, no document management and no additional collaboration features.

Filed under: mediawiki

fnielsen says...

The MediaWiki page counter for my Brede Wiki now tells me that it has passed the 1000 "total pages" mark. Pages include, e.g., comments with data on scientific articles, pages for brain regions and pages for "topics" such as neuroticism. The Brede Wiki is presently open for anonymous edits and wiki spammers are quite interested in the article on Hidehiko Takahashi. I wonder if they are communicating something via the cryptic comment fields. Disregarding the spammers the article on Richard S. J. Frackowiak seems to be the most popular article after posterior cingulate gyrus.

Filed under: mediawiki

isayel says...

As an early Mediawiki user and evangelist I will only write about Mediawiki as a CMS.

Nowadays Content Management System refers mainly to Database Management System and Mediawiki stores the content of the wiki in a database. This storage is as easy as writing freely in "edit" mode and save. You can use or not some mediawiki markups to improve presentation of the text (bold, italic...) and link one page with another or refer to an external website.
So MediaWiki is the most powerful way to quickly store and retrieve any data
But at the end of the day you can SEARCH in the wiki every single word you want BUT you will NOT be able to ASK a basic question (query) to this wiki database.

Example:
- search : "Berlin" > you will get an amazing page of results with all the pages which titles contain the word "berlin" and all the pages which contain the word "berlin" in the core text content.

- ask :"What is the capital of Germany" > no way.

The Semantic Mediawiki Extension adds a "dissipated structured database layer" to MediaWiki. Any data, anywhere inside the text of any MediaWiki page, can be selected to be structured as having some values of some property. Properties are similar to the traditional fields of a structured database. So adding property and values to some data in your Mediawiki allow two tremendous features:
1- Ask (query) : for example in your international company you decide to run one unique wiki. This wiki has to be multilingual. A nice way to know where are the pages written in French is to do a simple query to the database. You decide then to create a Property:Language. To do so:

  1. you open a new page with title "Semantic Properties" : everybody will be invited to check it before "editing" a page in the wiki.
  2. this new page contains a very short list of mandatory properties according to your wiki target use.
  3. each property is written in the page with the following mediawiki markup : [[Property:Language]]
  4. when you save the "Semantic Properties" page you click on the link 'Property:Language'
  5. the page with title 'Property:Language' explains the different value of Language: English, French, German, Italian, Portuguese, Spanish, ... This is not an exhaustive list, any user can add a new value (ex: Chinese)
  6. new page has to contain this tag [[Language::English| ]] or [[Language::French| ]] to be reported as an English or a French page.


2- Report (Printout) : every query could be reported or print out in a customized format. This is a hugh and valuable improvement to compare with the result SEARCH page of standard Mediawiki.

3- Forms: on my point of view it is the less operating feature as it reduces the "free editing" feature which gives more power to the wiki content compared to blog content. Enrichment of content is open in a wiki and this is what enterprise 2.0 are looking for.

To wrap it up, Semantic tool must not kill the free access to knowledge that Mediawiki gives, offers to organisation.
Let a free folksonomy prevail and do not impose a presupposed taxonomy. Life and time will build it as it should be...

Credit Jean-François Ayel > Michelin, Jean-François Tavernier, CEO Versailles NewYork, Jean-Pierre Ayel, Direct Marketing Handbook, Years of experience: Dbase 1984, Internet 1994, Mediawiki 2004, Zaragoza.DiWiki.org 2006...

See also : http://iphylo.blogspot.com/2009/08/wikispecies-is-not-database.html

Related articles by Zemanta
Zemanta helped me add links & pictures to this email. It can do it for you too.

     
Click here to download:
Semantic_and_Mediawiki_free_an.zip (173 KB)

Filed under: mediawiki

px says...

i wish wordpress tags had support for pseudonyms, aliases, etc kind of like how mediawiki can for pages.

Filed under: mediawiki

hdknr says...

Formats text following the MediaWiki (http://meta.wikimedia.org/wiki/Help:Editing) syntax.

To return HTML from Wiki:

from wikimarkup import parse

parse
(text[, show_toc=True])

To return HTML without certain "annoying" elements, such as headings:

from wikimarkup import parselite

parselite
(text)

ふーむ。

Filed under: mediawiki

elya+ray says...

Vor ein paar Wochen hatten wir Besuch von Tim Pritlove, dem Macher des Chaosradios. Mit einer Sackkarre voller Audio-Technik belegte er unser Wohnzimmer und die Steckerleisten, und ausgestattet mit zwei beeindruckenden Headsets und zwei frischgebrühten Milchkaffees tauschten wir uns über anderthalb Stunden zum Thema MediaWiki aus.

Fast zeitgleich und sehr passend ;-) zu dem Launch meiner neuen Website mediawiki-beratung.de ist heute die aktuelle Ausgabe des Chaosradio-Express-Podcasts live gegangen.

(Raymond)

Filed under: MediaWiki

jfayel says...

* All web2.0 and specifically Wikis need so much good sourcing
- JFA
 
* Post YOUR comments and tips...
 
 
How to Cite Sources
The purpose for citing is to let readers know that a specific piece of
information you're providing has a source, other than your own
observation or reasoning. In many cases, the strength and credibility
of your work depends on the validity of your sources, as well as your
ability to represent those sources clearly without plagiarizing. Even
if you fail to cite a source, or cite improperly, without meaning to
do so, the consequences can be just as dire as if you did it on
purpose, especially in academic and professional settings.
...
 
http://www.wikihow.com/Cite-Sources
 

Filed under: mediawiki

jfayel says...

* Be true on social networking... in plain true
  Be true or you will go nowhere...
 - JFA
 
* Post YOUR comments...
 

Filed under: mediawiki

elya+ray says...

Eine gute Woche. Eben die Pressemitteilung der Foundation gelesen: Die Stanton Foundation, benannt nach dem CBS-Chef Fank Stanton, spendet 890.000 US-$ mit dem Zweck, die Benutzeroberfläche von Wikipedia für Neuautoren einfacher/zugänglicher zu machen. Ich bin begeistert - wer nämlich einmal außerhalb unseres sehr kleinen WP-Universums versucht hat, einem Newbie die Benutzung eines Wikis zu erklären, weiß, daß wir uns das mit dem "Wiki-wiki-ist-alles-doch-ganz-einfach" nur einbilden. Das war vielleicht 2003 mal so, ist jedoch lange Vergangenheit. Die Wikipedia-Oberfläche ist insgesamt unglaublich kompliziert geworden, wir haben uns eben nur daran gewöhnt.

Ideen, wie man sowas machen könnte, gehen mir schon lange durch den Kopf:

  • Usability-Studie eines unabhängigen Instituts/Uni
  • Umfrage in der Community
  • Projektteam bei der Foundation, Besetzung einer Jury mit Fachleuten und gewählten Community-Mitgliedern
  • Beschreibung der Anforderungen
  • Internationale Ausschreibung, z.B. an entsprechenden Hochschulen
  • ... usw.

Denn: es geht ja nicht nur ums Finden von Lösungen, sondern auch um die Akzeptanz unter den „Alt“-Benutzern, die jede noch so geringe Veränderung an „ihrem“ Interface seitenweise diskutieren müssen...

(elya)

Filed under: MediaWiki