OTRS & the permissions problem

Screenshot of the OTRS interface

The Wikimedia Foundation uses a software package called OTRS for a variety of purposes. OTRS volunteers are chosen from various Wikimedia projects, usually if not always admins, as the OTRS chores often require checking of deleted edits.

If you manage to dodge the inbound links on Wikipedia:Contact us, you’ll eventually reach an email address. Most of the addresses on that form represent OTRS queues. So one function is for answering queries from the public. Other similar functions include answering press queries, fundraising queries, and legal queries.

One function dear to the heart of many Wikimedia Commons users is that of permissions. “Permissions” means forwarding emails in which an author agrees to license their work under a free license to OTRS, to act as a record of the permission being given.

Typically it would play out like this:

  1. Wikimedian goes hunting for an image for their pet topic. They find a good candidate, but it’s all-rights-reserved copyrighted or under a non-free license.
  2. Wikimedian writes a begging email to the author, hopefully using a template request. (This is important: if you only ask “for Wikipedia”, the author will probably give Wikipedia-only permission. That’s not free enough.)
  3. Author is dazzled by flattery and/or the possibility of having their image appear on Wikipedia and replies, assenting to the free license terms.
  4. Wikimedian uploads the work and forwards the email to OTRS as evidence of the license release.
  5. The Wikimedian or OTRS volunteers tag the work with a template providing a link to the relevant OTRS ticket as a reference.

Ideally this would be quite straight-forward and move along in a timely fashion, but of course it doesn’t work like that. :) Common problems faced by OTRS volunteers checking the permission queues are:

While I was at Wikimania I gave an impromptu tutorial on using Wikimedia Commons. When I’d finished and said “any questions?” I think the first one was about: what should I do if I have my friend’s photo and he just told me OK? How does that work in the context of OTRS?

I had to lamely reply that he should ask his friend to send him an email granting the permission. I would like to say “talk about an edge case!” but that is less and less true.

How can we solve this problem, of shallow verification of permissions? I say “shallow” because of course OTRS is only represents a first basic check. This is “balance of probabilities”, not “beyond a reasonable doubt”. Should someone later come along with a convincing claim to own particular images and never have given permission for them to be used, we’ll chalk that OTRS ticket up to “well, we made an effort”. We’re not checking for passport fraud…these are projects that we let anyone edit, after all. ;)

The second part of the “permissions problem” is that of longevity. What is an acceptable statement of “proof” may not be 12, 24, 36, 48 months later. Or even further into the future. And how long will those tickets be preserved? Perhaps the permissions tickets should be shipped with the database dumps? Or will WMF maintain the OTRS system for perpetuity?

Or, more likely, they will degrade with time, and slowly be deleted over time, with more and more being replaced by definitively free works. This is what’s happening with “web-sourced” free works, I think. Websites die. Even the US government department websites get rearranged and all the convenient “evidence” links die. What can we do about it?

When confronting the problem of changing Flickr permissions, it was put forward that we should have a bot or something taking screenshots of the images on Flickr showing the free license.

So, dear world, any thoughts about how to approach this vexatious problem?

18 October, 2007 • ,


Elsewhere on the web...

Commenting is closed for this article.

list of all posts, ever

find articles by tag

monthly archive

most popular articles

  1. [guest] Rethinking the Top Ten
  2. An alternative term for "User-generated content"
  3. How to use Gmail to manage high-traffic mailing lists
  4. NLA Innovative Ideas Forum audio/video now available
  5. Write API enabled on Wikimedia sites!
  6. Free as in Freedom miniconf recap + slides
  7. Templatology, an essay
  8. Top 10 software extensions Wikimedia Commons needs in 2008
  9. Is mass collaboration all it's cracked up to be?
  10. GLAM-WIKI, day one

(from the last 30 days)