Final Milestone

What's Changed

• Feature/be 552 need and resource entity consistency by @alitpc25 in #554
• removing X-Selected-Role from header in auth by @furknbulbul in #556
• Fix Unresponsiveness on Map Page and Enhance Annotation Card Functionality by @kubraaksux in #564
• Request Creation Backend Integration Implementation by @kubraaksux in #563
• Improved/Added coordinator functionalities. by @volcaniqueo in #571
• Feature/be 555 refactoring some api endpoints in backend by @alitpc25 in #558
• Feature/be 559 recurrent need implementation by @alitpc25 in #576
• Improved/Added admin functionalities. by @volcaniqueo in #577
• Address the Deficiency at Resource Type and Resource Selection Logic in ResourceDetails1 Component by @kubraaksux in #569
• Implementation - First Draft of - Customer Request - Add Components as Images To be Annotated to Resources by @kubraaksux in #562
• Responder Specific Map Implementation Changed with The Purpose of Showing Responders Their Tasks Only by @kubraaksux in #575
• Resource selection implementation with category tree revised by @kubraaksux in #590
• #592 NullPointerException handled by @alitpc25 in #593
• Feature/frontend text annotation by @ilgazer in #595
• Role prefix removed by @furknbulbul in #597
• Feature/mobile 394 notification page by @alperenDagi in #598
• Feature/be 594 annotation backend server creation by @alitpc25 in #599
• Feature/mobile 390 create task screen by @HarunErgen in #601
• Feature/be 398 task action improvement by @furknbulbul in #424
• #591 Implemented Image upload to resources using amazon s3 bucket. by @alitpc25 in #603
• Filtering Resource by Receiver Id by @volcaniqueo in #607
• My requests page added by @GulbeycanCagri in #605
• Update ResqService.kt by @GulbeycanCagri in #608
• Implement need and resource lists. Format lists for Map Screen by @HarunErgen in #604
• Dev by @GulbeycanCagri in #609
• Feature/mobile 360 profile bug fix by @GulbeycanCagri in #610
• #612 Victims allowed to use some endpoints in NeedController. by @alitpc25 in #613
• Save location in shared preferences by @HarunErgen in #617
• change auth by @furknbulbul in #621
• Feature/be 572 74 missing unit tests by @volcaniqueo in #614
• Topbar Edited to Show Role Based Panel View by @kubraaksux in #622
• Ongoing Tasks Implemented by @GulbeycanCagri in #624
• My Tasks Implementation by @GulbeycanCagri in #627
• Update resource services. Update resource lists on map screen. by @HarunErgen in #626
• Delete resq/mobile/ResQ/app/src/main/java/com/cmpe451/resq/viewmodels… by @GulbeycanCagri in #628
• Fix my mistake by @GulbeycanCagri in #629
• Missing unit tests for Resource & Notification Service by @volcaniqueo in #630
• View need status by @furknbulbul in #631
• Responder action view by @ilgazer in #602
• Update My Requests Page by @GulbeycanCagri in #635
• Final Milestone Update: Facilitator Map Page First Draft and Enhancing User Experience through Backend Integration and Comprehensive Revisions to Whole Codebase by @kubraaksux in #636
• add checkboxes to display and set action status by @ilgazer in #634
• Feature/mobile 500 map implementation by @alperenDagi in #639
• frontend added a create action page by @ilgazer in #641
• Resource Backend Integration Enhancements by @kubraaksux in #640
• Frontend- Security and Privacy - KVKK by @kubraaksux in #644
• Tie annotation frontend to backend by @ilgazer in #646
• Frontend/Facilitator by @kubraaksux in #618
• Request Backend Integration - Seperate createNeed Requests For Each Category by @kubraaksux in #642

Full Changelog: customer-milestone-2...customer-milestone-3

0.2.0-alpha

Captured Requirements at This Milestone

Under User Roles/Victim title
1.1.2.1.3. Victims shall be able to view assistence locations on a map and as a list. (Help centers, soup kitchens etc.)
1.1.2.1.4. Victims shall be able to filter the assistence locations by type and distance.
1.1.2.1.5. Victims shall be able to view available resources on a map and as a list.
1.1.2.1.6. Victims shall be able to filter resources by name, category and distance.
1.1.2.1.7. Victim shall be notified when a relevant asistance location is nearby.

1.1.2.1.3. is considered in annotation implementations. For now, code is partially implemented which marks annotated objects and their cards have geolocation ( as longitude and latitude), metadata, category, short and long description. Annotation datas were improved in detail to capture the essence of annotations better. For now on, since other implementations have more urgency, we had decreased the priority of annotations for this milestone. It will be completely and comprehensively implemented at Milestone3.

1.1.2.1.4. , 1.1.2.1.6, implemented completely.
1.1.2.1.7 shows mock-data for now and it is implemented as first draft.

Under User Roles/ Responder

1.1.2.2.2. Responders shall be able to create a resource for objects or services they can offer.
1.1.2.2.3. Responders shall be able to set the following information regarding a resource: location, quantity, type, category
Those are fully implemented and frontend and backend is integrated.

Under User Roles/ Facilitator
1.1.2.3.2. Facilitators shall be able to create requests.
1.1.2.3.3. Facilitators shall be able to create resources.
-Those are allowed at frontend with respect to implementation of backend.

