Kubra Aksu ‐ Milestone 2 ‐ Individual Contribution Report

Member Information

• Name: Hatice Kübra Aksu
• Team: Frontend Team

Responsibilities

My primary responsibilities included overseeing the strategic planning and development of frontend features to align with Milestone 2 requirements, focusing on enhancing user experience and functionality and also facilitating coordination between other teams. I took the lead to the meet requirements for the frontend as it can seen in my PRs with the mentions and understanding of the requirements. I have written most of the pages and components that was presented at presentation since I write code continuously as you can see from lab-reports and the frequency of my PRs. While I was doing that, I have always followed the customer meeting and customer requests. Following those, I have updated our frontend development and reassured my teammates to be aware of it. Also I have contributed to the facilitation of communication between the customer and the different teams of ResQ. This involved improving the Account Page for victim personalization, customizing the Map feature with advanced search and filtering capabilities, streamlining the victim request creation workflow and responder resource creation workflow completely.

My involvement was crucial in integrating Google Reverse Geocoding, significantly enhancing the user-friendliness of our location displays. This integration was a strategic response to customer feedback aimed at improving the usability of our data tables. I was instrumental in developing and refining workflows that streamlined the process for responders creating resources and victims making requests, thereby managing list views effectively across various user roles. This initiative was key to ensuring a seamless and efficient frontend development experience.

In addition to these contributions, I created a sophisticated annotation logic, a feature that our customers highly value and is necessary for users, particularly victims, to easily understand and utilize facilities. Recognizing the importance of accurate and user-friendly geolocation information, I dedicated considerable effort to refining our geocoding capabilities. This focus on detail and user-centric design in geocoding and annotation has been a critical aspect of my work, reflecting my commitment to enhancing the overall user experience and functionality of our application.

In my role, I consistently monitored and revised the project requirements, guiding the implementation of our code accordingly. This iterative process of requirement revision was crucial, especially when changes were necessary to align with evolving project objectives. My leadership in this area ensured that our development efforts remained closely tied to the updated requirements, effectively steering the project in the right direction as needs evolved.

Also, as in every milestone report of ours, I took great responsibility to prepare our report and evaluating our progress, methodologies, and many other deliverables requested.

For our project presentation, I focused heavily on creating a detailed user scenario that mirrored our development, aiming to gather comprehensive feedback. Additionally, I was instrumental in preparing and delivering the presentation, playing a significant role in its overall execution and success.

Main Contributions

1. Frontend Milestone 2 Requirements Considerations- Future Plans
   • This issue focuses on strategizing and planning for the future development of the frontend, aligning with the requirements set for Milestone 2. issue_366
2. Account Page Improvement for Victim Consideration
   • This issue focuses on adding weight and height input fields to improve support and personalization for victims with specific clothing needs. issue_375
3. Map - Data Table Component Customized for Search and Filter
   • Enhancing the map search and filtering experience by developing a data table component that displays key information such as name, type, quantity, and location. issue_378
4. Enhancement: Victim Request Creation Workflow
   • Streamlining the process for creating victim requests with key details like type, status, and urgency for improved efficiency and user-friendliness. issue_380
5. Added Google Reverse Geocoding for Displaying Locations in Human Readable Format
   • Enhancing location data display in human-readable form for resources and requests using Google Reverse Geocoding. issue_388
6. Data Table Revision After Customer Meeting and With Respect to User-Friendliness
   • Enhanced user control over data table display with customizable row count per page. issue_418
7. Further Implementation for Request Creation Workflow with Respect to Customer Meeting
   • Improved the request creation process post-customer feedback, featuring an enhanced UI for better usability, new features like recurrent requests and custom fields, along with improved validation and error handling. Aimed at efficiency, user-friendliness, and accommodating diverse needs. issue_421
8. Implementation of Responder Resource Creation Workflow
   • Developing a user-friendly and efficient workflow for responders to create and manage resources, with a focus on intuitive design and detailed resource management. issue_422
9. Moved List View From Victims & Responders to Coordinators & Facilitators
   • Streamlining list views for coordinators with a condensed, exportable format, and enhancing detail and proximity focus for victims and responders. issue_458
10. User Scenario for Customer Meeting is Necessary
    • User Scenario for customer meeting is necessary to get feedback so with this consideration I have created a detailed user sceanrio which aligns with our development and uses functionalities implemented. issue_503
11. Create Release and Tag for Milestone 2
    • I have created a new release with considering and covering all covered requirements at the scope of this milestone. issue_506
12. Implement Enhanced Country Selection with Phone Codes on Account Page
    • Implemented telephone code selection to ensure accuracy and effective communication with users worldwide, recognizing the importance of precise contact details in a global context. issue_507
