-
Notifications
You must be signed in to change notification settings - Fork 1
Meeting #3 ‐ 01.10.2024
- 📆 Date: 01.10.2024
- ⌛ Duration: 15.00 - 17.00
- 📍 Location/Platform: Face-to-face in BM B5
- 📝 Note-taker: Ahmet Firat Gamsiz
- ✅ Ahmet Fırat Gamsız
- ✅ Isil Su Karakuzu
- ✅ Orhan Unuvar
- ✅ Ozan Kaymak
- ✅ Soner Kuyar
- ✅ Yusuf Aygun
- Review of game records availability in Wikidata and integration possibilities.
- Defining semantic search capabilities for the chess community platform.
- Finalizing community interaction mechanisms, including user-generated content and incentives.
- Structuring and organizing chess game data to enhance user engagement.
# | Details | Responsible | Due Date | Issue |
---|---|---|---|---|
1 | Gather platform requirements. | TBD | TBD | TBD |
2 | Create user interaction scenarios. | TBD | TBD | TBD |
3 | Develop mockups for core platform features. | TBD | TBD | TBD |
4 | Putting meeting note #3 | Ahmet Firat Gamsiz | - | #255 |
-
Chess game records from sources like Wikidata are limited, though metadata such as player names, titles, and Elo ratings are available. Detailed game records, particularly from Lichess, offer more comprehensive data, including opening moves and game progress, which will be critical for the replay and commentary features. While integrating game data, it's important to enrich the platform with this detailed information to support features like game replays, move-by-move analysis, and player tracking.
-
A semantic search will allow users to filter chess players based on specific attributes, such as country, age, Elo rating, title, and tournament participation. Additionally, metadata such as player rankings and participation history can be linked to user profiles.
-
Fostering meaningful interaction among community members is central to the platform. Features such as the ability to create posts, comment on games, follow/unfollow users, and create puzzles will provide the foundation for a dynamic and engaging community. Labelling and categorization systems (e.g., tournaments, tips, events, coaching) will help organize the content. These labels will also aid in making user-generated content structured and machine-readable, improving content management and accessibility.
-
One of the core features will be the ability for users to replay chess games, including options to annotate specific moves or game positions. Chess APIs will enhance this experience by providing real-time analysis, such as game statistics based on board positions. By enabling users to interact with the games through comments and analysis, the platform will encourage deeper engagement.
-
Chess puzzles will be another major component, with users able to create, rate, and comment on puzzles. A system of upvotes and rankings will incentivize puzzle creation, while high Elo-rated players will have more influence in puzzle approval.
-
To reduce data redundancy and optimize storage, only games with active user interactions (comments or annotations) will be saved to the platform’s database. This ensures the system remains efficient while still enabling users to engage with game data.
🏠 Home
- Communication Plan for CMPE451
- Responsibility Assignment Matrix(RAM) for CMPE451
- Requirements Document for CMPE451
- Project Plan for CMPE451
- Web Annotation Data Model (WADM) Documentation
CMPE352
- Domain Analysis - Video Games
- Wikidata Research
- Mobile Development Research
- Web Development Research
- Application Programming Interface (API) Research
- Repository Research
- Useful Resources
- Requirements
- Responsibility Assignment Matrix
- Project Plan
- Elicitation Questions
- Scenarios
- Mockups
- Milestone Report 1
- Use Case Diagram
- Class Diagram
- Sequence Diagrams
- Milestone Report 2
- Milestone Report 3
- Meeting #10 ‐ 15.05.2024
- Meeting #9 ‐ 08.05.2024
- Meeting #8 ‐ 17.04.2024
- Feedback Meeting - 17.04.2024
- Meeting #7 ‐ 27.03.2024
- Meeting #6 ‐ 22.03.2024
- Customer Meeting ‐ 17.03.2024
- Extra Meeting ‐ 15.03.2024
- Meeting #5 ‐ 13.03.2024
- Meeting #4 ‐ 06.03.2024
- Meeting #3 ‐ 28.02.2024
- Meeting #2 ‐ 21.02.2024
- Meeting #1 ‐ 16.02.2024