In order for Bus Ops reporting developers (the targeted initial users of Site Services) to have data to query, we need to define the initial data schema and rules to provide data fill, create configurations, and then fill in the data.
Acceptance Criteria:
Initial data model defined (what fields will we have in Site Services for site -- does not need to be comprehensive, but needs to be expandable in the future)
Needs to include mapping from multiple standard sources for site data to the aggregated table for Sites
Rules defined for pushing data from the source/s (e.g. if a new value is available from one of the sources, under what circumstances should it be pushed into.
*
Configurations developed and deployed from the rules and data model.
*
Existing schema extended from updated data model.
*
Initial values actually populated into the Site Services database and able to be queried / consumed via the Site Services API
Assumptions / Preconditions:
* Assume that we are using the current Site Services data framework, which is Sites-based only (not relational model of Locations : Structures : Sites)
Hi, Dear.
I'm very happy to bid your project.
I'm full stack web developer and have much experienced with Python/Apache.
So it is no problem for me.
If you give me an opportunity I will do your job perfectly in short time.
Best regards.
Thanks