Stakeholder Meeting (10.03.2026)

Participants

• Stakeholders
  • Yusuf Anıl Yazıcı
  • Arda Saygan
• Group Members
  • Buğra Keser
  • Cansu Er
  • Mehmet Kaan Ünsel (Partially)

Agenda

• Introduction of the Social Event Mapper project
• Presentation of the current system concept and requirements
• Collecting stakeholder feedback and suggestions

Discussion Summary

Event Location and Navigation

• Events should include a direct pinpoint location using Google Maps integration.
• When users click on the location, Google Maps should open automatically, allowing them to view the location and obtain directions.
• The project closely resembles location-based event applications such as Luma, which the team can use as an example.

Event Interaction

• Each event should have a discussion/comment section.
• Users can use this section to discuss event details, ask questions, or provide additional information about the event.

Tagging and Categorization

• Users should be able to suggest categories for events.
• The system should ensure consistent data entry so that event information remains structured and reliable.
• Users may be allowed to create custom tags when existing categories are not sufficient.

Moderation and Ethical Considerations

• Events containing hate speech, harmful actions, or unethical content should be reviewed by moderators.
• Such events may be restricted or banned if they violate platform policies.
• Users should be able to report events that they consider inappropriate or harmful.

Additional Notes

• QR codes will not be displayed on the web version of the platform.
• Stakeholders provided feedback regarding improving the clarity and consistency of requirement language.

Decisions

• Events will include Google Maps pinpoints with the ability to open directions.
• Events will include a discussion/comment section.
• A tagging system will be supported, including suggested categories and custom tags.
• A reporting mechanism will be implemented for users to report problematic events.
• Moderation rules will be established to review and potentially ban unethical or harmful events.
• QR codes will not be shown on the web interface.
• Requirements documentation will be updated to improve clarity and language consistency.

Action Items

• Update the Requirements Wiki page with new features discussed in the meeting.
• Document the event reporting and moderation workflow.
• Add event discussion/comment functionality to the system design.
• Update tagging requirements (custom tags and category suggestions).
• Link this page in the Meeting Notes navigation of the project wiki.