Details
-
Feature
-
Must have
-
Obs Mgt & Controls
-
-
- Initial implementation of 'full' ODT services
-
3
-
3
-
13
-
4.333
-
REL-96 ODA v0.1.0-experiment
-
Team_BUTTONS
-
Sprint 5
-
-
-
-
15.6
-
Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
-
-
Cross_Team_Code_Review Team_BUTTONS
Description
The ODT has two components: a browser-accessible frontend that presents the ODT user interface and a backend component that interfaces with SKA systems (ODA, AAA, etc.) to provide services required by the front end. The frontend and backend work together to provide ODT editing (frontend) and ODT storage (mainly backend) functionality. SBD storage is a good example of how the two work together:, the ODT frontend does not store edited SBDs directly into the ODA; instead, it uploads them to the backend which processes the SBDs, validates them (again), and uploads them to the ODA.
This feature calls for the development of a prototype of the ODT backend. The ODT frontend will use the backend for SBD retrieval and storage. Implementation of the ODT/ODA interface is being covered in SP-2297.
Starting point: SB object created in ODT backend - retrieved by front end, modified and sent back
Scope of SB creation: the parts of an SB that the front end can handle
Web client -> ODT service -> ODA storage
NOTE: creating something in the web client doesn't store in the ODA yet if it's just a filestore.