With this outburst of data in recent years, it's a tough task for a user to select and pick a nice movie for watching. Also, with the huge options and preference choice made easily available, selection of data in a particular domain is not at all easy. Recommender systems are used to provide new personalization and also to showcase existing recommendations. These recommender systems can be used for recommendations on various domains like books, songs, jokes, news, online products and not limited to movies.
Research and literature survey suggest various approaches to creating an RS. Also, it is important to note that an RS has its own positives and negatives and we should be careful while selecting a suitable approach for implementation.
The most commonly used approaches of RS are via Collaborative Filtering methods and Content-based filtering techniques. IDMRS makes use of a logical combination of both these approaches and hence is hybrid in nature.
Till now, there are not many details available about demographic personalization for the movie domain except . IDMRS makes use of recommending personalization to a user in five regional languages: Kannada, Hindi, Telugu, Tamil and Malayalam. This way we were able to concentrate mainly on the South Indian dialect languages.
IDMRS could group users based on attributes like age, gender. The personalization produced by IDMRS could determine the user’s need for a movie recommendation. A movie recommendation was based on the similar movie taste given as an input or a completely new movie. The same was achievable for a new user as well. A new user could get a movie recommendation based on previous interests and preferences or a completely new movie as a recommendation. This way the common cold-start problem faced in RS was avoided to a certain extent. To be precise, a new user lacks good recommendations due to lack of enough ratings. IDMRS utilizes the user demographic data to avoid cold-start problems.
IDMRS was able to customize movie name generations. That is, the demographic information available can be used to provide customized personalization as per the language of choice.
One of the most common problems of available movie data sources like Netflix, Amazon Prime, and now the new Jio Movies, Airtel Movies, Flipkart videos is the lack of a comprehensive list of Indian movies.
Also, it is unfortunate to note that except Netflix, these data sources do not provide their dataset for research and future learnings.
・ A web portal for the curated dataset collection of data: A web portal where a user signs up by filling demographic data. Then the user can provide a like or a dislike as a movie rating.
・ Indian Demographic Movie Dataset: With the implementation of IDMRS, we were able to create a dataset of Indian Demographic Region and especially for the South Indian dialect languages.
・ Analysis of the data: We made use of a logical combination of content and collaborative techniques for filtering and analysis of this regional dataset.
2. Related Work
In  an Indian regional movie dataset the very first of its kind-database of regional Indian movies, users and their ratings is created. It consists of movies from 18 regional languages, capturing ratings from 919 users and for 2851 movies.
The analysis of this dataset is done using some supervised and unsupervised collaborative filtering techniques like Probabilistic Matrix Factorization, Matrix Completion, and Blind Compressed Sensing etc.
In  the researchers make use of the MovieLens dataset  and try to exploit the user demographic attributes for solving the cold-start problem in the Recommender System. The paper is structured into overall five phases where in the last phase they also provide directions for future research after the MovieLens dataset is evaluated.
Also, this paper suggests a novel framework to solve the cold-start problem by the utilization and influence of demographic attributes on user ratings and also to assist the RS to improve its recommendations.
3. Proposed Approach and Work
The IDMRS recommendation generation for a user works at five stages:
I. Data collection
II. Similarity index calculation
III. Recommendation generation
IV. Recommendation evaluation
V. Presentation to users or regeneration of recommendations.
For IDMRS, the similarity index calculation and recommendation generation are both demonstrated in a single phase.
The workflow of IDMRS is shown in Figure 1.
Table 1 is the description of user demographic data.
Each user would need to register and login into the site before able to see recommendations or even before rating a particular movie. This also made sure that a session was maintained all the time till logout. The IDMRS also can be considered as a session-based RS.
Table 2 shows the description of tables in the IDMRS.
3.1. Metadata Information
The IDMRS dataset was constructed in the Phase-1: Collection of data consisted of majorly three tables: User, Movie and Ratings as in Table 2. The user description
Figure 1. The workflow of IDMRS.
Table 1. User demographic data in encrypted format.
Table 2. Description of tables in IDMRS.
is described in Table 1.
Table 5 gives the overall picture of the curated dataset.
3.2. Calculation of Similarity Index and Generation of Recommendations
First of all, the curated dataset had a train/test split ratio of 8:2. In our work of
Table 3. Desc of movie table.
Table 4. Desc of ratings table.
Table 5. Curated dataset details.
calculating the similarity index and generation of recommendations, we created a Hybrid Recommender for our approach.
A hybrid recommender is one which makes use of logical combinations of both content filtering and collaborative filtering techniques. Hybridization techniques are further classified as monolithic design, parallelized design and pipelined design of hybridization .
Our approach makes use of a monolithic hybrid design model where in for the:
Input: User Id and Movie name
Output: Similar movie based on the input movie name and sorted on the basis of expected ratings by that particular user
Also, to make sure that we had our hybrid recommender design working, we split our implementation to work on and see the results of these recommenders:
1. Popularity recommender
2. User based recommender
3. Item based recommender
For the popularity recommender, we used Top-N functionality, where in N is most popular set of films as per the count of user ratings sorted from high to low.
In the case of User based recommender, cosine similarity index was used. The similarity index is defined as in (1)
Hamming distance was used for similarity in the case of Item based recommender system. One of the reasons for using Hamming distance was, we used movies of same language and length or duration greater than 2 hours as a feature vector for item based recommender system and in presented binary format.
The hamming distance between 2 movies say A and B with “ ” as the feature vector is as defined in (2)
The recommendations of movies with highest value of cosine similarity to a value of 1 and the least hamming score were generated.
Table 6 depicts an example of the hamming distance calculated between 2 movies of the same length:
Note that, the hamming distance of unequal lengths is always 1 and equal lengths is a binary 0 value. All such movies where in the hamming distance was 1 was calculated and grouped together.
The hybrid recommender made a logical integration of user based recommender with item based recommender.
3.3. Evaluation of the Recommendations
Common Modelling Metrics Used in Recommender Systems
The evaluation metrics used in our approach is Mean Absolute Error (MAE) and Root Mean Square Error (RMSE). They are the most common modelling metrics used in the case of Recommender Systems .
MAE and RMSE are defined as in (3) and (4)
Table 7 shows the MAE and RMSE evaluation modelling metrics of the IDMRS.
The IDMRS was able to generate recommendations by also utilizing the demographic attributes and the metrics had a fair amount of improvement.
Table 6. Hamming distance for movie with duration as a feature vector.
Table 7. Evaluation of IDMRS models.
Table 8 displays the demographic attributes used for better recommendations.
3.4. Presentation of Recommendations to Users
Though the complete IDMRS site was developed using the open source PHP framework, Python language code was used on the dataset to obtain recommendations.
We had to execute Python scripts within PHP and display the outputs back onto PHP. We came across  to solve this issue. The escapeshellcmd and shell_exec() functions were used to call Python within PHP.
4. Results and Discussion
In this section, we run our model for Precision, Recall and F-measure score of the generated recommendation list.
Precision, also called the positive predicted value, as in this case of IDMRS is the fraction of relevant movies predicted by the system to the overall retrieved movies. A movie is relevant when its rating is greater than or equal to 3.8 or else it is irrelevant and this is fetched from the curated dataset.
Precision is defined as in (5)
Likewise, recall is the number of related movies predicted by the model to the total number of relevant movies.
A recommended movie is also the predicted movie whose rating is again greater than or equal to 3.8 and this is the output or the result of the prediction algorithm.
Recall is also called sensitivity. It is defined for our IDMRS as in (6)
Finally, the mean between the precision and recall is measured by a score called F-Measure. When the measure is having a value of 1―then it means that, we are giving equal significance to both precision and recall.
Now F-Measure becomes F-1 (as in equality to a value of 1 to both precision and recall).
F-1 measure to our IDMRS is derived as in (7)
Table 8. Demographic attributes used for IDMRS improved recommendations.
Table 9 depicts the precision, recall and F-1 scores for the user with UserId-5 for the IDMRS hybrid recommendation output. The Trial I and Trial II details are depicted as per Table 10(a) and Table 10(b), through the confusion matrix. The train to test split was an 8:2 ratio.
For the few trials done, for our model of IDMRS, we were able to achieve a precision of nearly 50% and recall of more than 50%. We are able to achieve an F1-score of 54%. The F1-score denotes the performance of the Recommender System. The higher the value, the better it is.
One of the observations made during the run of IDMRS was, with higher number of trials and an aggregated average of Precision and Recall taken, the performance of the RS could improve drastically.
Also with the addition of more number of demographic attributes and fine tuning of the same, the F1 score could raise by at least another 10%. These attributes observed are could be the movie maker characteristics, the genre or the type of the movie.
Unfortunately when the IDMRS dataset size is compared with the other existing movie datasets, the size of IDMRS is very small and tiny. Adding more attributes and increasing the size of the dataset is discussed in challenges.
These are a few of the challenges faced while working with our work:
➢ The total number of Indian languages is 22 in . The collection of data for these 22 languages is indeed a herculean task.
Table 9. Precision, recall and F1 score.
Table 10. Confusion matrix with TP, TN, FP & FN values for 2 trials. (a) The trial-I values; (b) The trial-II values.
➢ The data collected for the 5 languages of our implementation is only for a period of 5 years. If all of the year’s data needs to be collected, then it's not an easy task and is indeed a difficult challenge.
➢ We should understand the restriction of data and the huge sizes of movies in different formats. The dataset of IDMRS only stored the metadata of movies. Storing the physical movies is not easy and may not be needed as well.
➢ The attributes used for producing demographic outputs are few in number. If the dataset has more number of fields as demographic data, then procuring recommendations out of them has many numbers of permutations and combinations.
6. Conclusions and Future Work
In this work we provided a novel approach of evaluating the demographic attributes available in the curated dataset to provide and recommend movies to new users. The movies were sometimes the popular ones recommended and few times absolute new users were provided with interesting movies; thus the problem of cold-start was also avoided to an extent.
The IDMRS can be also considered as a session-based RS. All the operations of the RS had to be done with the user logged-in.
Further work and research can be done using the dataset of IDMRS. More number of options for obtaining hybrid recommendations can be made if there are a numerous number of demographic attributes, which can be added to the curated dataset through web scraping or any other feature.
Finally, the same approach of working with movies as in the case of IDMRS can be applied to other domains as well. IDMRS can work as a generic platform.
 Exploiting User Demographic Attributes for Solving Cold-Start Problem in Recommender System.
 Calling Python Files within PHP.
 Over 22+ Indian Languages.