Skip to topic | Skip to bottom
Home
Search:

Global
Global.VozMobCMSr1.19 - 06 Sep 2008 - 07:02 - MarkBtopic end
You are here: Global > VozMob > VozMobCMS

Start of topic | Skip to actions

VozMobCMS

This page is part of the VozMob project.

Table of content :

Project tools

CMS specs

One-Line Summary: Community Mobile Blogging with Drupal.

The idea is we are training groups of low-wage immigrant workers in LA, starting with day laborers, via partnerships with community based organizations to do digital storytelling using mobile phones (and computers). We're aiming for maximum ease of use.

requirements:

  • anonymous publishing of text, photo, audio (video less crucial at this stage, but we should make it possible anyway) from mobile phones to a newswire.

  • planned so that it's as easy as possible for mobile phone users with a wide range of models and service providers to publish (ie, probably most people would send items via SMS or MMS, but maybe via email would work best)

  • ability for mobile phone user to simply dial a number, and leave an audio clip that gets converted (to ogg?) and published to the newswire.

  • Reasonably easy to use system to allow an editorial collective to create or promote features out of newswire articles, with thumbnail images for each feature. This part (editing and publishing features) can be done via the web.

  • Also, FYI There is a team of programming students working to write java applications for phones that allow 3rd party apps. They are trying to make apps so that, for example, the end user can publish a geotagged photo to the site with just a couple of button presses. So the developers will have to coordinate with this team.

  • The initial group of users may be getting Motorala iDen phones with these apps installed, so it definitely should work with them. However, we obviously don't want to lock the CMS in with one particular phone/plan, but make it useable by as many models/plans as possible, with an initial emphasis on those that are most used by first generation immigrants in LA. We're doing a survey to find that out, over the next couple months.

Functionality Shortlist

  • Phone call --> Audio file posted to newswire. Solutions: Australia IMC has one working solution: http://melbourne.indymedia.org/pimp.php._ _See Dyne.org solution: http://lab.dyne.org/Phone2Podcast. __Research existing phone->Drupal modules. _Solution: asterisk integration. But what is best solution for getting audio files posted as nodes?_
  • Call-in interface ("Marca 1 para Espaņol. Press 2 for English." etc.) Then, add metadata. Solution: asterisk
  • SMS or email from phone --> text post to newswire solution: mailhandler. But will users send SMS to an email addy? Or to a phone number (will require gateway sms->email)
    • requires mailhandler to recognize emails sent from phones via sms. email format from the main US carriers we are dealing with include: @vtext.com, @txt.att.net, @myboostmobile.com, @vmobl.com, @messaging.nextel.com, @messaging.sprintpcs.com, @tmomail.net, @message.alltel.com, @mymetropcs.com. generic format is NNN@vtextSTOPSPAM.com, etc. where NNN is the 10-digit phone number. A more extensive list can be found at http://www.notepage.net/smtp.htm
  • Cellphone photo --> image post to newswire solution: attach to email (if phone can do this)-->mailhandler. If not, MMS? but expensive. So some users may be moving photos from phone to computer first, then upload.

Functionality Dreamlist

  • Browse all content via mobile phone
  • Cellphone video --> video post to newswire
  • Browse content via audio, numerical keypresses, even voice recognition. ("Press 1 or say 'New' to hear the most recent story. Press 2 or say 'Publish' to post a story." etc.)

Possible solutions

For text:

  • a) text posts from phones via email (with mailhandler)
  • b) text posts from phones via browser (opera for mobile, config theme to be friendly to this)
  • c) text posts from phones via chat or irc. (for example, gchat has free j2me app for many phones. but privacy concerns.)
  • d) text posts from phone via dedicated J2ME app (pro: if done right, most user friendly. con: only works for people w/app installed on handset. we have some people working on handset apps, so need to coordinate w/them in any case)
  • e) use third party commercial mobile sms service (like twitter. But privacy and content licensing concerns).
  • f) use third party speech-to-text conversion (Jott, http://drupal.org/project/jott. But english only, and privacy concerns).

For photos:

  • a) Photo posts from phones via email (with mailhandler)
  • b) photo posts from phones via browser (opera for mobile, config theme to be friendly to this)
  • c) photo posts from phone via dedicated J2ME app (pro: if done right, most user friendly. con: only works for people w/app installed on handset. we have some people working on handset apps, so need to coordinate w/them in any case)
  • d) use third party commercial mobile photo service (but privacy and content licensing concerns).

For Audio:

  • use asterisk, make it work w/drupal
  • use a third party commercial service (like odeo. but privacy and content licensing concerns.)

