Organisation Registry

Who's doing What Where and When (4W)

Introduction

"Who, What, Where"
The Organization Registry keeps track of all the relief organizations working in the disaster region. It captures not only the places where they are active, but also captures information on the range of services they are providing in each area.

Haiti Requirements: ​http://wiki.sahanafoundation.org/doku.php/haiti:requirements#organization_registry

Old PHP User Guide: ​http://wiki.sahanafoundation.org/doku.php?id=doc:or:english

We should aim to be able to exchange data with UN OCHA's 3W. Information about the 3W database schema, possible import methods to OCHA, and 3W controlled vocabulary lists can be found at BluePrint3W More work should be done to ensure that the schema is compatible with the BluePrint3W schema.

Tables

This means having the following tables:

Organisation

• Name
• Acronym
• Type IS_IN_SET([Government,International Governmental Organization,International NGO,Misc,National Institution,National NGO,United Nations])
• Website
• National Staff
• International Staff
• Number of Vehicles
• Vehicle Types
• Donation Phone (gives the org an incentive to be listed)
• Logo (could be displayed on the map)

Sectors

• Name
• Abbreviation

Office

• Name
• Type IS_IN_SET([Headquarters,Regional,Country,Satellite Office]) (Would "Field" be a better term than "Satellite")
• Phone 1
• Phone 2
• Email
• Fax
• Address 1
• Address 2 (used for Postcode)
• Needs validation (checkbox) [NEW] or Validated

Contact

Handled by the Person Registry?

• First Name
• Last Name
• Title

Projects (previously Activities)

The Project Management module will be the main repository for Projects information.

These fields are take from a WASH (Water Health and Sanitation) Cluster form

• Organization (link to Org Table)
• Location
• Sector
• Sub-Sector (opt)
• Description
• Beneficiaries (number)
• Start Date
• End Date
• Funded (Y/N)

4x Many-to-Many tables to link them

• structured like t2_membership

Sector-to-Organisation

Many-to-Many table to link Sector to Organisations.

Office-to-Organisation

Many-to-Many table to link Offices to Organisations.
Optional validator to limit Offices as being affiliated to just a single Organisation

Contact-to-Office

Many-to-Many table to link Contacts to Offices.
Optional validator to limit Contacts as being affiliated to just a single Office

Contact-to-Organisation

Many-to-Many table to link Contacts to Organisations.
Optional validator to limit Contacts as being affiliated to just a single Organisation

Q: Is it useful to be able to have a Contact be affiliated to an Organisation but not to an Office?

• would the default 'HQ' be appropriate?

Would be nice to add these functionalities:

• Organigram creator from the Contacts
• ID cards from the Contacts

Q: Wouldn't "Staff" be a better description than contact? Q: Contact implies just a single person for each organization.

Screens

This describes the screens laid out in a way matching with the workflow.

Dashboard

• Organization Dashboard (will go to the organization of the current user)
• Organizations Registry
• Projects
• Map

Organization Dashboard

• Org. Details
• Edit Org. (Restricted)
• Offices
  • Add Office
• Projects (for displayed Org.)
  • New Project

Organization Registry

• List of Organizations
• Add New Organization

Projects

• List of all Projects
• Display on Map (redirects to Map, with Project filter selected)

Map

Filterable options to display:

• Offices
• Projects

• We want to be able to add Proejcts by Jurisdiction (e.g. Neighborhood for PaP)...without knowing the GIS data.
• If we do have polygons for neighborhoods, these will be displayed automatically on map.
• KML/GeoRSS feeds will just be GIS Centroids.

Reports

• Tabular
• Map
• Key is to be able to identify Gaps

---

BluePrints