Courses/Wikis-Publishing Platforms

<slidy theme="a"/>

Wikis as Publishing Platforms - 3 x 3 hours course

Wikis-Publishing_Platforms/synopsis and goals

Day 1

Getting to know wikis: what are wiki. wiki syntax, pages, categories, Extensions.

Context: wikis as (hybrid) publishing platforms

• Publishing
  • what is written on wikis is public;
  • Low threshold for publishing - click the edit button

• (Hybrid)
  • wiki content can easily be published under different formats or context.
  • Examples: Wikipedia Export book function; Toneelstof, Beyond Social, or this presentation (both wiki content and slide show)

Ward Cunningham Wiki Wiki Web

In 1995 Ward Cunningham creates the first wiki, naming it Wiki Wiki Web (Wiki in Hawaii means quick!).

• Interview with Ward Cunningham
  • links between pages, as ways to connect information
  • links to non-existing, encourage the creation of the new pages
  • read-write system - writing is as natural and expected as writing
  • the wiki territory expands as a result of contributions
  • anonymous editing - collaborative writing.

Wikipedia, Wiki Media Foundation, MediaWiki

• 2000 - Jimmy Wales attempts to create a free online encyclopedia - Nupedia.
• Nupedia fails.
• 2001 - After hearing about wikis Wales and Larry Sanger decide to build Nupedia on it, calling it Wikipedia.
• Wikipedia was first build using a software called UseModWiki (a sibling of Wiki Wiki Web). UseModWiki was slow and didn't support the scale Wikipedia was growing into.
• A new wiki software for Wikipedia, starts is developed, based more efficient and scalable web technology: PHP programming language, MySQL database. The software got the name of MediaWiki.
• 2002 - Wikipedia switches to using MediaWiki.
• 2003 - Wiki Media Foundation is created.
• MediaWiki currently power many wikis, including Wikipedia and subsidiary project, as well as other wiki such as this one.

Wiki software

• MediaWiki - PHP, MySQL, Webserver
• Docuwiki - similar to MediaWiki
• MoinMoin - Python, relies on plain text files & folders
• Zim - Desktop wiki, relies on plain text files & folders.
• TiddlyWiki - another Desktop wiki, based on HTML files and Javascript

Comparison of wiki software

Running a wiki: 2 options

Install and set up a wiki in your PC or server.

OR

Use a wikifarm (wiki host), such as Wikia. List of several wiki farms.

Users

To edit a wiki you need most wikis to register as user.

Different user's groups have different privileges:

• user: can edit and create pages
• administrators: can delete pages, put other users into a different group
• bot

Wiki Markup language

Wiki Markup: structured text, simplified version of HTML, easily converted to HTML.

• Wiki Markup Cheatsheet
• Tutorials/wiki_tutorial
• File:Cheatsheet-en.pdf File:Cheatsheet-nl.pdf

Pages Creation

Pages can be created by:

• creating an empty page link, clicking it, and start editing. The following [[my empty page]] will translate to my empty page
• adding the page name to URL bar, you'll be directly to the empty page, and start editing http://publicationstation.wdka.hro.nl/wiki/index.php/my empty page

• Red link = previously non-existing page.
• Blue link = existing page.

Talk Pages

Every Page has its respective Discussion or Talk page.

Talk pages are the site of discussion and conflicts that go on to the making of an article.

An example: Talk page on Invisible Pink Unicorn Wikipedia article

Experiment:Edit User Pages

Create and edit your user page.

Include internal (to pages on this wiki) and external (to web pages outside this wiki) links.

Include an internal and external image.

Files and Images

To include non-text media (images,pdfs,audio-video) on the wiki, a File page needs to be created as a place-holder for the file

• [[File:myimage.png]]
• the page must be saved
• click on the red link, of the file you want to upload
• Follow the instruction to upload your file

Pages' Revision History

The history of versions or revisions of a page is stored.

They can be accessible via "View History"

