Movie Explorer. Group Members: Name: Chen Wang JHED: cwang107 Section: 415 Name: Yang Xi JHED: yxi5 Section: 415. Domain Description:

Transcription

1 Movie Explorer Database Project (Phase II) Group Members: Name: Chen Wang JHED: cwang107 Section: 415 Name: Yang Xi JHED: yxi5 Section: 415 Domain Description: We are trying to build a movie explorer system in the format of an IOS app. The domain is relatively easy to understand. The data we use consists of detailed information about each movie and more related data like actors information, company s information and etc.

2 (1) Project Overview We try to build a movie explorer system and all of our data is collected from online API in the format of JSON. After the collection of data, we insert those data to our server side database, which are all deployed in AWS EC2. Then we complete the server side to support various queries through php + mysql. To reflect our work, we have implemented an IOS front end and the RESTFul communication between our php server and mobile client side. Some screenshot of our app are as follows: We can search the movie and actor through our app. In the backend it will execute some simple SQL query. And also, we could use filter to perform advanced query. The detailed project demo in gif could be found in: compute- 1.amazonaws.com/demo.html (2) Data resource 1. OMDB API: 2. Movie Database API : 3. MyAPIFilm API :

3 How we load data: Since the information we need are not fully included from the open data source provided from those three databases API, fortunately every id of actor and movie were actually from IMDB website and shared with those three databases, so that we would extract each information we need from each databases and integrate them to the table we designed. We have written the extraction code in php file, and put it on our server to let the the server grab the data periodically from the open source databases. The data was passed through REST. The image above has already indicated the information extraction workflow: 1. We have downloaded a small movie list which only contains movies titles from IMDB website;; 2. We began to look up the OMDB and MyFilmDB by the title of movie from the movie list. 3. The MyFilmDB will give us the list of actors concerning each movie and we would use it by sending the information to Movie DataBase and lookup the actor, company information.

4 4. After all the exchanged information step, we would integrate all the data into our designed table with different identifier. Although the MyFileDB and Movie Database have restricted the number of queries by 1000 per day, there are already 6,000 records which were stored in our databases and it s enough for the usage in our project. (3) User Guide IOS User guide: The front end of our project is an IOS app, written in swift language Therefore a Mac environment and XCode are required to run the code, either by simulator or iphone. In this case, we also provided a quick demo about how the app works. If you want to run the code, the requirements are as follows: 1. Xcode version or above 2. Target ios deployment 9.1 or above Then you can click the build and run button on the top left of the XCode. Create Tables: All the tables are specified in project phase I. We have submitted our SQL code for creating all the tables in the /sql/createtable.sql. Copy the code to the mysql console will bring you all the tables. Data Extraction: Before testing data extraction, please make sure your have already create all the tables we use in your sql and you should provide you own database, username, password to allow the code access your database. The data extraction code was provided in the file dataextract.php. The way use it is putting this file onto our server and let script run it. If you just want to see the result without insert the data into database, the simple way is put the php file onto your server and access it from internet. The information will be printed on the internet explorer, as follow:

5 (4) Specialization Complex information extraction, advanced GUI (5) SQL file Since the we extract data from online API, so all of our SQL files are embedded in php file. (6) Limitations Although our server side and database are capable of supporting complex queries, it is hard to implement that from the perspective of GUI and front end. Technically, we can achieve it, but it s almost impossible to give a good user experience as a ios app. (7) Future Improvement We can add a search box which support any keyword searching. In addition, a speech recognition can also be embedded in this system to solve complex queries which are difficult to implement in front end. Through some technique of natural language processing, we can identify the functionality of different keywords and then request a corresponding query to the server database. For example, if we say 2015 comedy and rating which is higher than 6.5, the system would recognize the different conditions and return all qualified results.