13. Enhancement of Request Creation with Focus on Recurrent and Specific Needs
    • Revamped for precise aid allocation, considering population-based quantification and dietary preferences. issue_508
14. Integration of Google Reverse Geocoding for Human-Friendly Location Names
    • Implemented Google Reverse Geocoding to simplify location data presentation, improving user experience by automatically converting coordinates into place names. issue_509
15. Integration of Advanced Filtering in Resource Data Table
    • Enhanced the resource data table with advanced filtering features for improved data management. issue_510
16. Frontend Login and SignUp Process with Backend-Driven Feedback
    • Improved frontend login and signup processes with real-time backend feedback for a smoother user experience. issue_511
17. Enhancement of Request Creation Process with Multi-Step Interface for Victims
    • Improved request creation with a multi-step interface for capturing multiple individuals' needs, recurring essentials, child-focused requirements, and health conditions. issue_512
18. Enhance Aid Distribution with New 'Request Review & Summary' Page
    • Streamlined distribution with a 'Request Review & Summary' page for dynamic display, clear formatting, and comprehensive review of aid requests, ensuring accuracy and thoroughness. issue_513
19. Resource Creation is Implemented with Respect to Requirements
    • Enabled responders to create resources with location, quantity, type, and category information, addressing resource management needs, including digitization and categorization. issue_514
20. Annotation Logic for Date and Geographical Data and Additional Metadata
    • Created annotation logic for our map interface, enhancing readability, contextual data integration, expanded metadata display, and interactivity, resulting in a significantly improved user experience. issue_515
21. Write our progress for our requirements for ML2 Report
    • I have evaluated and concluded our progress with respect to requirements. issue_520
22. Write test plan for ML2 Report
    • I have added my test plan as a link to my issue which i have explained our frontend test plan in detail, also i filled the necessary part in project plan according to that. issue_523
23. Comprehensive Review and Documentation of Frontend Development Processes
    • This issue shows a summary of my detailed documentation to capture our frontend development cycle, including requirement validation, technical integration, customized testing, feedback integration, alignment with customer direction, and our rationale for not implementing unit testing, serving as a guide for maintaining high standards in our frontend development. issue_527
24. Creation and Review of Release Documentation with Milestone Requirements - alpha 0.2.0
    • I have created our last release with revisiting requirements and indicating them at release body. issue_528
25. Create Evaluation of Project Deliverables and Impact Analysis on Project Plan.
    • I have evaluated our status of deliverables with the consideration of the impact analysis of our project plan. issue_529
26. Comprehensive Technical Assessment of Project Management Tools and Methodologies
    • I have evaluated our tools and methodologies with the consideration of the effectiveness of our project management. issue_530
27. Requirement Progress Report
    • I have revised all requirement and stated their progress with the consideration of our current development stage. issue_531
28. Requirements Revisio
    • While i was reviewing requirements for progress analysis, I also revised requirements with the consideration of our last customer meeting. issue_533
29. Create Individual Contribution Report for Milestone 2
    • I have created my personal report which shows my responsibilities and contributions. issue_535
30. Development of New User Scenario for Upcoming Presentation
    • I have created a user scenario for our presentation with considering our development. issue_536
31. Preparation and Submission of Milestone 2 Report Section: Project Overview and Status
    • Completed and submitted a detailed section on 'Project Overview and Project Status' for the Milestone 2 report, highlighting key advancements in our disaster response project. issue_537

Code-related Significant Issues:

1. Account Page Improvement for Victim Consideration
   issue_375
2. Map - Data Table Component Customized for Search and Filter
   issue_378
3. Enhancement: Victim Request Creation Workflow
   issue_380
4. Added Google Reverse Geocoding for Displaying Locations in Human Readable Format
   issue_388
5. Data Table Revision After Customer Meeting and With Respect to User-Friendliness
   issue_418
6. Implementation of Responder Resource Creation Workflow
   issue_421
7. Implementation of Responder Resource Creation Workflow
   issue_422
8. Moved List View From Victims & Responders to Coordinators & Facilitators
   issue_458
9. Create Release and Tag for Milestone 2
   issue_506
10. Implement Enhanced Country Selection with Phone Codes on Account Page
    issue_507
11. Enhancement of Request Creation with Focus on Recurrent and Specific Needs
    issue_508
12. Integration of Google Reverse Geocoding for Human-Friendly Location Names
    issue_509
13. Integration of Advanced Filtering in Resource Data Table
    issue_510
14. Frontend Login and SignUp Process with Backend-Driven Feedback
    issue_511
15. Enhancement of Request Creation Process with Multi-Step Interface for Victims
    issue_512
16. Enhance Aid Distribution with New 'Request Review & Summary' Page
    issue_513
17. Resource Creation is Implemented with Respect to Requirements
    issue_514
