Archive for the ‘MediaWiki’ Category

English Wikinews adopted the usability beta as default

Friday, October 30th, 2009

Wikinews

Earlier today, English Wikinews adopted the usability beta as a default interface. The usability team is thrilled that en.wikinews community has reached the consensus to be the first adopter of the usability beta as default. We will continue enhancing the interface to simplify and make it easy to navigate and edit.  Our sincere appreciation goes to the entire en.wikinews community for embracing our work. It is a great day for the usability team. We feel blessed.

Naoko Komura on behalf of the entire usability team
Program Manager, Usability Initiative

Google experiments with new ways to search Wikipedia

Monday, October 26th, 2009

The good folks at Google Custom Search, in cooperation with experienced Wikipedian Mathias Schindler, have developed a “Google Custom Search skin” for Wikipedia that can be activated by following these instructions. In addition to using Google to search for Wikipedia articles, it makes it possible to search linked Wikipedia articles, as well as the content of linked external websites, using a simple tabbed interface. See the post at the Google Blog for more information.

This is a community initiative, not an official new feature developed by the Wikimedia Foundation, so we make no guarantees of any kind for its operation. It does show how much bottom-up innovation is possible thanks to Wikimedia’s open APIs and scripting interfaces. We’re very happy that Google has built this alternative new way to search Wikipedia. Please provide feedback below, or to the Google Custom Search team here.

Erik Moeller
Deputy Director, Wikimedia Foundation

Usability Beta Status

Monday, September 14th, 2009

Here’s a brief update on the status of our recently launched usability improvements.

Since the launch of the beta invitation to the first set of usability improvements on August 6th, about 173,000 people tried out the beta and about 134,000 people continue to use the beta as of September 12th.

Beta retention rate is interpreted roughly 77%. These numbers are aggregation of all Wikimedia projects in all available languages. If we look at the retention rate by project or by language, the number varies significantly. For example, the beta retention rate of English Wikipedia is 82% and Spanish Wikipedia is 80%, while the beta struggles to retain beta trial users of the language communities such as Japanese and Korean at the retention rate of 59% and 54% respectively.

We are reviewing the survey feedback and trying to isolate specific issues of languages whose retention rate is below average. If you are curious about how the beta opt-in and opt-out look like at daily or weekly basis, you can visit the preference statistics page. Here is the example link to English Wikpedia. Just change the language prefix or project name to get to the project of your preference.

Naoko Komura
Program Manager
Wikipedia Usability Initiative

A quick update on Flagged Revisions

Wednesday, August 26th, 2009

One of the wonderful characteristics of Wikimedia’s wikis, including Wikipedia, is that every change ever made to a page is recorded, back to the very first version (compare, for example, the first version of the article about chess with the most recent version of the same article). This characteristic also makes it possible to assign quality assessments to specific versions, thereby giving our readers greater transparency about the perceived current or past quality of an article.

A very powerful software feature called Flagged Revisions makes it possible to systematize such quality assessments.  It’s been in production use in many of our wikis for more than a year now, including the second-largest Wikipedia, the German language edition. Fundamentally it’s a very flexible feature, and different project communities (the German Wikipedia, the English Wikibooks, etc.) can come up with configurations that suit their needs. By means of our public issue tracker, they can then request from the Wikimedia Foundation that such configurations be turned on.

Even though we’ve made no official announcements about this, you may have seen media reports that Flagged Revisions will soon be enabled in the English Wikipedia. Indeed, there is a specific proposal that was developed by the English Wikipedia community, entitled Flagged protection and patrolled revisions. It’s a very thoughtful proposal that attempts to balance the desire for higher quality, and more systematic assessment thereof, with the immediacy of Wikipedia as it exists today, and was supported by a large majority of interested Wikipedia editors. The idea behind this proposal is to allow regular contributors to systematize a first, basic assessment of all edits by new contributors. However, this assessment will be purely for informational purposes to the reader: a reader will see whether or not the version of an article they look at has been patrolled, and if not, whether a prior patrolled version is available.

Only in a small percentage of cases, we would require changes to be patrolled before becoming the default view for readers. The proposal is to do so initially in the case of articles at high risk of vandalism, including high risk biographies of living people, where false information can do the most serious harm to an individual.

A popular media narrative of this proposal (in the cases where it has been reported roughly correctly to begin with) is that it represents a “clamping down” on Wikipedia’s open editing process. That is nonsense. It is presently the case that many high-risk articles are completely uneditable by new contributors, which is referred to as page protection. For example, as a completely new user, you are not able to alter the article about Barack Obama. These kinds of protections of high-risk articles have been common for many years now. If the proposed model works as intended, it will actually allow us to open up many articles for editing which are currently protected from being edited. Edits will have to be patrolled, which is clearly a step up from edits not being possible at all.

It is true that some implementations of Flagged Revisions are more conservative than that. Any edit in the German Wikipedia by a new or unregistered user has to be patrolled before becoming visible to readers. This is definitely not the case in the proposed English Wikipedia configuration. We believe in letting our communities experiment with different approaches in an attempt to find the right balance.

