Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Reference Application is a state of the art implementation of OpenMRS, which may serve as a solid base for new implementations. It is designed using the latest UI 2.x and App Framework and is related to

Jira Legacy
serverOpenMRS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId45c5771b-fa4b-3e43-b34a-c19dc45ccc95
keyRA-61
, which make it easy to add new functionality as small apps in a similar fashion to mobile applications. However, lots of the administrative tasks e.g concept, form, global propertySetting (formerly Global Property from platform 1.8 downwards), roles, locations and privilege management are still being done from the legacy user interface which is accessed via the Advanced Administration App, these tasks need to be ported to the reference application too.

...

  • Add User Account Manager tool  see https://tickets.openmrs.org/browse/RA-61
  • Manage Locations (including tagging those location, adding and editing location attributes)
  • Add advanced settings management tool(s), add custom pages for managing specific global properties Settings (formerly Global Properties from platform 1.8 downwards) (e.g. all the security.* GPs together nicely in a Security Settings page)

...

Administration Tools will be built on UI Framework, which form the base of reference application. The module will have standard module dependency on “uiframework” module. The UI Framework is built on Spring MVC and implements Groovy templates for views. So, the views will be provided by .gsp files. Existing fragments of UI 2.0 will be used and new fragments will be created wherever required. 

 

Deliverables

 

Communication Plan

Weekly meetings - ~10 am EST every Wednesday

Emails, IRC

 

Project Timeline

  • 21 April – 15 May : Understand App Framework and UI 2.x deeply, learn required technologies, get to know the mentors, prepare working on the project
  • 19 May – 26 May : Will not be available due to the final exams at university
  • 26 May – 22 June : Create module, implement User Manager
  • 23 June – 27 June : Midterm evaluation
  • 28 June – 15 July : Implement Location manager
  • 16 July – 1 Aug : Implement Advanced Settings + Record Manager (possibly)
  • 2 Aug – 7 Aug : Finalize UI
  • 8 Aug – 18 Aug Write tests, prepare documentation
  • 19 Aug – 22 Aug : Final evaluation

UI Mockups

1.       1. Administration App Homepage

...

3. findUser App

Mockup
Version12
NameFind user

 

4. addUser App

Mockup
Version45
Nameadd user

 

5. Location manager Dashboard

...

Mockup
Version1
NameRecord Manager

 

Resources

 

Deliverables

 

Communication Plan

 

Project Timeline

·         21 April – 15 May : Understand App Framework and UI 2.x deeply, learn required technologies, get to know the mentors, prepare working on the project

·        19 May – 26 May : Will not be available due to the final exams at university

·         26 May – 22 June : Create module, implement User Manager

·         23 June – 27 June : Midterm evaluation

·         28 June – 15 July : Implement Location manager

·         16 July – 1 Aug : Implement Advanced Settings + Record Manager (possibly)

·         2 Aug – 7 Aug : Finalize UI

·         8 Aug – 18 Aug Write tests, prepare documentation

...