18. Annotation Logic for Date and Geographical Data and Additional Metadata
    issue_515

Management-related Significant Issues

1. Frontend Milestone 2 Requirements Considerations- Future Plans
   issue_366
2. User Scenario for Customer Meeting is Necessary
   issue_503
3. Create Release and Tag for Milestone 2
   issue_506
4. Write our progress for our requirements for ML2 Report
   issue_520
5. Write test plan for ML2 Report
   issue_523
6. Comprehensive Review and Documentation of Frontend Development Processes
   issue_527
7. Creation and Review of Release Documentation with Milestone Requirements - alpha 0.2.0
   issue_528
8. Create Evaluation of Project Deliverables and Impact Analysis on Project Plan
   issue_529
9. Comprehensive Technical Assessment of Project Management Tools and Methodologies
   issue_530
10. Requirement Progress Report
    issue_531
11. Requirements Revisio
    issue_533
12. Create Individual Contribution Report for Milestone 2
    issue_535
13. Development of New User Scenario for Upcoming Presentation
    issue_536
14. Preparation and Submission of Milestone 2 Report Section: Project Overview and Status
    issue_537

Pull Requests

As Author

1. Backend integration for resource creation is further implemented PR_501

2. Resource Creation Implemented In Detail PR_495

   • Solves: issue_514

3. Resource Creation is implemented with respect to requirements. PR_488

   • Solves: issue_514

4. Enhanced annotation logic for Date and Geographical Data and Additional Metadata PR_474

   • Solves: issue_515

5. Request creation is enhanced with the focus on recurrent needs, multiple victim needs, in-depth analysis of needs PR_462

   • Solves: issue_421 issue_508 issue_512

6. Advanced Countries Selection at Account Page for Accuracy of Phone Numbers PR_459

   • Solves: issue_507

7. Enhance Aid Distribution with New 'Request Review & Summary' Page PR_410

   • Solves: issue_513

8. Enhancement of Request Creation Process with Multi-Step Interface PR_409

   • Solves: issue_512

9. Initial Draft for Victim Request Creation Feature PR_408

   • Solves: issue_380

10. Frontend Login and SignUp Process with Backend-Driven Feedback PR_399

• Solves: issue_511issue_354issue_353

11. Implement Enhanced Resource Data Table with Advanced Filtering Features PR_385

• Solves: issue_378

12. Added Google Reverse Geocoding for Displaying Locations in human readable format - Geolocation/Annotation PR_382

• Solves: issue_509

13. Enhanced Account Page Layout and Including the Addition of Weight and Height Selection to Assist in Determining Appropriate Clothing Sizes for Victims PR_367

• Solves: issue_375

As Reviewer

1. Implement category trees and integrate with backend for map page. Add victim page with quick add need

   • PR_493

2. Remove bad testing data

   • PR_475

3. Feature/frontend add filtering by amount, creation date and map area coordinates

   • PR_469

4. Migrated to HTTPS

   • PR_457

5. Feature/frontend notifications page

   • PR_428

6. Migrate API endpoints to api.resq.org.tr

   • PR_342

7. Feature/frontend add list and filtering

   • PR_461

Additional Information

In my active engagement with the project, as evidenced by the frequency and content of my pull requests (PRs) and issues, my continuous and diligent work is apparent. The project insights, which transparently reflect each team member's contributions, further corroborate my consistent effort and dedication. I firmly believe that meaningful project development cannot be relegated to the final week alone, and my sustained contributions throughout the project's lifecycle have been vital.

Throughout the project, I consistently encountered the challenge of my pull requests (PRs) going unreviewed, often compelling me to proceed with self-merging due to sporadic engagement from my colleagues. This pattern of intermittent collaboration, particularly evident in the project's final week, occasionally resulted in unilateral decisions or modifications to the established features and code by other team members. In the crucial concluding days, despite my proactive efforts to secure reviews through calls and messages and the saying of the reviewing and helping to solve the problem, the feedback was opposite, I received ultimately led to the reversal of my contributions and not helping any at all. This development was not only professionally challenging but also deeply disheartening, as it significantly undermined the essence of collective effort and teamwork, which are imperative for the success of any collaborative project.

I initially developed a map table with list view and diverse filtering options, tailored for victim use. However, I later adapted this data table to suit all user roles, incorporating advanced features like filtering and exporting. Post a customer meeting where our data table received positive feedback, my teammate Ilgaz and I decided to repurpose it for facilitators and coordinators, while creating a new, more detailed table for victims, akin to Google Maps. Consequently, my earlier pull requests and issues, originally labeled for victims and responders, now cater to coordinators and facilitators. This strategic shift significantly influenced our project's planning direction. And since we did not have any other customer meeting after this change, I look forward to it!