Customer Meeting Notes #1 - bounswe/bounswe2024group9 GitHub Wiki
Meeting Information
Date: 14.03.2024
Time: 17.05
Online/Offline: Offline
Location: BM #35
Duration: 1.5 hour
Note Taker: Elicitation Team
Attendees
- Suzan Uskudarli
- Mustafa Atak
- Eray Eroğlu
- Huriye Ceylin Gebeş
- Kristina Trajkovski
Agenda
A conversation with Suzan teacher about the progress of our ideas
Meeting Notes with of our questions and answers
1 - Can third-party platforms be used to log in? If available, which ones should be (Gmail, Facebook)?
One working login system should be prepared by the end of the semester, but although it would be nice to add such different systems, it is not mandatory. It is best to add it to the requirements as nice to have, but it would not be a problem if it is not completed as it may be overwhelming to implement.
2 - Should logins and registers be via e-mail or username?
It would be best to use both. Username makes the person's login simpler, but providing a backup method for the user in situations that require sending e-mail, such as forgetting a password, will be beneficial for everyone. That's why both usernames and hymn emails should be used.
3 - Should there be private profiles?
Having private accounts can be useful for many people, but it's better to think of them as nice to have for now.
4 - What will be shown when the person reaches the end of the feed or explore? What should the feed look like for a newly joined user with no followers, no following?
You don't need to post anything(first quick answer), but if we think about it in more detail, asking users some questions about what they like when they sign up and posting a post accordingly can help you show something to show for "cold users". As a different option, it might be a good start to present the posts that are famous on the platform at that time to the user.
5 - Would it be better to mix the posts made with explore in terms of page fullness, or should they remain on separate pages?
It may make sense to do it until the end of the term, but it may be difficult to implement, so it is nice to have, but it is not mandatory, but Feed should definitely be.
6 - To create a route, can location searches be added to the left, like Amazon Chart, and additions can be made there?
(The idea was liked and for those who wanted to add information to the existing route, the idea of making additions for each piece called "node" on the route was discussed. It may be called a "re-routing")
7 - How should groups be formed while performing these tasks?
In order to keep learning at the highest level, everyone should have done some work in every field, such as requirements elicitations mockup. It would be more beneficial for you to separate the teams with options such as login search feed or web mobile.
8 - What precautions should be taken in case the person forgets the password, such as sending an e-mail, giving a one-time password and asking security questions?
You can do it any way you want
9 - Will comments sent by people we follow on others' posts be displayed first?
It would be a good thing to do, in fact, putting a filter in the comment section might be a good choice. (Letterboxd platform may be a good example for that idea.)
10 - By obtaining location permission from the user, we can make the explore page easier by showing routes with locations around it. What do you think?
It's a very good idea, it may make your work easier for "cold start users".
11 - Should the interactions of people we follow with people we do not follow in chain interactions be included in our feed?
It's a logical idea to diversify the content in the feed. If A follows B and B follows C, person A may see content in their feed related to a comment B left on C's post.
12 - The user followed a shared route and wants to convey his personal experience. Should the post be in the form of commenting or should he be able to modify the route for himself and share it?
It would be better to have both, add both
13 - How can Wikidata be used more actively?
If we go through an example, if a person searching for Topkapi Palace also finds personal information about Mehmet the Conqueror in the wikidata, it would be beneficial to have it linked to the text for more active use.
14 - What are your suggestions for search bar filters?
The search bar can look at wikidata queries for filters (Historic etc can be used). With Ntlk NLP tools, entities can be extracted from the text the user writes on the route and searched accordingly.
15 - Should there be a reporting system for posts? Should there be blocking? How should they be handled?
It would definitely make sense. They may give people wrong routes and expose them to situations such as theft. Therefore, downvote and report route options should be added and what is reported should be checked by admin users.
16 - How can we add restrictions to new users joining to deal with situations like bot accounts?
A daily route sharing limit for each new user would be good, perhaps a length limit could be added to the shared route.
Action Items
| Item | Responsible Person | Due Date | Relevant Issue |
|---|---|---|---|
| Inform the rest of the team about meeting | Kristina, Eray, Ceylin | 15/03/2024, 23:59 | #Issue 75 |
| Prepare the page about customer meeting | Mustafa (Mutti) | 16/03/2024, 23:59 | #Issue 74 |