<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Guillaume Paumier&#039;s weblog &#187; digiKam</title>
	<atom:link href="http://www.gpaumier.org/blog/tag/digikam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gpaumier.org/blog</link>
	<description>open knowledge, design &#38; technology</description>
	<lastBuildDate>Thu, 26 Jan 2012 15:14:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>digiKam / KDE imaging coding sprint 2009</title>
		<link>http://www.gpaumier.org/blog/330_digikam-kde-imaging-coding-sprint-2009/</link>
		<comments>http://www.gpaumier.org/blog/330_digikam-kde-imaging-coding-sprint-2009/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 07:07:00 +0000</pubDate>
		<dc:creator>Guillaume Paumier</dc:creator>
				<category><![CDATA[KDE]]></category>
		<category><![CDATA[digiKam]]></category>
		<category><![CDATA[Essen]]></category>
		<category><![CDATA[Germany]]></category>

		<guid isPermaLink="false">http://www.gpaumier.org/blog/?p=330</guid>
		<description><![CDATA[I just came back from the digiKam / KDE imaging coding sprint in Essen, Germany. My main goal was to start working on an export plugin to Wikimedia Commons from digiKam, which can be a wonderful tool for Wikimedia photographers. <a href="http://www.gpaumier.org/blog/330_digikam-kde-imaging-coding-sprint-2009/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<div id="attachment_482" class="wp-caption aligncenter" style="width: 600px"><a href="http://www.flickr.com/photos/languitar/4112662088/"><img class="size-full wp-image-482" title="digiKam coding sprint by Johannes" src="http://www.gpaumier.org/blog/wp-content/uploads/2009/11/digiKam-coding-sprint-by-Johannes.jpg" alt="digiKam coding sprint by Johannes digiKam / KDE imaging coding sprint 2009" width="590" height="245" /></a><p class="wp-caption-text">digiKam &amp; KIPI coding sprint 2009. Photo by Johannes Wienke.</p></div>
<p>I just came back from the <a href="http://techbase.kde.org/Projects/Digikam/CodingSprint2009">digiKam / KDE imaging coding sprint</a> in Essen, Germany. My main goal was to start working on an export plugin to Wikimedia Commons from digiKam, which can be <a href="http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/">a wonderful tool for Wikimedia photographers</a>.</p>
<p>I met a lot of great people there, and it was really nice to benefit from their experience. I learnt a lot during these three days, and being in the same room as other developers made it a lot easier to work together.</p>
<p>By analyzing how the existing Facebook KIPI plugin was made, I was able to create the basis of the communication layer between the plugin and a MediaWiki site, even though I had not done any C++/Qt development before. Admittedly, I had some existing knowledge of Lisp, Java and C, but it was old and limited; I was quite happy to advance so quickly. While my current work focuses on a specific wiki (Wikimedia Commons), it could be later extended to a more general MediaWiki library for Qt.</p>
<p>Special kudos and <em>Vielen Dank</em> to Marcel Wiesweg, who organized the whole event. Everything went great, we had a pretty good Internet connection and we even ate well! (one thing you wouldn&#8217;t necessarily expect during a coding event). <a href="http://www.gpaumier.org/blog/331_airport-fun/">The trip back</a> was also fun.</p>]]></content:encoded>
			<wfw:commentRss>http://www.gpaumier.org/blog/330_digikam-kde-imaging-coding-sprint-2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>digiKam, the perfect tool for Wikimedia Commons photographers?</title>
		<link>http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/</link>
		<comments>http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 15:32:44 +0000</pubDate>
		<dc:creator>Guillaume Paumier</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[KDE]]></category>
		<category><![CDATA[Photo]]></category>
		<category><![CDATA[Wikimedia Commons]]></category>
		<category><![CDATA[digiKam]]></category>
		<category><![CDATA[KIPI]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[upload]]></category>

		<guid isPermaLink="false">http://www.gpaumier.org/blog/?p=297</guid>
		<description><![CDATA[For several years now, I have been a photographer for Wikimedia Commons. Commons is actually the reason why I became interested in photography, and why I bought a DSLR camera and various lenses. And I have ended up taking a lot of pictures.

The problem when you take a lot of pictures is that the time you need then to process and upload them grows exponentially. Besides, if you want to upload your pictures to several platforms (say, Commons, flickr and your blog), you have to deal with the specifics of each website. It would be much simpler and faster to describe, tag, classify, geotag the pictures only once (using an appropriate batch-editing tool) and then to have each website extract the metadata, or to use an upload tool that extracts them automatically. <a href="http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<div id="attachment_319" class="wp-caption alignright" style="width: 140px"><img class="size-full wp-image-319" title="digiKommons" src="http://www.gpaumier.org/blog/wp-content/uploads/2009/09/digiKommons1.png" alt="digiKommons1 digiKam, the perfect tool for Wikimedia Commons photographers?" width="130" height="375" /><p class="wp-caption-text">From your computer to Commons using digiKam</p></div>
<p>For several years now, I have been a photographer for Wikimedia Commons. Commons is actually the reason why I became interested in photography, and why I bought a DSLR camera and various lenses. And I have ended up taking <em>a lot</em> of pictures.</p>
<p>The problem when you take a lot of pictures is that the time you need then to process and upload them grows exponentially. Besides, if you want to upload your pictures to several platforms (say, Commons, flickr and your blog), you have to deal with the specifics of each website. It would be much simpler and faster to describe, tag, classify, geotag the pictures only once (using an appropriate batch-editing tool) and then to have each website extract the metadata, or to use an upload tool that extracts them automatically.</p>
<h3>Wikimedia Commons</h3>
<p>So, on the one hand, you have <strong><a title="Wikimedia Commons" href="http://commons.wikimedia.org">Wikimedia Commons</a></strong>, a repository of freely-licensed multimedia files (photos, maps, diagrams, sounds, videos, etc.). It is a project of the Wikimedia Foundation, from which uploaded files can be used across all Wikimedia projects in all languages, including the famous encyclopedia Wikipedia.</p>
<p>Wikimedia Commons contains over 5 million files, the overwhelming majority of which have been contributed by volunteers. Such a large amount of files makes it mandatory to properly:</p>
<ul>
<li> describe what each work is about</li>
<li>identify the author and the copyright status of each work</li>
<li> classify each work in order to be able to find it later and to manage such a large collection.</li>
</ul>
<p>Besides these requirements, it is also considered a good practice to <a title="Commons - Geocoding" href="http://commons.wikimedia.org/wiki/Commons:Geocoding">geotag your pictures</a> (if applicable), i.e. to indicate the geographical location of where the picture was taken.</p>
<h3>digiKam</h3>
<p>On the other hand, there is <strong><a title="digiKam" href="http://www.digikam.org">digiKam</a></strong>, a <a title="FLOSS" href="http://en.wikipedia.org/wiki/Free_and_open_source_software">FLOSS</a> &#8220;<a title="digital asset management on Wikipedia" href="http://en.wikipedia.org/wiki/Digital_asset_management">digital asset management</a>&#8221; application whose special features allows to annotate, classify and catalogue a large media library, although it provides some very handy editing and post-processing tools as well. digiKam uses the <a title="KIPI plugins" href="http://www.kipi-plugins.org">KIPI plugins</a>, which provide handy features such as batch editing or export modules to a variety of websites, including <a title="Export from digiKam" href="http://maketecheasier.com/use-digikam-export-photos-flickr-picasaweb-and-facebook/2009/09/14">Flickr, Picasa and Facebook</a>. The 4th beta release of digiKam 1.0 was <a title="digiKam 1.0 beta4 announcement" href="http://www.digikam.org/drupal/node/477">recently released</a> and the official 1.0 release is <a title="digiKam release plan" href="http://www.digikam.org/drupal/about/releaseplan">planned for late October</a> this year.</p>
<p>I won&#8217;t go through <a title="list of features of digiKam" href="http://www.digikam.org/node/341">digiKam&#8217;s impressive list of features</a>; instead, I will focus on those that make digiKam a very powerful tool for Wikimedia photographers.</p>
<h3>The perfect combination?</h3>
<p>So let&#8217;s take a quick look at the features digiKam offers that would be handy for people who want to contribute their pictures to Wikimedia Commons:</p>
<table style="font-size: 100%;" border="0" cellspacing="1" cellpadding="1" align="center" summary="Comparison of Commons recommendations and digiKam features">
<tbody>
<tr>
<td><em>Commons requires or recommends&#8230;</em></td>
<td><em>digiKam offers&#8230;</em></td>
</tr>
<tr>
<td>copyright information (author and license)</td>
<td>full metadata read/write support, including Author and Copyright fields</td>
</tr>
<tr>
<td>multilingual descriptions for each file</td>
<td>multilingual descriptions since digiKam 1.0, with appropriate language codes</td>
</tr>
<tr>
<td>classification with hierarchical categories</td>
<td>classification with hierarchical tags</td>
</tr>
<tr>
<td>geotagging<sup class='footnote'><a href='#fn-297-1' id='fnref-297-1' onclick='return fdfootnote_show(297)'>1</a></sup></td>
<td>geotagging (automatically using GPS data or manually using Google Earth)</td>
</tr>
</tbody>
</table>
<p>So, what&#8217;s missing? Well, you can do a lot of stuff with digiKam to prepare your pictures before they&#8217;re uploaded to Commons. Yet, you still have to upload them manually, or using an external tool such as Commonist. And even if you have been spending days to annotate your pictures, describe them in several languages, geotag them, etc., well, all this information remains in the image metadata. Neither Commonist nor MediaWiki knows how to extract these metadata meaningfully (yet); as a consequence, you have to redo all the work when uploading each file to Wikimedia Commons. The Ford Foundation recently <a title="Ford multimedia usability grant" href="http://wikimediafoundation.org/wiki/Press_releases/Wikimedia_Ford_Foundation_Grant_July_2009">awarded a $300,000 grant</a> to the Wikimedia Foundation in order to improve the usability of the upload process. I expect some work will be done regarding the extraction of metadata from files. Yet, when uploading a large number of files, it would be more convenient to provide a standalone desktop upload tool like Commonist. Or&#8230;</p>
<p>What would really be neat is <strong>an integrated export module to Wikimedia Commons in digiKam</strong>; not only would it serve as a batch upload tool, but it would also read all the metadata and create the file description pages accordingly. A few weeks ago, I contacted the main developer of digiKam in order to discuss the possibility of implementing such an export module. He showed interest in this project even if he didn&#8217;t have the time to code it himself. As a consequence, I have initiated a <a title="KIPI brainstorming page" href="http://commons.wikimedia.org/wiki/User:Guillom/KIPI">roadmap and brainstorming page for the plugin</a>.</p>
<p>Feel free to contact me if you&#8217;re interested in helping implement such a plugin.</p>
<h3>Notes</h3>
<div class='footnotes' id='footnotes-297'>
<div class='footnotedivider'></div>
<ol>
<li id='fn-297-1'>I recently noticed a <a title="Geocode users on Commons" href="http://commons.wikimedia.org/wiki/Commons:Geocode_Users?withJS=MediaWiki:Geocode_Users.js">JavaScript tool allowing users to geotag themselves</a>, using a map from OpenStreetMap. This is exactly the kind of tool I would like to have for pictures; I can&#8217;t understand why it exists for users, but not for media files. <span class='footnotereverse'><a href='#fnref-297-1'>&#8617;</a></span></li>
</ol>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
