Status Update #11

This Week:

• Links now open in a new tab instead of opening in the same window.
• Once user submits the URL, he gets a confirmation page and an option to go back to the results page
• Added “Caution” and “Safe Buy” images on the second page i.e. the results page.
• The website now loads in seconds, even on mobile platform.
• Added summary of Results section.
• Ethicheck motto statement (Changing lives through technological innovation): Changed color to blue, based on the survey feedback
• Added a "Go back to Homepage" button on the results page, based on feedback received from one of the users.
• Users can now start a new search on the second page (results page)
• Text box to submit user URLs has been moved to the bottom of the page within the user URLs section.
• Moved all data to the Cisco Server

Current Status:

The website has been fully functional since last week. Currently tweaking the website based on user suggestions and trying to add new features.

Next Week:

• Getting the common gateway interface setup on the Cisco Server.
• Adding more information into our wiki.
• Bug fixes for some companies - Creative Technology, Philips etc.

Status Update #10

User URL's feature

User submitted links

This Week:

• We added a new feature so now users can add relevant URL's to the website and other users can see them
• Users can also access our wiki from the website in order to create a non-existent page or to add information to an existent one
• We added more companies to our wiki
• We watched several videos about building apps in android 
• Result links now open in a new tab
• Added images to the results page
• The website now loads in second, even on mobile platform

Current Status:

• Our website is now fully functional. 
• After talking to Dr. Hammond about it we decided we are not developing the app as it will be too time consuming and we want to be able to focus more on the website. 

Next Week:

• Add a summary of the results at the top of the website (example: "icon of thumbs up" 5 "icon of thumbs down" 4)
• When users want to add a URL we will redirect them to another html page that will ask them for title, url, and classification. We will do this in order to classify the users links as well.
• Allow users to state whether a link is correctly classified or not
• Transfer the website to the NAS server  

Status Update #9

This Week:

• We are now crawling our own wiki! So we are giving links to our own wiki as part of the results. Also, if the company page does not exist in our wiki we provide a link for people to create it if they want to.
• We added many more company pages to our wiki.
• We expanded our training set, and now the results are much more accurately classified.

Current Status:

• Our website is now fully functional. We are beginning to look into developing an android app.  

Next Week:

• After deciding to develop an android app instead of a wp7 app we will start reading and watching tutorials about it.
• Develop the last feature for the website: to allow users to share links of relevant information.
• After the last feature is done we will concentrate completely on the android app for the next couple of weeks.

Status Update #8

This Week:

• This week, we got to the python code to compile on the web server using the common gateway interface.
• We have fixed the bugs in the classification algorithm.
• We expanded our training set, however, we still need a lot more documents in our training set to improve the performance of our classifier.

Current Status:

• Our website is now fully functional. We have fixed most of the bugs. To improve the relevance of the results found, we need to keep adding articles into our train set.

Next Week:

• Starting next week, our main area of focus will be the Windows 7 phone application development.
• After some research, we came to know that IronPython can be used to compile Python codes on windows 7 phone environment. We need to get acquainted with the functionalities of IronPython.

Spring Break March 12 - March 20

Status Update #6

This Week:

• Previously, we were hosting our website and wiki on CSE Cisco Server. However, anyone who needs to access the website needs VPN access into the CSE firewall, so we decided to move our website on a different web server.
• Now, our website is hosted on my desktop computer running apache webserver. The website can be reached using this link: http://74.194.129.16/ethicheck/ethicheck.html
• Classification algorithm has been implemented and we have a working prototype of our website. There are a few bugs in the implementation of the classification algorithm which we are trying to fix.
• Limitations: The training set (test bench) is currently limited.

Current Status:

• We almost have a working prototype of the website. (We do have a few minor bugs that need to be fixed) However, it is somewhat crude since the information sources are limited (NY times and Wikipedia). Also, the test bench is relatively small. Information can be manually added later into our wiki which we are using as our database.

Next week:

• Add information into the wiki and also crawl the wiki.
• Start developing the windows 7 phone application. We don't plan to stop the work during the spring break, however, the work might slow down due to the team members being in different cities during the week.
• Research: getting python code to compile on windows 7 mobile platform.

Status Update #5

Website Screenshot

Wiki Screenshot

This Week:

• Setup the web server.
• Installed Python and MediaWiki on the Web Server.
• Host the Ethicheck website on CSE Linux Web Server.
• Host the Wiki on CSE Linux Web Server.
• Researched the best classification tool to be used.
• Currently in the process of implementing the classification algorithm.
• Met with Dr. Gill and got ideas about collecting information about companies.

Current Status:

• We are close to develop a working prototype of the website which will show how users can search information and contribute to information using our wiki.

Next Week:

• Connect the python code with the web interface using either Common Gateway Interface (CGI) or Web Server Gateway Interface (WSGI). This step will be the final step towards creating a working prototype.
• Implement the classification algorithm using the Natural Language Tool Kit (NLTK).
• Start researching about how to develop the phone app and deploy it on windows phone platform.