A test wiki for the English Wikipedia configuration has just been set up in the Wikimedia Labs, and we’ll be importing articles from Wikipedia soon and make a broad call for testing. It’s important for us to get this right – we want to make sure that we don’t make Wikipedia harder to use, for our readers or our editors, in the process of deploying this functionality. That said, we hope to be able to deploy Flagged Revisions in production use on the English Wikipedia within 2-3 months.

From Wikimania in lovely Buenos Aires,
Erik Moeller
Deputy Director, Wikimedia Foundation

[UPDATE 8/26] This post originally said that all biographies of living people would be “flagged protected”. This is not correct. The current proposal is for for articles that are currently under normal mechanisms of protection (where new and unregistered users cannot edit) to be eligible for the new protection model, which allows for more open editing. I apologize for the confusion; thanks to Sage Ross for the quick correction.

The abc’s of Usability!

Wednesday, July 29th, 2009

Basket of berries, remixed by Parul V; photos by Dinowx, Siegert, and Yuval Y (CCBYSA)

Hopefully by now you’ve had a chance to try the new skin ‘Vector‘ that the Usability Team has implemented as part of our first release, also known as Acai!  If you haven’t yet, we invite you to check it out by going to Appearance > Skin in your preferences and selecting ‘Vector’.  As you play with the new skin and enhanced toolbar, the Usability Team is looking forward to our next release – codename Babaco – the next alphabetical tropical fruit in what we expect to be a delicious series.

We hope to continue adding features to enhance the editing process – including but not limited to further toolbar enhancements; dialogs for the creation of links, tables, and references; and tools to aid in navigation of article content during editing.  Our research, design, and development depends on feedback from users, community members, and interested parties like you.  We invite you to take a look at our work and if you have any opinions, praise, concerns, or criticism, please let us know here.  We look forward to hearing from you!

Parul Vora, Wikimedia Usability Initiative

Let’s tango!

Friday, July 17th, 2009

Reference icon for the enhanced toolbar

The open source movement is not only about software and knowledge base creation. There are active movements in user interface design as well. tango! is one of the neatest projects in design collaborative world, contributing in the creation of open source software such as Open Office and Ubuntu. We, the usability team, also benefit from such open source design projects which allow us to reuse their icons by modifying to meet our needs. For example the icon on the right is the new reference tool icon which can be found in the enhanced toolbar. It is the reuse of Gnome Desktop icons from Wikimedia Commons.

The first set of usability enhancements, new tab layout, enhanced toolbar, and reorganized search page, are now available in MediaWiki projects except for right-to-left language wikis such as Arabic and Hebrew. The support for right-to-left languages should be available in a few weeks, so just hang in there. We welcome you to try out the usability enhancements by going into your preferences and enable ‘Vector’ and the enhanced toolbar from Appearance and Editing menus.

I hope you find the new interface easy to interact. Let us know your feedback in the discussion page of the most recent release page.

Naoko Komura
Program Manager, Usability Initiative

Brewing ideas for the Wikipedia usability initiative

Tuesday, June 2nd, 2009

The usability team has been translating the usability study into a new design and software for the last four weeks. The current focus is to implement easy improvement to overall usage of Wikipedia with the focus of editing interface in the next three months. The proposed skin by the usability team, Vector, will have streamlined tab layout, so that users will not lose the state of reading or editing whether in articles or in discussion pages.

Another usability improvement we are working on is the action-grouped toolbar, which hides the overwhelming number of tool icons which are not being used by novice users, but they are available for power users in the expanded mode. Lots of clutters will be removed from the editing interface.

You can see some of design mock-ups from our project page. Some of these proposed design concepts will be staged at the prototype environments this month and for any future improvements. (The action-based tool bar will not be seen on prototypes till June 8.)

If all goes well, these new features will be available from a user preference configuration early July. In the subsequent release in August, additional navigation aids are in the plan. We will be sharing the product feature at our project page in coming weeks. We look forward to your feedback.

Naoko Komura
The Wikipedia Usability Team

The Wikipedia Usability Initiative is still hiring.

Tuesday, May 12th, 2009

The Wikipedia Usability Initiative has extended the application deadline for the Software Developer position till May 30th. We are recruiting two candidates for this position. Both local applicants to the San Francisco Bay Area and remote applicants are encouraged to apply. Please help spread the word.

http://wikimediafoundation.org/wiki/Job_openings/Software_Developer_(project)

Naoko Komura
Wikipedia Usability Initiative

Usability Study Results (Sneak Preview)

Friday, April 24th, 2009

Usability Study Sessions

The Wikipedia Usability Team has finished up their analysis of the User Experience and Usability Testing conducted this past March with Bolt | Peters!  As noted, please expect a full report on our project page soon.  While we are getting all of our i’s dotted and t’s crossed, we wanted to share with you some of the major themes and findings & successes and failures.

Outstanding

