List of Projects OSRA - Support system Team meeting summaries Client meeting - 9 September , 2014

Client meeting - 9 September , 2014

Updated about 5 years ago by Motasem Salem
A face-to-face meeting was held with the client on 9 September. The following are some of the points that were discussed:

We agreed on what constitutes Phase 0:


  • Branch data storage and lookup
  • Organization data storage and lookup 
  • Partners: create, read and update 
  • Sponsors: create, read and update 
  • Orphan List upload
  • Orphan List import
  • Orphans: read, update
  • Sponsorship management: Create, Activate and Deactivate sponsorship + all related workflows and business logic
  • Role based authorization (3 roles only: Admin, Orphan manager and Sponsor manager roles)
  • Basic reports (list of reports & details of each to be given later)

Hosting and file storage:


They are fine with paying for Heroku and S3

Maintenance of data in lookup tables:


There is no need for any CRUD interface to manage lookup data. These 
rarely change and when they do, they will create a new user story for that.

The following is the list of these tables:

  • Branches
  • Organizations (sorry Sly, I know you already created CRUD views)
  • All statuses 
  • Provinces

Orphan list OSRA ID:


We can keep a simple running sequence (with a number of leading zeros) as the OSRA num for Orphan Lists. The important thing for them is to keep track of the partner that submitted a list and the date it was imported.

Orphan state:


There are three different statuses for an orphan:

  1. Activity Status: Active / Inactive / On hold
  2. Sponsorship Status: Unsponsored / Sponsored / Previously Sponsored
  3. Priority: High / Normal

Orphans above 18 should be displayed in a different row color in index views.

I have more details about the business rules for each type. I will provide a write up later.

Orphan DoB validations:


As Craig pointed out, we need to validate the orphan's date of birth in relation to their father's date of death.

Orphan card PDF generation (Phase I):


There will be multiple PDF templates:

  • Generic OSRA template in Arabic.
  • Each of the organizations will have their own template with their logo.
  • An English template for non-Arabic speaker sponsors (very rare).

When generating the English card, the user should provide the required orphan data in English. This should be saved in a separate table in case the same report needs to be regenerated later. In case of regeneration, the user should be given the option to modify the data and store the updated values.

Orphan photo and document upload (Phase I):


Users need an interface to upload image files (preferably multiple files at a time). The users will rename the files appropriately offline and when they upload them, they will be linked to the corresponding orphan record based on the file name.
 
Naming conventions to be agreed on and communicated later.

Other points:


  • There is no need to link a user to a particular branch.
  • Sponsor status should be one of: Active, Inactive or On hold. There is no need for an Under revision status for a sponsor.
Revisions

comments powered by Disqus