Sub module #4360
closedFeature #3752: Design of the web framework for Data Centre Software
Feature #1850: Design and Development for web based ANRS
Module #2148: Developement for Configuration screens
Mission Activity..Modifiations as per client feedback
100%
Updated by Thara S Pillai 9 months ago
- Status changed from New to Closed
I. UI Enhancements
1.Online/Offline Mode Specification
• Add a UI option to specify whether the mission activity is Online or Offline.
• If Online:
o Set is_online = 'Y' in database.
• If Offline:
o Display a dropdown list of Online Mission Activities to link with.
o The selected linked activity should be saved in the database.
2. Sensor Configuration Enhancements
2.1 Format JSON Generation
• During the saving process of sensor configuration:
o A Format JSON should be created dynamically.
o From this JSON, extract the platform_code and store it in the database against the mission activity.
2.2 Format Template Selection
• A Format JSON Template should be selected from a predefined server location.
• This server location path should be passed to the Python script, which will generate the final format JSON for online mission activities.
3. Mission Activity Workflow
3.1 Go Online Operation
• After saving a mission activity, a "Go Online" button should be available.
• On clicking Go Online:
o Redirect to a new page listing all mission activities where:
No data has been entered.
is_online = 'Y'.
3.2 Go Live Activation
• From the list, select one mission activity and click "Go Live".
• The following operations should occur:
o Set the selected mission activity’s is_active = 'Y'.
o Validate that the platform_code of the selected activity is not already in use by another mission activity.
• Optionally, provide a "Go Offline" button to deactivate:
o When deactivated, set is_active = 'N'.
II. Edit Restrictions
• If any data has already been entered for a mission activity:
o Editing should be disabled for that activity.
o Display an appropriate message or tooltip indicating that editing is locked due to existing data.
III. Sensor Live Configuration
1 Sensor Activation
• In the Sensor Configuration section:
o Prompt whether the sensor is live or not.
o Only sensors marked as live should be included in the generated Format JSON.
2 Sensor Ordering
• The sensors included in the format JSON must be sorted by depth order before JSON generation.
IV. Database Changes (Proposed Fields)
Field Name Table Description
is_online mission_activity Indicates whether the mission activity is online (‘Y’) or offline (‘N’).
linked_activity_id mission_activity Stores the ID of the linked online mission activity for offline missions.
platform_code mission_activity Extracted from format JSON and saved.
is_active mission_activity Indicates whether the mission activity is currently live (‘Y’/‘N’).
V. Python Script Integration
• The Python script should:
1. Accept the format template location,mission activity sensor id array as input.
2. Generate the final format JSON based on the sensor configuration.
3. Return or store the generated JSON for database update and mission activation.
VI. Validation & Constraints
• Ensure only one mission per platform_code is active (is_active = 'Y').
• Restrict editing for missions with recorded data.
• Validate linked online mission activity for all offline missions.