Guillaume Paumier's weblog open knowledge, design & technology
  • Home
  • About
  • Wikimedia
  • Design
  • Graphics
  • General
  • KDE
  • RSS Feed

Ten features that would dramatically improve Wikimedia Commons

By
Guillaume Paumier
– June 30, 2009Posted in: Wikimedia Commons
Logo of Wikimedia Commons

Logo of Wikimedia Commons

About two years ago, I said “Commons may be the next coolest project, as soon as developers find the time to improve its usability to make it more user-friendly”. Sadly, Wikimedia Commons hasn’t evolved much in terms of usability since then. MIT’s Technology Review recently published an article about improvements to come regarding the management of video content on Wikipedia and Wikimedia websites. I heard a lot of people say: “Good, but what about pictures?” Some technical improvements described by the Technology Review will be useful for both images and videos, such as the media and upload wizard currently developed by Michael Dale. However, Wikimedia Commons still needs many little (or big) features that would dramatically improve its user-friendliness.

Browsing & reusing

  1. Automatic localization: Websites such as Wikimedia Commons and meta-wiki host content in various languages and have a multilingual audience. These multilingual wikis should automagically detect the locale of the user’s browser and use it as language of the interface, especially for unregistered users. As for users with an account, their browser’s locale should be set as the default language in their preferences.
  2. Usage-centric page layout: It’s all very nice to know that such image is a “retouched picture” or that such diagram was “made using Inkscape”. But I think what most of the users want to know is: how to use the picture (in Wikimedia projects or elsewhere) and how to download it (using the best resolution available). Many people use the right-click-save-as method to save pictures from the Internet. If they do that on Commons, they will only save the low-resolution preview. There should be a big button « Download high-res », as well as snippets of code to embed a file with proper attribution.

Metadata

Full metadata support is the cornerstone of many other features. EXIF is probably the most known type of metadata, but there are also others such as IPTC or XMP.

  1. Pull metadata from files on upload: this idea is not a new one, yet it hasn’t been implemented. A fair amount of photographers add a lot of metadata to their files: author, description, copyright information, geotags, keywords, etc. and it is extremely cumbersome to have to redo all the work by hand during the upload.
  2. Store metadata in a database to make search and attribution easier, especially: description, license, media type (photo, diagram, map, etc.). It should be connected to the MediaWiki API to allow for easy extraction of these data.
  3. Push metadata to files on download: In the field of publishing, storing credit information directly into the file’s metadata is strongly recommended and is a standard practice to avoid losing track of it.

Related open bugs

  • bugzilla:6672: EXIF orientation not used (rotation from digital cameras)
  • bugzilla:3361: Image author, description, and copyright data saved in EXIF fields
  • bugzilla:16956: Show IPTC metadata on image description page
  • bugzilla:657: Pull copyright metadata from files on upload
  • bugzilla:11484: Include ISO rating in abbreviated exif metadata.

Editing

  1. Built-in basic editing features (lossless rotate, crop) and ability to save under another name (i.e. for crops). Similarly, a built-in geocoding feature using OpenStreetMap. Geocoding images means attaching geographic information about the place where the work was made. This may be made easier by the current initiative to integrate OpenStreetMap with Wikimedia projects. And of course it should save the coordinates as metadata.

Rating

  1. Some sort of community-managed rating feature; as someone said elsewhere, “Commons is a depository, and depositories are expected to host lots of junk”. A rating feature would allow the best of Commons to be presented first during the search, and junk to be presented last.

Searching

With currently more than 4.6 million files (and counting), it is becoming increasingly important to improve the search features of Wikimedia Commons.

  1. An “advanced search” feature similar to flickr’s. It should be possible to search by media type, by license, and to add toggles such as “safe mode” (explicit content) or “personality rights”.
  2. Multilingual search: Files on Commons are ordered in hierarchical categories, using English as lingua franca. If you want to find a file, you have to search in English. I imagine it is possible to use some dictionary (coupled to the language detection) to give good results for a search in any language.
  3. Google-Images-friendliness. A lot of people use Google Images to find pictures, but images from Wikimedia Commons rarely appear in these results (unless they are used on a Wikipedia page).

Note: All these ideas are given from a user point of view; their technical feasibility has to be assessed by a MediaWiki-literate developer.

Tags: MediaWiki, metadata, usability, Wikimedia, Wikimedia Commons

