masterfacilitylist / mfl_admin_web

This is the administration ( backend ) web application

mfl_admin_web

This is the administration web application of the the Kenyan MFL v2.

Project organization

The project's structure has been derived from ng-boilerplate

mfl_admin_web/
  |- coverage/    #  contains coverage output
  |- build/    # contains output of the build process, used to serve files in development
  |- bin/    # contains output of the compile process, used to serve files in production
  |- karma/    # contains configuration for karma
  |  |- karma-unit.tpl.js
  |- src/      # contains the source code of the application
  |  |- app/      # contains the source code of the angular app and app-specific code
  |  |  |- app1    # a single app
  |  |  |  |- tpls      # contains app1's templates/partials
  |  |  |  |  |- app1.tpl.html
  |  |  |  |  |- app2.tpl.html
  |  |  |  |- tests      # contains app1's tests
  |  |  |  |  |- module.spec.js
  |  |  |  |  |- routes.spec.js
  |  |  |  |  |- controllers.spec.js
  |  |  |  |- module.js      # contains app1's module definition
  |  |  |  |- routes.js      # contains app1's states
  |  |  |  |- controllers.js # contains app1's controllers
  |  |  |  |- ...
  |  |  |- app2
  |  |  |- app3
  |  |  |- ...
  |  |- assets/      # contains the application's assets
  |  |  |- <static files>
  |  |- less/        # contains the application's less files
  |  |  |- main.less
  |  |- settings.js  # contains the application's 'environment' configuration
  |- vendor/
  |- .bowerrc
  |- bower.json
  |- build.config.js
  |- changelog.tpl
  |- circle.yml
  |- .gitignore
  |- .jshintrc
  |- Gruntfile.js
  |- module.prefix
  |- module.suffix
  |- package.json

Development

All the commands in this section assume that the current working directory is the root of the project.

Requirements

The project requires nodejs to be installed in your system

Getting started

First install npm and bower dependencies

$ npm install

The command shall install bower dependencies right after npm dependencies are installed.

If grunt or bower are not installed globally in your system or you want to use the ones installed by the project, you may have to add the bin directory in node_modules to system PATH.

export PATH="$(npm bin):$PATH"

Development environment

Run grunt connect:dev to serve files. This server uses development only files.

To automatically build files after changes, run grunt watch.

If you don't want to have automatic builds, run grunt build to build files.

Production environment

To see what is going to be used in production, run

$ grunt

or

$ grunt build
$ grunt compile

This will create the 'compiled' files in the bin directory.

The files can then be served using

$ grunt connect:prod

Testing

Running tests is as easy as running

$ grunt test

mfl_admin_web's Issues

Review on 8th June

• CRUD (Excel checklist)
• Use of MOH logo with 'Ministry of Health' written below court of arms
• Logo USAID to go to a new tab
• Feedback for every action
• Show autocomplete on a tablet
• Optimize excel download
• Open weekend and open during public holidays
• Add ward name to facility list and owner
• Number of times a facility service has been rated
• Fix facility-owners in county
• Add facility types to dashboard
• Spreadsheet for responsiveness

June 2nd Review Checklist

@jason-wanjohi

• Ensure there is fallback plan for old/unsupported browsers
• Have logos for the 4 main browsers.
• The logos should link to a browser's official download pages
• Make sure search works everywhere

@owagaantony

• Add year to copyright information
• Fix page titles
• Fix header: should show user
• Remove top nav icons
• Rename "CHUs" to "Community Units"
• Implement user profile
• The forms that are inside cards should have more padding
• Change order of menu entries in the services section ( categories come first )
• When you are in a nested view e.g "Add a service category", the relevant entry in the side nav should be highlighted
• Review action buttons for all forms e.g Delete makes no sense for a new item
• Handle HTTP 429 for rating API
• Finalize on navigation
  • Add all the links that should be part of the navigation bar
  • Think through drop-downs
  • Add the default url
• Fix login page:
  • Replace "username" with "email"
  • Fix the login button
• Site name(Master Facility List V2.0) should link back to the home page
• For all dropdowns, the front-end should explicitly request sorting by name, ascending order. Extend this to the public front-end.
• Fix "Cancel" in forms
• Create a default error 404 page
• Fix the dashboard
  • Styling
  • Have better names for the panel titles
  • Fix county level user; Constituencies do not show
  • Fix the state of the dashboard when a user is not logged