“Usually it’s the most information in the easiest spot to access.  It always looks very well put together….it boggles my mind how many people can contribute and it still looks like an encyclopedia.” – ‘Galen’
“I like Wikipedia because it’s plain text and nothing flashes” – ‘Claudia’
“It’s always one of the first hits on Google” – ‘Grace’

If there was one thing that was consistent and unanimous across our study participants, it was the assessment that Wikipedia is an incredibly valuable information resource whose accessibility is unparalleled.  Aside from its value as a reference, a time and lifesaver, and an up to the minute news resource, participants also praised it’s simplicity, coherence, and breadth.  Also, an extra thanks to Google, for showcasing just how referenced Wikipedia articles are – consistently making their links one of the top hits – our users count on that!

Room for Improvement

“Rather than making a mess, I’d rather take some time to figure out how to do it right.” – ‘Dan’
“Where are the rules?……I don’t really want to read all of this other stuff about what I”m supposed to do.” – ‘Grace’

All of our participants are Wikipedia readers, but had little or no experience with editing.  Generally the editing process was not a warm and welcoming one.  Before subjects even hit the ‘edit’ or ‘edit this page’ buttons, they voiced concerns about the rules, proper etiquette, formatting, and were naturally conscientious of and inhibited by maintaining the community expectations.  When a few of them attempted to find answers to their questions about rules and etiquette, they were overwhelmed with the amount of information and documentation they encountered.

“ [I felt] kind of stupid.” – ‘Galen’
“It looks all jumbled and crazy…I’m going down to the stuff that looks like it makes sense.” – ‘Tito’
“I’m not a programmer.  I know the letters PHP.” – ‘Seamus’

Once within the editing environment, most subjects commented on the illegibility of the hybrid Wiki syntax and article content – the more complex the article, the more exaggerated the response.  When users made it past their initial reactions, navigating around the syntax to perform basic word processing tasks (correcting a typo, inserting a block of text, bold and italics formatting) proved less problematic than finding a particular section, adding references, using tables, creating and naming links.  But not even our youngest and most computer savvy participants accomplished these tasks with ease.

“It’d be nice to have a GUI, so you could see what you’re editing.  You’ve made these changes and you’re looking at it, and you don’t know how it’s going to look on the page.  It’s a little clumsy to see how it’s going to look.” – ‘Bryan’
“On a blog it looks like the real page when you look at it.  I have a hard time looking at this and going back to the way it actually is.  I’m trying to correlate what’s on the real page.” – ‘Saurab’

Aside from feeling confused by the “code”, “computer lingo”, and “html”, subjects could not correlate what they were seeing within the edit box to what they saw on the article page.  Most subjects opened a separate browser window to view the static article as they were making their changes and used preview and save before they had finished their work to monitor their editing progress and results.

Fail

“[This is] where I’d give up.”  – ‘Shaun’
“ There sure is a lot of stuff to read.” – ‘Dan’

Yes, we can admit it.  In some ways it seems, we are failing our users.  The tasks that users most often failed to accomplish were adding references, creating a new article, and successfully finding help.  When adding references, users questioned where and how to enter their sources.  Once they established a location, they struggled with both the interface and the complex wiki syntax.  Several users, while scanning pages to try to figure out how to create a new article, saw ‘create a book’ and thought “add a wiki page” was what they were looking for.  In both adding references and new articles, some users consulted help.  Help proved to be quite a labyrinth, where the cheat sheet was one source of shining light.

Check out this highlight video (in English only for now) on Commons:
Editing Wikipedia Makes Me Feel Stupid
Explain the Editing Process to Me
I Can’t Tell What This Really Looks Like

Though we cannot tackle the full scope of issues that our study participants brought up, brought to our attention, and validated, it was an eye-opening and learning experience for the whole team.  The study informs us as we take a further look at the most effective changes we can make to lower these barriers for potential Wikipedia editors.  We look forward to sharing our complete report and initial ideas with you – stay tuned!

Parul, Wikimedia Usability Initiative

Usability Study

Thursday, April 9th, 2009

Usability study participants
The usability team, and Bolt|Peters, a user experience research firm in San Francisco, conducted a usability study from March 24th to March 26th. The objective of this study was to identify common interface barriers new editors face by asking participants to conduct simple editing tasks in Wikipedia.

We conducted two types of studies: in-person and remote. Ten participants (three are pictured at the right), who were selected based on their experience level of editing Wikipedia, age group, and gender, were invited to the lab for a one hour study and an interview. Five participants were recruited in real time from the Wikipedia site for remote testing. We asked them to conduct the same tasks we did for in-person study.

The analysis of the results is currently underway, and Parul will be releasing the summary on our project page soon.

One thing I want to share with you before the summary is available is that we received lots of kudos and love from our participants about Wikipedia. People just love Wikipedia. :-)

Naoko Komura, Program Manager of the Wikipedia Usability Initiative



Fundraising FAQ    ·    Donor privacy policy    ·    Tax Deductibility of Donations    ·    Planned Spending Distribution