Elicitation Questions

Points of Interest

• Which sort of places are considered Points of Interest?
• How are Points of Interest added to a route?
• There are POIs defined by system users and ones already included in Google Maps API. How will we handle this distinction?
• What should the POI page include?
• What should the POI page not include? -Who shoul be able to access to POI’s which are not loaded from wikidata but created by users.

Routes

• What is the maximum length for a route?
• Will the routes be importable/exportable if so, in which format ?

Search results and the page design

• Should Explore be on a separate page?

• Should Explore be something that can continue endlessly?

• How will Explore be determined based on the user's previous likes, saves, and followed accounts?

• Will there be a refresh feature for Explore?

• Will there be any differences in how Explore posts are shown (e.g., interested, not interested)?

• Will Explore posts be shown more frequently as they are liked?

• Will the color theme of the Explore page be different from the feed?

• Will the Explore page have any other distinct features from the feed?

• How many posts should be fetched from the database for Explore, and what should the limit be?

• If Explore posts are limited, how will it be determined when the user reaches the limit?

• What is the best way to store liked posts in Explore to ensure that similar routes are shown more frequently in the future?

• What should be included in the search bar? (Profiles, route names, travel preferences)

• What should be the main result of the search? Routes, profiles, or travel options?

• Should these quick results be shown to the user instantly as they type in the search bar?

• Should the user search by applying filters in the search bar or filter the results after performing the search (similar to websites like Sahibinden.com)?

• Should the text entered in the search bar be searched across all databases collectively, or are there priority queries that need to be searched first?

• How can fetching and processing results from the query be implemented simultaneously as the user types in their search?

• Should the most searched keywords be stored along with their results in another database for faster retrieval?

• Are there any daily limitations on displaying routes to prevent scraping?

• What should be included on the result page?

• Can routes that use the location be placed below the location on the location result page?

• Can a section be added to the side, similar to an Amazon chart, for quickly adding the ongoing route to the location result page?

• Will the location result page include the location on the map?

• How will the display style change, if at all, based on the type of result (person, place, route)?

• What information about the person will be displayed on the result page?

• If the result is a route, will possible routes be listed or the most likely one be placed at the top?

• Can multiple types of results be shown harmoniously on the result page (e.g., person and route)?

• If there is harmony, will the space they occupy on the page be equal, or will one have more details than the other?

• What details will be shown to the user on the person result page?

• If the location of the result is to be shown on the map, should Google API be used simultaneously?

• If a map API is used, how can it be determined whether the result is a location or another category?

• How many results will be shown on one page, and will more appear as you scroll down? Will there be any limitations?