Each revision shows its author, time, action, and at times summary.

Revisions can be compared, edited and undone.

Artworks exploring Wikipedia's Revision History

The Iraq War: A History of Wikipedia Changelogs by James Bridle, collects the history of changes from the Wikipedia's article on The Iraq War between 2004 and 2009.

Epicpedia by Annemieke van der Hoek transforms Wikipedia's revision history into a theater script.

Cramer, Florian. 2011. “A Brechtian Media Design: Annemieke van Der Hoek’s Epicpedia.” In Critical Point of View: A Wikipedia Reader, 221–26. Amsterdam: Institute of Network Cultures. http://networkcultures.org/blog/publication/critical-point-of-view-a-wikipedia-reader/

Works that:

• present other interfaces to Wikipedia,
• placing in the foreground the revision history:
• question the neutral point-of-view and unified nature of Wikipedia articles.

Experiment:History

Rewind the history of edits from your user page to a previous stage, and back to the current.

Structuring a wiki

What situations require an overall structure, more elaborate than its "flat" systems of pages?

Subpages: simple hierarchy

Subpages are useful for organizing information hierarchically, as parent/child/grandchild

A subpage of a given main page, is create by adding a slash, followed by the sub-page's name, to the main page name.

[[main page/subpage/sub-subpage]]

Example: this very page Courses/Wikis-Publishing Platforms is a sub page from the Courses page

{{Special:PrefixIndex/{{FULLPAGENAME}}/}} can be placed on a parent page to display all its children.

Namespaces: separate spaces

Namespaces are container for specific content.

• Example: the Namespace Wrecks in this wiki was created for material dedicate to Wrecks project and not a part of the Publication Station Wrecks:Main_Page and FIN:Main_Page

• Note: Namespaces need to be created in the configurations of the wiki.

Categories: Tags, Hierarchies, Spaces, States

Categories are (the only) ways to tag content.

[[Category:courses]] a page to the courses category

Problems: No limit to the categories that can be added to a page.

For next week

Install Pandoc on your machines. We'll use it to convert wiki content on other formats.

Day 2

The Importance of Being Markup

Converting wiki content into other formats.

Markups

Wiki syntax is a markup language. Markup languages are exclusive to plain text formats (as opposed to rich text or binary formats). In plain-text file text-formating is applied to the text through a series of "marks" or tags. The marks or tags are like instructions, on how each marked segment of text should be interpreted or rendered.

Markups: write/interpret

You have be doing been using the wiki Markup during this workshop. You've probably noticed how, when in writing mode, symbols as =heading= bold Page are interpreted and given a specific meaning or style when the wiki page is rendered, or in other words, is in read mode.

Like the markup of the following segment, originates a styled and structured page.

= Revenge of the Text =

There is a room in the '''Musée d’Orsay''' that I call the ''room of possibilities''.

That room contains:
* a snow flake
* the end of a cloud
* a bit of nothing

Markup: explicit structure

One of the advantages of markup languages is that they imply an explicit text structure.

In order words, markups force you to declare:

• "this sentence is a section heading": =section heading=
• "this word is bold": bold word.
• "this hyperlink has x as URL and" [x-URL title]

