FOR ARCHIVAL PURPOSES ONLY

The information in this wiki hasn't been maintained for a good while. Some of the projects described have since been deprecated.

In particular, the "Ushahidi Platform v3.x" section contains information that is often misleading. Many details about this version of Platform have changed since.

This website is an extraction of the original Ushahidi wiki into a static form. Because of that, functions like logging in, commenting or searching will not work.

For more documentation, please refer to https://docs.ushahidi.com

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: remove link to roadmap

...

  • Automated upgrade in a couple of clicks
  • Increase quantity and quality of documentation - how to guides, trouble shooting etc
  • I dream to see the option to get the same sub/categories of my crowdmap deployments in the new Ushahidi 3.0 (Ushahidi, v3.x - Roadmap it is not clear if in the alpha was planned the same feature)

Admin

  • New Admin UI - a whole redesign of the backend   Definitely planned. 3.0 is a full rebuild
  • Spatially-aware administration - Improving the admin part for   approval&verification workflow management by regulating the grants only to those reports that are located in a defined area (for example per countries)
  • Add Admin "Healthmeters" to monitor the system where information is being added SMS, voice, reports, emails etc. Perhaps use a sliding time related scale to set the acceptable timeline. This will allow easy way to assess where resource is best utilised to optimise the system performance. Simple Colour grading green (processes clearing faster or at same speed as incoming requests), Orange (processes clearing at a slower rate to incoming requests), Red (Process overloading or clearing at a rate that is below acceptable levels -  example SMS queue has 6 hours of processing based on current clearance rate
  • Rework people tracking (USER roles/registration) Currently Users = people with access to site  . Reporters = people who report via email/SMS and Report Person = Person listed on a report that might actually have been entered by a different user... 
    Propose: 
    • Any interaction with the site (comment, report, send   SMS) creates a new USER in one USER table. All users are by default 'public (no admin access)'
    • Each USER can have multiple phone numbers, email, twitter, facebook, etc associated with that user profile. USERS can create passwords that do nothing more than allow them to change their personal info and associations (would need some system of varification: ask them to send a one-time code from their SMS, ask them to post a one-time code on their twitter account, etc) that would then link in all their reports from various media.
    • USERS can then easily be granted more access by elevating their position to a different ROLE
    • Thus if a USER sends an SMS, email, twitter, facebook   post, it is linked to their account (assuming their phone number / email / twitter account is already registered with that account) it if is not, a separate user might exist for phone # 123, and email 123@gmail.com and twitter account @123 – and this is fine, but once a USER submits registration info, they can link all of these accounts under one profile.
    • Reports can be sorted by USER (whether via email, sms or submitted on site  )
    • Ability to search user lists (uchaguzi   has over 200 user accounts). You have to page search. There is no user search. You also cannot mass edit roles by users. Hard to manage large teams.
    • Propose to allow admin editing of an anon / email / SMS post to allocate the ID of a current author/user (links to suggestion for every author/user to have their own hub page showing their contributions)
  • Map on Admin side for better report finding / filtering (currently handled by JEtherton plugin for some versions) this is related to "Front-End Admin" below. Planned: 3.x will have less separation between back and frontend.
  • Front-end admin?!?! Users with higher roles are granted more functionality, but otherwise the general layout looks the same. (Currently feels like Windows 8 split personality). Planned. Though there may still be something like a 'Tools' UI section for configuring site settings

...