4.1 Categories
The system will automatically retrieve user experiences into different categories like
“Attractions”, “Food”, “Sports”, ”Festivals” and “Night Markets”.
4.1.1- Attractions Category
Attractions category automatically retrieve all user experiences related to attractions from the Facebook timeline. Figure 4.1(a) shows all user experiences from the attractions category. Figure 4.1(b) shows one of the selected links of the user experiences. Figure 4.1(c) details of the selected link.
In this section, we followed the entire algorithm defined in the 3.3.1 section except the 14thstep of the algorithm. Instead of the 14thstep of the algorithm we followed below steps:
1.
Check string liststr for “name”, “message” in list1 using Contains () method. If yes, retrieve message values.2.
Check for the existence of multiple strings like attractions, park, beautiful place, zoo etc.in the message. If one or more strings available in the message, retrieve name, message values.
3.
Check for link of the post. If yes, retrieve string value of link4.
Repeat these steps for each post in the list1 using “foreach statement”.46
Fig. 3.4.1(a) User Experience from the attraction category
Fig. 4.1(a) User experiences from the “Attraction” category
Fig. 4.1(b) Selected link from the “Attraction” category
Fig. 4.1(c) Details of the selected link
47 4.1.2- Food Category
This category automatically retrieves all user experiences related to food from the Facebook Timeline. Figure 4.2(a) shows user experiences from the food category. Figure 4.2(b) shows one of the selected links of the user experience. Figure 4.2(c) shows the details of the selected link.
In this section, we followed the entire algorithm defined in the 3.3.1 section except the 14thstep of the algorithm. Instead of the 14thstep of the algorithm we followed below steps:
Check string liststr for “name”, “message” in list1 using Contains() method. If yes, retrieve message values.
Check for the existence of multiple strings like food, dinner, lunch, delicious, taste etc. in the message. If one or more strings available in the message, retrieve name, message values.
1.
Check for link of the post. If yes, retrieve string value of link2.
Repeat these steps for each post in the list1 using foreach statement.48 Fig. 4.2(a) User experiences from the “Food” category
Fig. 4.2(b) Selected link to view details
Fig. 4.2(c) Details of the selected link
49 4.1.3- Sports Category
This category system automatically retrieves all user experiences related to the sports category from the Facebook Timeline. Figure 4.3(a) shows user experiences from the food category.
Figure 4.3(b) shows selected link of the user experience. Figure 4.3(c) shows the details of the selected link.
In this section, we followed the entire algorithm defined in the 3.3.1 section except the 14thstep of the algorithm. Instead of the 14thstep of the algorithm we followed below steps:
1.
Check string liststr for “name”, “message” in list1 using Contains () method. If yes, retrieve message values.2.
Check for the existence of multiple strings like sports and sports related differentkeywords in the message. If one or more strings available in the message, retrieve name, message values.
3.
Check for link of the post. If yes, retrieve string value of link4.
Repeat these steps for each post in the list1 using foreach statement.50 Fig. 4.3(a) User experiences from the “Sports” category
Fig. 4.3(b) Selected link of the user experiences
Fig. 4.3(c) Details of the selected link
51 4.1.4- Festivals Category
This category system automatically retrieves all user experiences related to the festivals category from the Facebook Timeline. Figure 4.4(a) shows user experiences from the food category.
Figure 4.4(b) shows selected link of the user experience. Figure 4.4(c) shows the details of the selected link.
In this section, we followed the entire algorithm defined in the 3.3.1 section except the 14thstep of the algorithm. Instead of the 14thstep of the algorithm we followed below steps:
1.
Check string liststr for “name”, “message” in list1 using Contains () method. If yes, retrieve message values.2.
Check for the existence of multiple strings like festivals, events, functions etc. in the message. If one or more strings available in the message, retrieve name, message values.3.
Check for link of the post. If yes, retrieve string value of link4.
Repeat these steps for each post in the list1 using foreach statement.52
Fig. 4.4 (b) Selected link to see details
Fig. 4.4 (a) User Experience from the “Festivals” category
Fig. 4.4 (b) One of the selected link from the festivals category
Fig. 4.4 (c) Details of the selected link
53 4.1.5- Night Markets Category
This category system automatically retrieves all user experiences related to the Night markets category from the Facebook Timeline. Figure 4.5(a) shows user experiences from the food category. Figure 4.5(b) shows selected link of the user experience. Figure 4.5(c) shows the details of the selected link.
In this section, we followed the entire algorithm defined in the 3.3.1 section except the 14thstep of the algorithm. Instead of the 14thstep of the algorithm we followed below steps:
1.
Check string liststr for “name”, “message” in list1 using Contains () method. If yes, retrieve message values.2.
Check for the existence of multiple strings for night markets in the message. If one or more strings available in the message, retrieve name, message values.3.
Check for link of the post. If yes, retrieve string value of link4.
Repeat these steps for each post in the list1 using foreach statement.54 Fig. 4.5(a) User experience from the “Night Markets” category
Fig. 4.5 (b) One of the selected link from the “Night Markets” category
Fig. 4.5 (c) Details of the selected link
55 4.2 Query Based Search
In this section, we can search data by using query. There are two types of query based search: 1) Keyword based search 2) Like based search.
4.2.1- Keyword Based Search
Using the keyword based search, we can search data using any keyword like food, foo, place, sports, festivals etc. If we search user experiences using “food” keyword, then it will check is there any string which starts from food keyword. If yes, then all user experiences containing with
“food” keyword will be pulled with the name, message and URL link of the posts. Figure 4.6(a) shows user experiences from the Facebook Timeline. Figure 4.6(b), 4.6(c) shows keyword to search, results from the search keyword.
In this section, we followed the entire algorithm defined in the 3.3.1 section except the 14thstep of the algorithm. Instead of the 14thstep of the algorithm we followed below steps:
Check string liststr for “name”, “message” in list1 using Contains () method. If yes, retrieve message values.
1.
Check for the user entered keyword in the message. If yes, retrieve name, message values.2.
Check for “link” of the post. If yes, retrieve string value of link.3.
Repeat these steps for each post in the list1 using foreach statement.56 Fig. 4.6 (a) Keyword based query box
Fig. 4.6 (b) Searched results
Fig. 4.6 (c) Details of the selected link
Keyword Based Search Box
Searching data for
“Flying” keyword
57 4.2.1.1 - Search User Experiences from Taipei City
4.3
Fig.4.7 (a) Searched Results from the Taipei City
Fig.4.7 (b) One of the selected link
58 4.2.1.2 - Search User Experiences from Taichung City
The application is not only limited to Taipei city but also It can be useful to search user experiences from other cities. For example, users can search user experiences from the Taichung city. Figure 4.8(a), 4.8(b), 4.8(c) shows searched results from the Taichung city, one of the selected link and the details of the selected link.
Fig. 4.7(c) Details of the selected link
Fig. 4.8(a) Searched results from the Taichung City
59 4.2.2- Like Based Search
Like based search used to search all user experiences based on number of likes. For example, we can search user experiences whose number of likes is 2. Here we used three Facebook accounts, one is developer’s account and other two accounts are the friend’s accounts who installed the
Fig. 4.8(b) One of the selected links
Fig. 4.8(c) Details of the selected link
60 application. Figure 4.9(a) shows user experiences from the developer’s and friend’s accounts.
Figures 4.9(b) User experiences with number of likes are 2.
In this section, we followed the entire algorithm defined in the 3.3.1 section except the 14thstep of the algorithm. Instead of the 14thstep of the algorithm we followed below steps:
1.
Check string liststr for “name”, “message” in list1 and like_count using Contains () method. If yes, handle code to check number of user entered no. of likes available in the list1. If yes, retrieve name, message and link with the user entered no. of likes.2.
Repeat these steps for each post in the list1 using foreach statement.Fig. 4.9 (a) “Like based search” box
Like Based Search Box
61 4.3 Multiple Timelines
The section automatically retrieves user experiences in pictures and videos category from Facebook. Here, we showed screenshots from multiple timelines.
4.3.1- Pictures Category
In this category, we implemented a mechanism to automatically retrieve all shared pictures from the developer’s as well as friend’s accounts with name, message and link of the post. Here we used three Facebook accounts (Multiple Timelines), one is developer’s account and other two accounts are the friend’s accounts who installed the application.
Figures 4.10(a) shows all posted pictures with name, message and link of the shared posts.
Figures 4.10 (b), 4.10 (c) show the selected URL of the posted picture to view details and details of the selected URL of the post (developers account). Figures 4.10(d), 4.10(e), 4.10(f), 4.10(g)show the selected URL of the posted pictures and details of the selected URL of the post (friends account).
In this section, we followed the entire algorithm defined in the 3.3.1 section except the 14thstep of the algorithm. Instead of the 14thstep of the algorithm we followed below steps:
Fig. 4.9(b) User experiences with number of like 1
Searched data with number of likes 1
62
1.
Check string liststr for “name”, “link” in list1 using Contains () method. If yes, check for pictures. Again if yes, retrieve name, message and link with the user entered no. of likes.2.
Repeat these steps for each post in the list1 using foreach statement.Fig. 4.10 (a) posted pictures from developers and friends accounts
63 Fig. 4.10(b) One of the selected links from the posted picture (developer’s account)
Fig. 4.10(c) Details of the selected link
Developers account
64 Fig. 4.10(d) One of the selected links from the posted pictures (friend account)
Fig. 4.10(e) Details of the selected link of the posted picture