You are not allowed to give meaning or structure to the text by visually styling (like you'd do in inDesign or Word).

Meaning or structure can only be given to the text semantically. That means adding marks to the segments of text we want to format.

Markups: interchangeable

One advantage of this explicit semantic formating is that conversions between different markups (Wiki, HTML, Markdown, LaTeX, etc) are made easy.

In most cases markups have HTML as a reference, allowing only formating options that are available in HTML.

Consequently converting between markups is easy.

A markups converter software has to only to know the meaning of all the meta-characters in a markup and what are the corresponding meta-characters in another markup.

If the software knows that it can convert

=title=

to

<h1>title</h1>

,

# title

,

\section{title}

Examples: the same text in different Markup

HTML:

<h1>Revenge of the Text</h1>
 <p>There is a room in the <strong>Musée d’Orsay</strong> that I call the <em>room of possibilities</em>.</p>
 <p>That room contains:</p>
 <ul>
  <li>a snow flake</li>
  <li>the end of a cloud</li>
  <li>a bit of nothing</li>
 </ul>

Wiki markup:

= Revenge of the Text =
There is a room in the '''Musée d’Orsay''' that I call the ''room of possibilities''.

That room contains:
* a snow flake
* the end of a cloud
* a bit of nothing

Markdown:

# Revenge of the Text
There is a room in the **Musée d’Orsay** that I call the *room of possibilities*.

That room contains:
* a snow flake
* the end of a cloud
* a bit of nothing

LaTeX

\section{Revenge of the Text}\label{revenge-of-the-text}

There is a room in the \textbf{Musée d'Orsay} that I call the \emph{room
of possibilities}.

That room contains:

\begin{itemize}
\itemsep1pt\parskip0pt\parsep0pt
\item
  a snow flake
\item
  the end of a cloud
\item
  a bit of nothing
\end{itemize}

Pandoc

One popular software for converting between markups is Pandoc

Working with Pandoc

Pandoc is a command-line tool. This means that instead of a GUI it uses a command line interpreter or shell, where the interaction with it is based on text commands.

There a few web interfaces to Pandoc, such as http://pandoc.org/try/, but they are not as flexible as the command-line interface to Pandoc.

Pandoc conversions: wiki to HTML

Convert a file containing mediawiki syntax, into a an HTML file.

pandoc --from mediawiki --to html5 --standalone input.wiki --output=output.html

pandoc - program dedicate to the conversion between different markups.

--from - option standing for “from”, is followed by the input format;

--to - option standing for “to”, is followed by the output format;

--standalone - option standing for “standalone”, produces output with an appropriate header and footer;

--output - option for file output;

input.wiki - plain-text file with wiki syntax - you need to replace it by its actual name

Pandoc conversions: HTML to wiki

pandoc --from mediawiki --to html5 --standalone input.wiki --output=output.html

Pandoc conversions: wiki to ICML

ICML files can be imported into inDesign. See Hybrid publishing/publishing resources#working_with_ICML_files for more information.

Pandoc conversions: wiki to EPUB

It is also possible to use Pandoc to produce an EPUB from a single

.wiki

file, or any other markup accepted by Pandoc.

A few extra resources, such the cover image, metadata, and stylesheet should be included, as they strongly influence the EPUB's outcome.

pandoc --from wiki --to epub3 --self-contained --epub-chapter-level=1 --epub-stylesheet=styles.epub.css  --epub-cover-image=cover.jpg --epub-metadata=metadata.xml --toc-depth=1 --output=book.epub     book.wiki 

New options:

• --epub-chapter-level=1 - at what titles' level chapters occur: heading 1
• --epub-stylesheet=styles.epub.css - css style sheet for epub
• --epub-cover-image=cover.jpg - epub cover image
• --epub-metadata=metadata.xml -
• --toc-depth=1

Example of metadata.xml

<dc:title id="epub-title-1">MAIN TITLE</dc:title>
<meta refines="#epub-title-1" property="title-type">main</meta>
<dc:publisher>Your Publisher</dc:publisher>    
<dc:date id="epub-date">2015</dc:date>
<dc:language>en-US</dc:language>
<dc:creator id="epub-creator-0">AUTHOR'S NAME</dc:creator>
<meta refines="#epub-creator-0" property="role" scheme="marc:relators">aut</meta>
<dc:contributor id="epub-contributor-1">EDITOR'S NAME</dc:contributor>
<meta refines="#epub-contributor-1" property="role" scheme="marc:relators">edt</meta>
<dc:contributor id="epub-contributor-5">DESIGNER'S NAME</dc:contributor>
<meta refines="#epub-contributor-5" property="role" scheme="marc:relators">dsr</meta>
<dc:subject>TAGS, SEPARATED BY, COMAS</dc:subject>
<dc:description>PUBLICATION SYNOPSIS</dc:description>

Conclusion: wiki as hybrid publishing tools

Hopefully these examples make more clear what I stated in day#1 wikis are inherently hybrid publishing tools, as

• wikis are about publishing quickly and easily
• wiki content can be easily converted to other formats, since it uses a Markup languange.

As a result many derived works, or re-mediations of wiki content exist. From the more pragmatic examples, such as Wikipedia Export book function, Toneelstof, Beyond Social, or this presentation (both wiki content and slide show); To more artistic interventions such as The Iraq War: A History of Wikipedia Changelogs by James Bridle or Epicpedia by Annemieke van der Hoek.

We'll continue looking re-mediations of wiki content. In the next day we'll focus on the MediaWiki API, an interface to Mediawiki wikis, which allows retrieving and editing content programatically.

Day 3: Remediation

Appropriating and reporposing wikis' content.

How to get content?

Although there is nothing wrong in copying the content of wiki pages in order to turn them into other publishing objects, it is a slightly tedious process, specially when you want to work with large quantities of data. Those tedious tasks can be more easily handled by software.

Mediawiki wiki present a solution for this problem by providing a Web API, which functions as a programmatic interface (computer-to-computer instead of human-to-computer) to Mediawiki installations.

APIs

An API or application programming interface is an interface that allows interaction via other software. It allows things such as apps to be build on top of existing services, where the apps use the API to interact with the service.

Web APIs

Mediawiki API is a Web APIs.

Essentially it means that the API is accessed thought HTTP requests and responds using JSON or XML object.

Mediawiki API

Mediawiki API allows many and very intricate request for information (and editing) from Mediawiki installations.

A few examples will follow, you can request using your web browser. Including a Pretty-prints JSON extension on your browser, as it will help you read the API's responses.

Example: Page basic info

https://en.wikipedia.org/w/api.php?format=json&action=query&titles=Main_Page&prop=info English Wikipedia's Main Page

http://beyond-social.org/wiki/api.php?format=json&action=query&titles=Colophon&prop=info Beyond Social's Colophon page

Example: Page content

https://en.wikipedia.org/w/api.php?format=json&action=query&titles=Main_Page&prop=revisions&rvprop=content English Wikipedia's Main Page

http://beyond-social.org/wiki/api.php?format=json&action=query&titles=Colophon&prop=revisions&rvprop=content Beyond Social's Colophon page

Decomposing an API request

http://beyond-social.org/wiki/api.php? format=json & action=query & titles=Colophon & prop=revisions & rvprop=content 

• http://beyond-social.org/wiki/api.php? - endpoint - the home page of the MediaWiki web service. It can be found by going to the Version:Special page of a wiki a searching for the API entry point
• format=json - the format of the output. Can either be JSON of XML, although XML is being phased out
• action=query - what action to you want to performed. query is the most used, but there many more available options, such as editing and deleting pages.

Then comes the action specific parameters

• titles=Colophon - the page queried
• prop=revisions - what properties you want from of a page: revision. As no particular revision is specified the latest will be returned
• rvprop=content - what specific properties you want from the page revision in question: content. You could also ask for the user who created the last revision, or the comment left by the user. These properties can be combined in a single request. rvprop=content|user|comment

Examples: Users

• what is an API
  • web apis
• MW API
• Example of MW API requests
• Python examples

, an interface to Mediawiki wikis, which allows  retrieving and editing content programatically

Notes on scripts

students should have to understand python to generate "derivates" from wiki content.

Instead they can be given a script that allows them to play with different arguments and allow different "derivates" to emerge from the same content.

Some guidelines:

• each script deals with only one type of content: users, text, revisions, images, subpages

the principal should be similar to epubtrailer where the user can choose: background-color, color, source (wiki, page),