• Add a notification area
• Typo in footer (period & space)
• In Top 20 counties hover should show details of that particular county
• Bar chart titles should be in title case
• Normalize chart legends(should all be in sentence case)
• Facilities navigation should highlight properly
• Page titles should be uniform
• Turn off CHU

@liyocee

• Implement Community Health Units (CHU)
  • Implement CHU CRUD
    • Ensure a CHU has contacts
    • Ensure a CHU has approvals
  • Implement (Community Health Extension worker)CHEW CRUD
    • Ensure a CHEW has contacts
    • Ensure a CHEW has approvals
• Implement a combo box, replace all voluminous selects with it
• Style the service catalog
• Implemment the admin(Setup ) section of the admin
  • Have all setup data CRUD implemented
    • Contact types
    • Towns
    • Counties
    • Constituencies
    • Wards
    • Owners and owner types
    • Job titles
    • Regulating bodies and regulating body contacts
    • Community health unit statuses
    • Community health unit approvers
    • show admin units codes. (Remove auto-numbers)
• Sorting in select, combo box (Stupid)
• Grid search
• Excel export
• Facilities get basics in

@ngash

• User management
  • User CRUD
  • User contacts
  • User groups
  • User Counties
  • Roadblock on login after password reset
    • Every drop down should handle pagination
    • Dashboard redirect
    • Lock access to the application, user must log in
    • Improvised RBAC

Admin section: final checklist

• Linking users and groups
• Linking users to contacts
• Roadblock on first login or after password reset

Community Health Units Section

• Community health units, contacts and approval
• Community health workers, contacts and approval

Facility workflows: final checklist

• Facilities, addresses, contacts, units and services ( consolidated workflow, not five separate screens; the facility detail view should have a header that summarizes pertinent information e.g code, status, regulatory information etc )
• Publishing workflow
• Approval ( maker-checker; SCHRIO / CHRIO )
• Regulation workflow
• Upgrade workflow
• Downgrade workflow
• Facility detail report ( shared with public front-end )
• Ratings report
• Facility correction template
• Cover letter

27th May review issues

• Chomba to pot mfl web into mfl public web
• revamp tests
• @owagaantony fix navigation

General UI matters

• Fallback behavior for old browsers; see http://modernizr.com/ and how https://html5boilerplate.com/ use it to display a warning for IE 8 and below and proceed from there;

• Prettify the login page

• User profile ( users managing some of their own details, including password changes )

• Revamp of navigation. The admin should have the following:

  • a dashboard, seen on first login
  • a "facility administration" tab in the top navbar ( every facility link will be on a left nav within that facilities section )
  • a setup tab, under which metadata setup will be found ( contact types, towns etc )
  • a user management tab, under which roles and users stuff will be found
  • a CHUL tab

  The default views for each of those sections should be sensible e.g the view that has the most likely action that a user wants to undertake after clicking through to that section. The nav hierarchy must take pains in showing the current nav position ( show active tab on the top nav and active view on the left nav ). Every position in the nav hiearchy should be deep linkable.

Setup section: final checklist

Setup screens for:

• Contact types
• Towns
• Counties and county boundaries ( display embedded map )
• Constituencies and constituency boundaries ( display embedded map )
• Wards and ward boundaries ( display embedded map )
• Owners and owner types ( display embedded map )
• Job titles
• Regulating bodies and regulating body contacts
• Community health unit statuses
• Community health unit approvers
• Communities ( for CHUL )

SIL AfyaInfo MoH MFL Meeting 8th June

• Track facilities that are open over the weekend and on public holidays and 24-hour facilities
• An error in the town field of Gathaga constituency (public user site)
• The category listing under admin was slow
• Total number of facilities owners numbers on the dashboard of admin website
• Updated service catalogue (they need to share the data so the developers can add it into the admin website)
• DHIS and MFLv2 Link up.
• Ministry of Health under the Court of Arms in the public website
• National, county and constituency group emails for access rights within the admin website
• Search for admin users should be swift to help assist users who forgot passwords or user names. Should allow search by any data fields e.g. name email etc

Create badges to create context for color of landing page cards

Service catalog section: final checklist

• Service categories
• Services
• Options
• Service options

Dashboard: final checklist

• Analysis of facilities by administrative unit
• Analysis of facilities by type
• Analysis of facilities by owner / owner type
• Analysis of facilities by regulator / regulatory status