Movie Spot Download

Project Requirements (Refer to attachment for final details) The object of this project is to create a service that will download new Movie Trailer Commercials from [login to view URL] and save them along with airings Data from [login to view URL] to the clients Box account via API. The service should be written in PHP and use specific naming and file conventions to save the data. Box publishes platform development documentation that should speed up this implementation: [login to view URL] The code should be clearly organized and commented. It should contain clearly defined system parameters to configure the UID & PW of the account accessing Box and [login to view URL] API’s as well as other global parameters. The script will run as a cron job and should be invoked via command line. The script is expected to have good error handling mechanisms as well as an alert system if the job fails for any reason. We will grant access to the iSpot API test/development center while this tool is being developed. Accessing the Box sandbox/test site will be the responsibility of the developer. The service will access the iSpot API, find new spots for download, access the Box database via API, and save the new spots in the appropriate folders and creating new ones as needed per the structure that is provided. Downloads must happen on an hourly basis and times should not overlap in an effort to keep from downloading the same spot more than once. All data will be downloaded starting on first date software is run moving forward. No retroactive data will be needed. - Spots must be downloaded hourly - Spots will be saved in one of two file structures depending on the Spot Type In order to perform this operation the developer will use the iSpot “New Content” API to get a list of new spots for a given time range. Using the IDs provided from the “New Content” API output, the script will access the “Meta Data” API and identify the [adtypeid], the [adtitle], [duration], and [versionid] in order to create the proper naming conventions and store the spots in the proper locations. Also using the IDs provided by the “New Content” API, the script will access the “Download Content” API to get the download URL for each spot in order to download them and save them using the naming conventions as provided. Separately a large amount of data about these and other commercial spots will need to be downloaded and saved on a daily basis. This data will be delivered from the Airings API and can be pulled via a start and end dates. All available data fields from the Airings API should be included as its own column/field in the saved airings report. The Airings reports will be saved in a separate section of the box account as a CSV file. Again there will be a Theatrical and Home Media folder tree that should be kept parallel. The structure will be as follows on the theatrical side. • Airings data will be saved in one of two file structures depending on the Spot Type Included in the attachment is an example of the folder structure that should be used. Names using the [ ] are names that should be gathered using API and/or date fields. Anything not in [ ] should be kept as listed. Please note that on the Theatrical side there will be folders for each duration. Those folders should be saved in 15 second increments. For example there may be a 15, 30, 60 second folder. Some spots may have a duration that is not exactly one of those lengths but should be stored in the closest folder. For example, a spot with a 29 second duration should be stored in a 30 second folder. Also, on the theatrical side. Commercials that are type 3 should be stored in the duration folders while any commercial spot that is type 2 (promo) should be stored In the Promos folder regardless of duration. All commercials and data saved on the Home Media side of the file structure should be type 1 commercials and there will not be a need for a Promos folder.