Near-Term Spikes

  • Workplan and timeline
  • Decision on solutions for mobile posting (what combination of drupal modules / other server side packages / third party services / handset apps)
  • Setup vserver (should start ASAP - expect 24-48 hour delay from "go" if by Koumbit)
  • Asterisk: "Call into a node" (within 2 weeks)
  • Asterisk: "Read from nodes" (next 2 weeks)
  • theme mockup and approval. Based on graphic at http://mobilevoices.net. Needs theme for web viewing and for mobile devices (some of this work can be done in parallel with the rest)
  • Clean Drupal Install
  • install dependencies (flowplayer? asterisk? ffmpeg? etc.)
  • create appropriate roles (anon viewers, registered posters, editors, administrators)
  • Necessary modules install and testing (running list here: iL8N. Views?)
  • successful text post from phone to site
  • successful photo post from phone to site
  • successful audio post from phone to site

Mobile Browsing

This section is for notes about browsing mobilevoices using a mobile phone

Accesskey Assignments / Menus

The table below is a first draft of assignment recommendations for using the numerical keypad to navigate the site on a mobile phone.

Key menu item description
1 HOME / LANGUAGE SELECT Home page / start page / language select (?)
2 PUBLISH Publish content
3 FEATURES Browse featured content (most recent feature first?)
4 NEWSWIRE Browse newswire content
5 SEARCH Search mobilevoices site
6 TERMS Terms and conditions, copyright, disclaimer
7 CONTACT contact us
8 ABOUT description of the project
9 HELP instructions

0 TOP return to top menu or go back one page

Notes

Drupal

Sourcecode

Workplan

team: mfb, omar, schock, joshhaglund

Estimated hours: 50 hours

TASKS

setup

  • 1hr Setup hosting environment, code repository

dependencies

  • asterisk setup and config
  • asterisk voice navigation: design, record audio clips, upload, and test

hardware

  • phone or gsm modem connected to the asterisk machine? What number will users call / how we route it to asterisk?

module installs and config, in order of priority

  • Drupal/asterisk: install, config, test, new functionality? http://drupal.org/project/asterisk
  • Integrate and test mailhandler for receiving emails (via SMS) and attachments: http://drupal.org/project/mailhandler
  • SMS framework: Needs port to d6, install, config, test. http://drupal.org/project/smsframework
  • need module to allow easy upload & addition of images in posts via web interface (imagehandler?)
  • Move to future functionality: 6hr Develop module to receive geotagged photos from java ME app (note: don't think this is necessary. The java app can just send email to mailhandler.)

configuration

  • roles & permissions (admin, editor, registered user, anonymous user

theming

  • 10-20hr Develop custom theme (XHTML, accesskey navigation) (time estimate depends to a large degree on how iterative the process will be)

graphic design

  • logo (done, by schock remix rini templeton)
  • buttons

Hosting/Setup

  • setup vserver & asterisk - 3 hours
  • vserver hosting (Koumbit: $50/month)
  • payment for minutes (depends on the package used... e.g. $0.005/min)

Call-in interface

  • dial in and leave a message - 1 hours
  • media mover / cron job - 6 hours

CallerID? meta/Login
  • CallerID? as metadata for mediamover: 4 hours
  • Login: R&D for authentication against Drupal/other user database: 10 hours

Browse content through asterisk

  • via numerical keypresses. ("Bienvenios a vozmob. Marca 1 para publicar su noticia. Marca 2 para oir la noticia mas reciente. etc. Press 1 or say 'New' to hear the most recent story. Press 2 or say 'Publish' to post a story." etc.): 10 hours? (No voice recognition for the moment.)

Documentation

  • 4 hours

Notes

* The existing "asterisk integration" module (http://drupal.org/project/asterisk) does not seem to be what we want (at least as a first step) since all features are initiated through the web interface. We will have to add new functionality.

* one idea was: user sends sms to vozmob. vozmob calls user. In countries where calling party pays, this would allow us to make publishing a voice story free for the user. In the US, it would be an easy way to keep track of and reimburse people for their talk time when they leave stories. Downside: more complicated than just calling in directly.

Bug reports

Contacts

Back to the main project page: VozMob
to top


Global.VozMobCMS moved from Main.VozMobCMS on 29 Feb 2008 - 01:10 by SashaCostanzaChock - put it back
You are here: Global > VozMob > VozMobCMS

to top

Copyright © 1999-2008 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding this tool? Send feedback (in English, Francais, Deutsch or Dutch).