1.1.2.3.4. Facilitators shall be able to view requests on a map and as a list.
1.1.2.1.5. Facilitators shall be able to filter requests by name, category and distance.

• Those are implemented in advance.

Under User Roles/ Coordinator
1.1.2.1.6. Coordinators shall be able to view resources, requests and tasks as a list and on a map.
1.1.2.1.7. Coordinators shall be able to filter resources, requests and tasks by whichever subset of name, category, amount, distance, urgency and status is applicable.

1.1.3. Location Services
Users shall be able to view the map and share their current location information on the map.
Partially implemented. Map integration with backend is under the scope of this milestone, share their current location information on the map not covered.

1.1.4. Information Filtering
Users shall be able to search for and filter information provided by facilitators.
All filtering and searching functionalities completely ready.

1.1.5. Disaster Reporting
Users shall be able to add and view warnings about the current disaster to the map.
Partially implemented. Users can view warnings but add yet.

Also those requirements are captured at this milestone:
1.2.1. Multi-hazard support
1.2.3. Resource Management
1.2.3.1. Digital Resources
1.2.3.1.2. Resources must be digitized and quantified in the system.
1.2.3.2. Categorization of resources
1.2.3.2.1. To facilitate distribution, sent resources should be categorized in detail, including the contents of each box, quantity, shoe/clothing size, etc.
1.2.3.3. Semantic relations between resources
1.2.3.3.1. Resources should have semantic relationships for efficient categorization.
1.2.3.4. Dynamic needs
1.2.3.4.1. The platform should be flexible enough to adapt to the changing needs of disaster areas, depending on the location and stage of the disaster. This includes different needs in urban and rural areas, as well as different needs for surviving the disaster and educational needs.
1.2.7. Map-based operations
1.2.7.1. The platform shall have a map interface that displays the appropriate subset of resources, requests, and tasks, along with warnings related to the current situation.
1.2.7.2. The map shall be capable of filtering items by the applciable subset of name, category, amount, distance, urgency and status.

Frontend Testing: We've tested the interface to confirm that all visible elements and user interactions function as expected.

Backend Testing: We've checked our server-side operations, ensuring APIs and databases handle data correctly.

Mobile Testing: We focused on ensuring that the app meets all specified requirements and thoroughly tested its end-to-end functionalities to guarantee a smooth user experience.

Integration Testing: We've tested the connection between the frontend and backend to ensure they communicate and operate together properly.

0.1.0-alpha

The project involved a range of tasks such as backend setup, implementing user authentication and authorization, database design, and setting up Dockerfile for backend deployment on AWS. The frontend development included creating sign-in and sign-up pages, user role management, and app services. Mobile development encompassed login-registration pages, navigation features, and user profile pages. Key functionalities like APIs for responders and victims, as well as unit tests for various services including authentication and category management, were also developed.

Release 0.0.1

What's Changed

• add application properties by @alperenDagi in #159
• dockerfiles and docker-compose added by @alitpc25 in #158
• Weather Api by @alperenDagi in #160
• Directionsapi by @alitpc25 in #162
• Added GeoJs by @GulbeycanCagri in #163
• Directions API merge by @alitpc25 in #164
• weather pages added by @alperenDagi in #166
• Geocode controller, service, model, frontend by @HarunErgen in #167
• utilized the model GeocodeData by @HarunErgen in #168
• Imdb api by @furknbulbul in #172
• weatherpage jsx and css files updated by @alperenDagi in #170
• directions api frontend updated by @alitpc25 in #173
• Directionsapi by @alitpc25 in #178
• Migrate to nginx by @ilgazer in #185
• Final changes by @GulbeycanCagri in #187
• Give and get feedback functionalities added by @alperenDagi in #188
• Directionsapi by @alitpc25 in #189
• Containerised backend build by @ilgazer in #196
• Imdb api frontend by @furknbulbul in #191
• weather api frontend updated by @alperenDagi in #197
• Translation api by @volcaniqueo in #195
• Hotfix: make docker dev build work again by @ilgazer in #200
• Geo js by @GulbeycanCagri in #198
• Directionsapi test cases by @alitpc25 in #201
• weathersercivetest added by @alperenDagi in #202
• Fix swagger by @ilgazer in #204
• Movie post endpoint by @furknbulbul in #209
• Imdb fix by @furknbulbul in #214
• Added tests. by @GulbeycanCagri in #218
• test added for imdb by @furknbulbul in #219
• added POST method by @HarunErgen in #223
• Wikidata api by @ilgazer in #224
• Nasaapi by @kubraaksux in #227
• Fix deployment by @ilgazer in #230
• added GeocodeControllerTest by @HarunErgen in #228
• Nasaapi end by @alperenDagi in #236
• Release 0.0.1 by @ilgazer in #237

New Contributors

• @alperenDagi made their first contribution in #159
• @alitpc25 made their first contribution in #158
• @GulbeycanCagri made their first contribution in #163
• @HarunErgen made their first contribution in #167
• @ilgazer made their first contribution in #185
• @volcaniqueo made their first contribution in #195
• @kubraaksux made their first contribution in #227

Full Changelog: https://github.com/bounswe/bounswe2023group1/commits/Group1-Practice-App-Release-v.0.1