SCS: Create Databases and Endpoints for Backend
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
- To create a series of endpoints that can do the following: get all the items in inventory, get a single item from inventory by id / upc, add an item to inventory, edit an item in inventory by id / upc, get required data for report generation (see .JSON).
- After the re-structure of our Backend from last sprint, it's time to implement.
Related Issues:
How are you going to achieve the goal or solve the problem?
- Using the .JSON files from last sprint, create data structures in Mongo and endpoints that match I/O requirements.
What will be produced as a result of this effort and where will it live on GitLab?
- The backend system will have the user interface that users could use our inventory system based on our design. It should be on spike-databases-endpoints
Give a justification of weight or due date.
- Weight: 4
- Due Date: It should be the last step for our project after everything from api and backend is all good to go. The api and backend system should be fully refoldered.
Who will do it, and what will they do?
@anhprotien588 will be completing this task. Tien will implement the database and connect the design from intake and outtake form to create a system that works likely.
What was the outcome?
The database has been completed with the proved of screenshots. We have four endpoints: category, inventory, item, and report. Everything works correctly as the format from format document. The backend system is all good to go.
Template Version 1.0.0
Edited by Tien Tran