Import/export wikipedia info

gusaus's picture
public
gusaus - Tue, 2006-10-10 23:55

In an effort to contribute to various music/arts-centric solutions, I've been looking for ways to use wikis as a repository for basic info that often gets duplicated.

Couple instances:

Many music sites such as emusic, MP3.com, Yahoo Music, and Rhapsody are licensing content from services like All Music Guide. On the other hand, sites like Wikipedia and Wikia already, or could, provide much of the same info.

When setting up a venue, services such as Upcoming, Eventful, Zvents, require the same standard info (name, address, category, brief description, etc.) that also could be found in a wiki (Wikipedia: Music Venues).

Being a non-programmer, I have no idea how easy/difficult it would be to pull and present relevant data, from wikis, in a structured, standardized fashion. Seems like it would save a lot of time/money/effort for both the sites/services as well as the artists and venues themselves.

I'm wondering if there's any development and/or thinking along these lines. I'd like to contribute any way I can.


Gollum browser may help...

rport's picture
rport - Thu, 2006-11-02 12:37

Perhaps you might like to look at the Gollum project

Gollum is a Wikipedia Browser for fast and eyefriendly browsing through the free encyclopedia "Wikipedia". Gollum gives you access to nearly all Wikipedias in all languages. Further more Gollum gives you some special features which allow you to easily customize your work with Wikipedia.

In my opinion the interface of Wikipedia is too overloaded and confusing. So let's get an easy to use interface. Gollum, the intuitive way to the powerfull knowledge of Wikipedia.

Gollum is for free and can be downloaded under the General Public License (GPL).

Russ


api

saml@drupal.org - Tue, 2007-02-20 00:20

Gollum, as far as I know, uses the MediaWiki api mentioned above, to extract the content of articles, and embed it in it's own browser-look-alike.

MediaWiki is THE...

saml@drupal.org - Tue, 2007-02-20 00:04

Presuming I have understood your needs correctly there's no better solution to this than MediaWiki (That's at least what I think... =) ).

Look at http://test.rilpedia.org/wiki/Venue:Phantom_of_the_opera (just put it there).

The code goes:

*'''Name:''' {{:{{PAGENAME}}/name}}
*'''Address:''' {{:{{PAGENAME}}/address}}
*'''Category:''' {{:{{PAGENAME}}/category}}
*'''Brief Description:''' {{:{{PAGENAME}}/brief description}}

( As you might have figured out{{:Some artice}} Means "translusion" of that article.)

If you look in http://test.rilpedia.org/wiki/Venue:Phantom_of_the_opera/name or http://test.rilpedia.org/wiki/Venue:Phantom_of_the_opera/address you find out where the data goes (Note the tiny "breadcrumb" under the title. It is shown there just because the URL looks like it does).

Now, you can either get just the content of this "venue", neatly formatted as HTML: http://test.rilpedia.org/w/index.php?title=Venue:Phantom_of_the_opera&ac...

Or extracting the complete info from each of the subpages, in a single XML-query, through the api:
http://test.rilpedia.org/w/api.php?action=query&prop=revisions&titles=Venue:Phantom_of_...

MediaWiki is THE container for data. Any solution incorporating Drupal should IMO always be INTEGRATING MediaWikis, not trying to build MediaWiki again. (Of course, why should you when there's a software constantly being tested against some 3,609,593 reg. user accounts... all of these know the syntax and ... and ... and... =) ).

Sincerely
Samuel Lampa
MediaWiki / Drupal Theme design