Content monitoring and moderation

Once the application is released and user numbers pick up, some users will inevitably post spam or otherwise inappropriate content. While screening every single contribution can be a full-time job, most user-generated content systems adopt a more lightweight approach where monitoring and moderation is delegated to the community. Following this approach, the CloudBank app now has functionality for users to flag content:

1) Someone might find this entry inappropriate


2) Click in the Menu button to bring up menu options


3) Hit the Flag entry menu option and tick a reason


4) The item is now flagged for everyone to see (red flag top right corner)


5) The flagged item is easy enough to spot for an administrator...


6) ...who then can look at the entry, edit it, reset the flag or delete it from the system.

Updated application and support docs

Please update CloudBank on your mobile phone to version 1.1 as we made some changes to the public API that break the prototype you might have currently installed.

The mobile user guide, API specification and RSS feed have also changed:

CloudBank app v1.1
http://itrg.brighton.ac.uk/download.php

Mobile user guide v1.1
http://itrg.brighton.ac.uk/cloudbank/files/CloudBank_Mobile_User_Guide_v1.1.pdf

CloudBank Public API v1.1
http://itrg.brighton.ac.uk/cloudbank/files/API_v1.1.pdf

New CloudBank RSS feed
http://itrg.brighton.ac.uk/cloudbank/rss.php

User groups or Tags?

One of our aims was to ready the system for use in different contexts and thereby make it more sustainable in the long term. To do this we planned to implement 'user groups' which would allow the creation of distinct learning spaces, e.g. to allow a group of students to start with an empty word list and only see content contributed by group members.

On closer inspection however, user groups have a considerable admin overhead - and they are not the only way forward to achieve separate content pools. A light-weight alternative are tags or 'hashtags' or 'channel tags'. Tags have no admin overhead at all and in many ways seem a more elegant and flexible solution.

On August 23, 2007, the Twitter hashtag was born. Invented by Chris Messina, the first tweet with a hashtag read as follows: “how do you feel about using # (pound) for groups. As in #barcamp [msg]?”

Source: The Short and Illustrious History of Twitter #Hashtags

Drawing up a list of real world problems / use cases and spelling out how these would be addressed with user groups or tags, we found that most problems could be addressed with both solutions (the main difference beeing the admin overhead for user groups). The only case not covered by tags is when groups want to keep their content private, however, this is balanced by the difficulties of usergroups to share their content with others. It all boils down to tag-based systems being by default open while user-groups are by default closed (even if you can easily join). Confronted with this almost philosophical questions we decided to implememnt a tag-based solution.


In order to cover all use cases, we need to be able to show all content, show only content from one or more subsets and exclude content from one or more subsets. Consequently the Settings dialog has these options:

• Show only these tags: Only content tagged with these tags will be visible when browsing (e.g. group tag). Leave empty for all content.
• Don't show these tags: Exclude certain tags when browsing (e.g. sex, religion). Leave empty to not exclude any tags.
• Default tags for my posts: Add these tags by default (e.g. group tag). Leave empty for no default tags in your posts.

Here's a use case:
A teacher at the ISC wants his students to start from scratch with an empty word list. He thinks up the unique tag ISC2010 and instructs his students to call up the Cloudbank Settings dialog, where they enter the tag as an inclusion filter('Show only these tags: ISC2010'). In addition, students enter the same tag as their default post tag('Default tags for my posts: ISC2010'). As a result, all content posted by students is tagged with ISC2010 and they only see CloudBank content tagged with ISC2010.

New app, tools, blog

You may have noticed the new menu bar just below the blog title? It sums up the latest development spurt to get CloudBank ready for prime time - as a sustainable and widely-used mobile language learning tool.

We now support dynamic user groups, not through a boilerplate user-group implementation but through rather sophisticated tagging support that enables teachers to set up ad-hoc content pools and gives learners fine control over what they see.

We addressed the issue of spam, offensive and wrong content by enabling users to flag items for review by a cloudbank administrator or editor (e.g. a teacher using the system)

We added context-sensitive online help to the mobile application for novice users, as well as an about screen and a settings menu.

We created an admin panel which enables non-technical staff to edit, follow up flagged items and delete content from the database.

Last but not least we prepared our shiny new Android phones for action, by un-doing the useless t-mobile default configuration, setting up reasonable settings and homescreen and installing the new Cloudbank app. This may sound like childs play, but in fact I had blisters on my fingers after configuring 8 phones via touch screen!

I'll be explaining each of these points in more detail over the coming days. But now it's off to deliver the phones to the ISC so that we finally can get on with our evaluation...

Phones are here - woo hoo

It's been a long battle but here they are, neatly lined up and charging. Can't wait to see them used in the field with international students filling up the CloudBank content repository! It's going to be very interesting...

Status update

So what happened in the first few weeks of our project extension?

In a series of planning meetings with Tom Ottway from the ISC we talked about possible ways to integrate the CloudBank app with formal language provision at the ISC. While CloudBank was developed in first place to support informal learning, the discussion showed that there are many engaging ways how the app could be used in formal language courses, ranging from field trips and outdoor missions to competitions where students collect language- and culture-related material and then analyse and talk about it in whole-class, group- or one-on-one discussions.

An interesting aspect in these discussions was that CloudBank not only supports language learners, but also helps teachers to better understand their students' requirements as they can examine the collected material and deduct where their students have difficulties. We never thought of it this way around, but it is very interesting and once again confirms the value of involving stakeholders at all stages in the wider development process!

Apart from usage scenarios we also talked about practical issues and agreed a meeting with ESOL teachers at the ISC. Initially we also planned to meet the students to be involved in the evaluation but eventually dropped the idea as it might unnecessarily narrow down or restrict their use of CloudBank if confronted at the outset with our own ideas of how the system should be used.

In our meeting with ESOL teachers at the ISC, we first gave a short presentation of CloudBank and then discussed the planned evaluation with teachers, answered technical and conceptual questions and further explored potential scenarios how students could use the application. The teachers we talked to seemed very interested in CloudBank and were keen to get their hands on a mobile device to play around with it!

And this brings me straight to the sad story of trying to buy the mobile phones for our evaluation. I fear this whole post might turn into a particularly nasty rant if I go into the details, so let's just say it's not only the university, but also the phone companies who have mind-bending rules and regulations that hamper their operations and frustrate staff at either end. I better stop here.

Rolling on...

Yes, we're one of the few lucky Rapid Innovation projects to receive follow-up funding from JISC! We'll use the funds to carry out a pedagogical evaluation of CloudBank in co-operation with the International Student Centre (ISC) at the University of Sussex. This will strengthen any future bids to develop the system further and thereby address one of the most important aspects of sustainability: funding.

So what do we plan to do?

Based on preliminary talks with Tom Ottway, Head of English at the ISC, we'll use CloudBank in two consecutive language courses with international students. A big hurdle for any mobile learning project is the availability of mobile devices, and to this end we'll purchase a set of cheap Android devices and make them available to students together with with pre-paid internet access. The pedagogical evaluation will then be carried out in collaboration with ESOL teachers at the ISC.

Before we can start however, we need to ready the system for use in a production environment. Currently all user-generated content ends up in the same pool, however, in order to use the system in different contexts and with different user populations it is necessary to introduce the notion of user groups or content channels. This will allow the creation of distinct learning spaces with separate content pools for specific user groups. As a knock-on effect, we also need to update the web interface, technical and end-user documentation.

Finally, the evaluation will yield plenty of material to talk about, and we're planning to do this at the mLearn 2010 conference in Malta to maintain momentum and ensure continued international interest in CloudBank.