-
Creation of prisma schema and seed
- Created all the necessary tables required to store each entity.
- Overall everyone gets inserted into the user table, because in the end everyone is a user and then it is later seeded into desired table by type.
- Furthermore, each user is seeded into its required table while also doing the same for courses, overall courses has a table however to differentiate the completeed courses a seperate table has been created.
- Completed course, current course and pending course (which works on user so far) are seperate tables which link to the overall course table.
- Use of composite primary keys in those tables allow us to properly make the relation between the courses and the students.
- Used an enum system with 3 user types which we can use to easily classify the user types. -Furthermore, db has been populated sucessfully using the seed.js
-
Creation of the repos
- Created a user repo to retrieve all user information
- Created course, student, instructor and admin repo using the basic CRUD operations using prisma
-
Creation of all routes
- Since the specific repos have been created, the corresponding routes have also been created.
- For example there is a route.js for the user which retreives the list of users from the user repo using the GET method
- Same have been implemented for the other entities, moreover for the student and course there is a PATCH method which allows us to perform updates for student or course of that particular ID.
-
Additionally, there is a repo which is used to generate the statistics.
- this repo is basically getting used in the actions.js to carry out server operations when implementing the statistics webpage which is created using next.js
-
Creation of components
- there are three components out of which only one has been successfully completed which is the courses.jsx
- this component displays statistics based off of course information hence is classified under the course component and tailwind css has been used to make the webpage slightly appealing rather than using the default css styling.
-
Use case 1
- Creation of login page
- Contains validations for username, password and the type.
- When right information is entered then it takes user to dedication webpage based on their "type".
-
Use case 2
- creation of search bar (works successfully!).
- User can search for course name or by course type such as "programming, engineering, etc."
- the search button present helps to render the final state of the webpage based on user criteria
- when erases keywords in search field and clicks the button then it will re-render the original state.
-
Use case 3
- Implemented registration system
- Loads the logged in user data from local storage
- When user clicks on the register button it displays appropriate message
- However, requires functions to work with admin page such as "approval feature"
- Needs data persistence system because when user clicks different course to register it does not work as expected.
-
Use case 4
- Created the report basically
- This displays the courses student has successfully completed, courses in progress and the pending courses.
- When student is in registration page, beside the search bar there is a button which takes them to the page which displays all that info.
- This works properly as it reads from the json files
- However the pending courses require the implementation of persistence to make it work properly.
-
Use case 5
- Developed the admin page
- Added all the required features
- Displays all the courses that with a filtering system
- Was not able to implement the persistence system
-
Use case 6
- Created the instructor webpage with javascript
- This will be used exactly like the admin layout
- There will be additional page to show the stats same for admin page