Content Comparison

...

• Updated Atlas Module associating marker with OpenMRS ID with new functionality.
• OpenMRS 2.0 Atlas Module integration.
• Atlas website markers management functions + extra functionalities (markers filtering, color, …).
• README in developer’s documentation explaining how are implemented new functionalities and Atlas Module App.
• README in user documentation  explaining how to use Atlas Module App.

Project Timeline

21 April – 18 May:

• Getting familiar with Atlas Module and OpenMRS ID SSO

• Fixing some Atlas related Tickets

• Community bonding, participating in community events (Developers Forum, OpenMRS University, Hangout with mentor….).
   

19 May – 31 May:

• Add Sign In form for OpenMRS ID and add OpenMRS ID SSO dependency in Atlas Module.
   

1 June 1 – 30 June:

• User can sign in successfully with his OpenMRS ID in Atlas Module

• Atlas Module ported to OpenRMS 2.0 (whith a look like google app style)

• Mid term Eval
  
  

1 July – 12 July:

• An existing marker can be associated with an OpenMRS ID in Atlas Module.

• Add function to "recover" control of a marker using the registered OpenMRS ID

• A marker can be created and updated directly in the Atlas Server.
   

13 July – 26 July: 

• New administrative screens in Atlas Server to manage markers (move, remove outdated or invalid markers)
   

10 August – 15 August:

• Extra features in Atlas Server : map exporting as a slide for presentation, marker filtering by type or version
   

16 August – 22 August:

• Wrapping up project, final touches.

• Writing Wiki and developer doc.

Mockups

...

Atlas Module

In my mind, Atlas Module just render the Atlas Server into OpenMRS app, adding admin function as enable/disable marker update

1. Home Page

   Mockup
   Version 1 Name atlas module homepage

2. Login and marker update ON/OFF

Atlas Server