Individual Milestone Report

Member Information

• Name: Ilgaz Er
• Group: 1
• Subgroup: Frontend Development

Responsibilities

Being a part of the frontend team, my main responsibilities were taking on various features at the weekly meeting, implementing them, reviewing the work of my teammates, and effectively communicating with my teammates regarding my progress on featuresand how it reflects on the project. Furthermore, I was, as with everyone else, responsible for creating a functioning app that satisfied all requirements.

Main Contributions

As a member of the frontend team, my main focus has been implementing the more technically challenging parts of the frontend application, in order to boost the total number of features we were able to actualise. Flowing out from that main goal, I accomplished the following tasks:

1. Annotations: I researched, conceptualised and implemented annotations in the frontend and coordinated with the backend team to create the annotation server.
2. Conceptualisation: I co-designed many of the features of our application, and communicated with my teammates as well as the backend to bring them to life.
3. Connecting the Website to Backend: From the design of the session token storage we currently use to the actual interfacing of the pages to the backend, I greatly contributed to connecting pages the frontend team developed to the backend.
4. Map Based Operations: I lead the development of the Map component, and integrated it with the overwhelming majority of the pages that used a map. My efforts resulted in a rich map-based experience for all users, including the visualisation of points as well as routes.
5. Category Tree: I created the frontend code for searching filtering based on the category tree.
6. Dockerisation and Deployment: I created the frontend docker container and was in charge of deploying our frontend to the Netlify hosting. I also assisted the backend team with resolving CORS and HTTPS related issues arising at the intersection of frontend and backend.
7. Cooperation: Beyond completing my work, I put significant effort into supporting the other team members. The scale of my efforts can be seen in me resolving a significant portion of the merge conflicts others have experienced, as well as my commits under the PRs of other team members.

Code-Related Significant Issues

• #589 - Coordinator Create Task Page
• #543 - Investigate annotations and decide on annotation format
• #542 - Implement annotation creation for frontend
• #541 - Implement annotation rendering for frontend
• #505 - Dockerise frontend
• #486 - Implement Category Tree based categorisation and item names
• #420 - Implement Responder My Tasks Page
• #419 - Implement notifications
• #414 - Implement Card View and Filtering for Map
• #374 - Frontend Tie Map to Backend
• #373 - Frontend Implement List View and Filtering to Map Page
• #300 - Frontend Implement Jwt Based Authentication For Login And Queries

Management-Related Significant Issues

• #524 - Write annotation plan and progress for ML2 Report
• #518 - Write summary of changes since ML1 for ML2 Report

Pull Requests

• #656 - Update FinalDeliverable.md
• #646 - Tie annotation frontend to backend
• #641 - Create Tasks View For Coordinators
• #634 - add checkboxes to display and set action status
• #602 - My Tasks View For Responders
• #595 - Implement text annotations for the frontend
• #504 - Dockerise frontend and add global readme file
• #501 - Backend Integration for Resource Creation
• #493 - Implement category trees and integrate with backend for map page. Add victim page with quick add need
• #475 - Remove bad testing data
• #469 - Feature/frontend add filtering by amount, creation date and map area coordinates
• #468 - Revert "Feature/frontend add list and filtering"
• #461 - Card-based Viewing of Information and Filtering in Map-Based Pages
• #457 - Migrated to https
• #428 - Notifications Page
• #342 - Migrate api endpoints to to api.resq.org.tr
• #340 - Show role-spesific pages based on selected role
• #330 - Implement sign up and localStorage based persistent login
• #306 - Implement generic map page
• #276 - initial application deployment