Changes between Version 59 and Version 60 of BluePrint/CAPBroker

Timestamp:

05/05/15 09:07:51 (10 years ago)

Author:

Nuwan Waidyanatha

Comment:

--

BluePrint/CAPBroker

@@ -91 +91 @@
 * The Models: The table definitions go are in modules/s3db/cap.py. Place some functions which will help in the creation, sending and receiving of CAP XML files in s3msg module where it might best fit.
   * A detailed description of the data model is here: https://docs.google.com/spreadsheet/ccc?key=0AiLVG3CYfknsdGljMXNQejNWSURnVHZYYnMySERzdHc
-  * The module dependency graph is explained here: ['''Tharindu - insert URL to doc''']
+  * The Eden modules and their dependencies are explained here: ['''Tharindu - insert URL to doc''']
 * The GUI
   * index: A map and a table of alerts sortable by the various fields of an alert. Clicking on a row on the table centers the map to the <Area> associated with the alert.
@@ -102 +102 @@
   * create alert: A map with ability for easy input of polygons and circles, A drop-down for picking profiles and templates to use. A way to specify recipients for restricted alerts.
   * Reference and mockups: http://eden.sahanafoundation.org/ticket/1026
+
+==== MANDATORY MODULE ====
+|| '''Module Name''' || '''Module Key''' || '''Description''' ||
+|| Home || default || Root page with the index.html that is initially called by the application and display the home page to the user with login controls (more) ||
+|| Administrator || admin || When login as administrator the home page presents all administrative functions for the administrator to carry out the respective functions (more) ||
+||  || appAdmin || Similar to the Admin module but provides additional features relevant to the specific application such as with handling database related administrative functions (more) ||
+|| Ticket viewer || errors || required during development cycle; errors are shown only when login as administrator (more) ||
+|| Translation Functionality || translate || core module for application localization (more) ||
+|| Synchronization || sync || To manage the synchronization of multiple users working on the same features (more) ||
+|| Support || support || Help page, can be disabled but essential for providing help features (more) ||
+|| Map || gis || definitely required for spatially presenting information (more) ||
+|| Person Registry || pr || mainly used for managing users with privileges and roles with respect to accessing and operating CAP functions (more) ||
+|| Organization || org || required for managing all organizations/institutions (more) ||
 
 == Implementations ==