6 Comments

  1. Frank Schulenburg
    Posted June 30, 2009 at 6:12 PM

    Thanks Guillaume, all of these are really good and helpful ideas. If you needed to priorize — which 3-4 features would you rate as having the biggest impact? Thanks again, Frank

  2. Siebrand
    Posted June 30, 2009 at 10:02 PM

    bugzilla:11484 was fixed some time ago.

  3. Longbow4u
    Posted June 30, 2009 at 10:18 PM

    Hi Guillaume, hi Frank,
    I agree that Wikimedia Commons needs some improvements. I would say a better search function is the most important thing, e.g. an image search which looks for information in the “Description” field. This does not need really new development. There was the “Mayflower Search tool” http://toolserver.org/~tangotango/mayflower/search.php?j=1&q=Gie%C3%9Fen&t=r which used an index. Unfortunately, the index file was last updated by tangotango on 24th October 2007 (!), so most of the new files (e.g. Bundesarchiv material) is not found.

    Longbow4u

  4. Andrew Turvey
    Posted June 30, 2009 at 11:45 PM

    Good list!

    One thing I’d add is making the upload process easier. Compare Flickr or facebok and you instantly see how far behind the curve we are falling.

    Look forward to the one for Wikipedia too!

  5. pfctdayelise
    Posted July 1, 2009 at 3:43 AM

    Nice list. Although I think the Google Images thing has improved a lot now from what it used to be (virtually invisible).

    I have written a couple of posts which cover a lot of similar/related ground as here:
    * http://brianna.modernthings.org/article/117/the-coming-challenges-for-wikimedia-commons
    * http://brianna.modernthings.org/article/40/top-10-software-extensions-wikimedia-commons-needs-in-2008

    I think a major thing at this point is improved workflow (license review, deletion processes, categorisation, descriptions translation). As you once said, and I completely agree, a major problem at Commons is that the content is growing much faster than the community. This does seem to cause systemic behavioural problems because the current community just doesn’t have a hope of dealing with all the work. So tech improvements that make it possible to deal with a greater volume of work by fewer people or in a shorter time, should hopefully filter through to less community-imposed complexity. To some extent. Not completely, because Copyright Is Hard (TM).

  6. Kolossos
    Posted July 22, 2009 at 8:54 PM

    I would say the support of high resolution images would be a very nice feature.
    I mean >40 Megapixels or so. We have excellent panoramas and scans of old maps with this size.
    The download needs very long also with a fast internet connection. The solution could work with tiles (like google maps ans Openstreetmap work)

    So a non-optimized prototype how it could looks is here:
    http://toolserver.org/~kolossos/zoom-image/zoom-ol.html

    I’m a fan of http://gigapan.org/ that shows that we can get low-prize highres images.

    Greetings

Comments Closed

Comments are closed. You will not be able to post a comment in this post.

  • Welcome
    Guillaume PaumierI am a French physicist, photographer & Wikimedian, currently living in San Francisco, California, where I work for the Wikimedia Foundation, the non-profit that runs Wikipedia. Read more.
  • Elsewhere
  • See also
    Strelitzia reginaePhoto gallery
    Microsystem under a microscopeunfoldscience: scientific communication
    books on a shelfJournal en français
  • Latest posts
    • A set of carton boards of several colors, each marked with a specific time and symbol WikiSym 2010
      28 July 2010 1:46 AM | 6 Comments
    • Observers behind a semi-transparent glass, looking at a user on a computer, guided by a facilitator Wikimedia Multimedia UX testing videos
      23 July 2010 10:29 AM | 4 Comments
    • Close-up on a yellow rubber duck, sitting on on a black notebook Wikimedia at KDE Akademy 2010
      22 July 2010 10:28 AM | 3 Comments
    • Screenshot of the wikipedia.org portal; The Wikipedia logo is surrounded by the 10 largest language editions, then languages are listed in size groups State of the language selection in MediaWiki and Wikipedia
      26 June 2010 12:15 AM | 4 Comments
    • Facebook logo using the twitter visual identity Why I’m not quitting Facebook…
      31 May 2010 9:16 PM | 2 Comments
  • RSS Journal de Guillaume Paumier
    • Wikipedia vu par des enfants de 8 à 11 ans
    • Retour sur l’incident technique de Wikipedia le 24 mars 2010
    • Stratégie de développement logiciel: Wikimedia & MediaWiki

About Arras Theme

Unless otherwise noted, the content of this website is available under the Creative Commons Attribution Share alike license. See Licensing and reuse terms.