Customer Meeting #1 (28.02.2020)

1. Details

• Location: BM roof
• Date: 28.02.2020
• Time: 12.00 am

Attendees

• Halil Umut Özdemir

• Meltem Arslan

• Burak Ömür

• Öykü Yılmaz

2. Agenda

• Asking some questions to clarify the project description.

3. Meeting Notes - Questions and Answers

1. Is there admin user type in the system? If so, what are the capabilities of such users?

No, there is not. There is an admin panel but the admin is not a user but the founders of this site.

2. Should there be bots to make adjustment in the platform?

Not necessary but if you like, you can add it.

3. Is there any other group of users(like students) which have different capabilities or permissions in the system?

No, everyone has the same permissions. Registered users only specify their jobs while registering and it can be seen on the profile.

4. In the platform there will be a registration but for who wants to register with their Google Acconts etc, are there a registration mechanism with Google Account etc.?

Users can only register with their Google Accounts, and if they do their Google scholars account directly linked to the system.

5. Which information is necessary to register to the system?

Name, Surname, profile photo(optional), e-mail address, research interest, affiliates. Do not take too much information(since it can be a problem for KVKK.

6. If there is admin user type, how can they registered? Also how can they login the system?

There is no admin type.

7. Which information (e-mail, username etc.) is used for login?

There is no user name, it looks unprofessional. Users use their e-mail to register.

8. Should the editing system be detailed? Is a system like GitHub's is enough? Can the plots or the codes etc. can be created in the platform or is it like moodle, only submission?

It can be a simple text editor.

9. What are the topics/events that a user able to create? Conference/journal/project etc? and who can create what type of event, and join/apply them.

Users can create project/paper proposals. Conferences will be added using the API system. If a paper will be proposed to a conference, it will be indicated. Everyone can create these events since there are no difference between a student or a professor. If the proposal is private, users can only join them with invitation. Otherwise everyone can request to join the team.

10. When users post their ideas is specifying requirements an obligation or not?

This is for you to decide.

11. How the project\issue management and documentation will be done? Will it be like GitHub?

There can be an issue management system like a simpler version of Github. and a timeline like milestones. For project management, there will be tags which indicate the states(e.g application of collaborators, published paper or projects).

12. Do every collaborator have the same permissions to manage a project or do they have different privileges?

Yes, no one has different privileges in the team. It is optional for you to create a poll to kick a member out.

13. Is a version management system like git needed?

No need to do that.

14. Is there a rating and comment system for projects?

No there is not.

15. Can guests see the profile and past publishing of registered users?

This is for you to decide.

16. Who creates the conferences, only academicians or are there other users? Or do we retrieve info from other websites? Are they only for general info, or will the summary or videos be published in that page?

No user creates a conference, we use an API to extract the venues and dates of the conferences.

19. What will the profile page include?(Current issues of user, previous work, comments and ratings, etc.)

Any information given while registering and papers and projects currently and previously worked on, comments and ratings, following and follower accounts (if the user is public, everyone can see who they follow but if it is private only the followers can reach this information.

20. Who can evaluate the academicians? Guests/ (if any) students. Can any comment be deleted by the profile owner?

Guests cannot. Only users who have collaborated before can comment and rate each other.

21. Will there be private profile / public profile like in LinkedIn?

Yes and this can be selected while registering.

22. Are there filters in the semantic search or in any search? Which labels\tags (like start time, end time, topic, research area etc.) does the advanced search mechanism include?

Yes there will be filters and you can add any filter you think is useful.

23. Is there a way to search academician accounts in the search engine?

Yes, you can filter your search as people/project etc.

24. How does the recommendation system work? Do we tell the users why we matched them?

You do not need to do a learning level of recommendation system. For example if someone has 10 projects you should not recommend him/her just because he has a high rating.

25. Should recommendation system work for the guests?

No.

26. Will our app connect to external sites/apps (Slack, Trello, etc.) for easy contribution to the research?

No.

27. Do we create an in-app communication system for registered users? (chat, calls, etc.)

Not necessary for now.

28. Can users follow each other? Can they block someone?

Yes they can follow each other but no they cannot block anyone. They can report inappropriate activities.

29. What are your performance criteria? For example, what is the time limit for any function?

You can add some features you think of.

30. In which versions of Android or browsers is the product used?

After you specify, you can use any, but make it realistic(like do not say it will work for all android versions).

4. Action Items

	Person	Action	Deadline
1	Everyone attended	Brief the one's who did not attend	28.02.2020 17.00
2	Oyku Yilmaz	Prepare the Questions and Answers Page	28.02.2020 23.55