Version 5 (modified by Fran Boon, 13 years ago) ( diff )


Non-Coding Projects

Projects that do not involve Coding but may involve using the software, writing documentation, etc.

Project: Testing


Role-Play Being a User

  • Bugs - Try to break it! Some suggestions for bug-hunting:
    • Start with the demo system, and register for an account there:
      • Pick one application to test so you get familiar with how it works.
      • Try all the functions.
        • All the menus and buttons.
        • Adding and deleting and listing and updating records.
        • Downloads and uploads.
      • Change settings.
      • Try putting in bad data.
      • Try different browsers and different operating systems.
      • Try it while logged in or not logged in.
    • Install your own copy, so you can...
      • Give yourself administrator privileges and try out administrative functions.
      • Start with an empty database.
      • Try it with different database systems.
    • You can report bugs you find, but first:
  • Think about how could it be better.
  • Try Sahana Eden out -- you can use:
  • Modules that could use some usability improvement:
  • New or unfinished modules that would benefit from feature and workflow suggestions:

Report Tickets

See: Reporting Guidelines

  • What do you expect it to do? What did happen?
  • What additional features would you want?
  • What do you think the workflow should be? Report unclear/inconvenient workflow
  • Additional/clearer help text required. Suggest tooltips (help info) for fields on forms.
  • Was there something you wanted that wasn't available?

Project: Documentation

We need instructions for how to use some of our applications. We have some instructions on the UserGuidelines page -- this can be a starting point. For applications that have no instructions, the User Guideline Template tells what the form of the instructions should be. The instructions are posted on the Sahana Eden wiki, so you'll need an account to edit the wiki. Some instructions are in Google Docs and need to be put in the wiki.
For GCI, we request that you complete the "Report 5 Bugs in Sahana Eden" task first and focus on the application you will be writing documentation for, to ensure that you understand the functionality.

  • Pick one of the applications. (For GCI, pick the task for the application you want.)
  • Look at any instructions that are already available for the application, linked from the UserGuidelines page.
  • Pretend you're a user -- these are tools for emergency management, so think about using it for dealing with a disaster. Try out the application -- try entering data and looking it up, see what features are available. (Look at the ProjectInformation section for more on thinking like a user)
  • Things to look at:
    • Do the current instructions match the way the application is now?
    • Are there application features that have no instructions?
    • Are the instructions confusing?
    • Do the instructions fit the User Guideline Template?
  • To edit the instructions:
    • Register on and log in.
    • Make a new wiki page by going to its url in your browser. For instance, if the application's current wiki page is called IncidentReporting, make one called NewIncidentReporting by going to in your browser. Click create new page.
    • In the current instructions, click edit this page. Copy the wiki text to the new page and save that one. Cancel the edit in the original page. Now you can edit the new page without any worry about making a mistake. Save your work often!
    • There is information about editing the wiki and wiki formatting.

In particular we need documentation for:

  • Organisation Registry
  • Assessment
  • Request Management
  • Project Tracking
  • Volunteer Management
  • Inventory/Warehouse Management
  • Incident Reporting

Project: Ticket Verification

Some of our bug reports (tickets) have been left open even though they've been fixed. Others don't have much information. We'd like you to go through some tickets to see if they're done or if they need more information.

  • Register for an account on our demo site. Or you can install your own copy of the software, if you want to test the very latest version. Look at the bug testing project description for information on installing.)
  • Find a bug to work on from this list of older open bugs. (Older bugs are more likely to have been fixed or no longer relevant, so that's why we want to look at those.)
  • When you've found a bug to look at, add "GCI" to the "Keywords" (near the bottom of the ticket form), and submit that change. That will let other GCI students know this is *your* bug!
  • Try to reproduce the problem reported in the ticket:
    • If the bug is still there, and the description of how to make it happen is clear, just add a comment saying you verified that it's still there.
    • If the description of how to make the bug happen is clear, and the bug is gone...
      • If there are also suggestions for improvements, and those haven't been done, add a reply that you've verified the bug is gone, and change the type to "enhancement".
      • Otherwise, add a reply to the ticket: Describe carefully what you did to test it, and "resolve" the ticket as "worksforme". (The person who reported the bug can still reply and reopen the bug if they want.)
    • If the instructions to cause the bug to happen aren't clear, try to figure out what the reporter meant -- try to find the bug yourself. If you can reproduce the bug, add better "how to reproduce" instructions. See the Bug Reporting Guidelines for what makes a good bug report.
    • If you can't figure out what the ticket means, add a reply that tells the ticket reporter what info would be helpful.
  • Post links to the tickets you worked on in your GCI task.

Project: Collate Organisation List

Collate a list of organisations involved in Emergency Management from multiple sources, for use in future emergencies. See full description here.

Project: Stock Taking of Humanitarian Catalogues

Prepare a Stock Taking Report to assess what Humanitarian Catalogues are available which could be pre-populated into Sahana

Some Sources to Start with (you will need to search to find additional catalogues ):

For each Catalogue list:

  • Source
  • Date of Publishing
  • Data model. What data "fields" are their for each item? These could be the column headings, or you could be able to determine the types of data each catalogue records for its items. Present this as a list.
  • Categories / Sub-categories - What is the list/hierarchy they use.
  • Number of Items
  • Summary Description of what the catalogue is for and what items it contains

Prepare a report with the information listed above for each catalogue. Publish this report on a new page at BaselineSupplyCatalog (you will need to create a Trac account to do this).

Project: Scenario Cards

Running simulations of disaster scenarios is crucial to:

  1. Test that Sahana works correctly
  2. Train people to use Sahana
  3. Familiarise programmers with the Disaster management domain.
  4. Interest people in the project

We have a number of different resources on simulations currently available:

You can also search the internet (please add additional resources to this page)

We need to develop a series (deck) of cards which depict Disaster Scenarios which can be put together (maybe in order, maybe randomly) to create a simulation. It would be wise to share your initial ideas with the mailing list, as there are a number of people with a wealth of domain knowledge who will be able to guide you.

Post any images and files (in an open data format) at TrainingSimulationsScenarioCards

Note: See TracWiki for help on using the wiki.