<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Towards Boosting Video Popularity via Tag Selection</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Elizeu</forename><surname>Santos-Neto</surname></persName>
							<email>elizeus@ece.ubc.ca</email>
						</author>
						<author>
							<persName><forename type="first">Tatiana</forename><surname>Pontes</surname></persName>
							<email>tpontes@dcc.ufmg.br</email>
						</author>
						<author>
							<persName><forename type="first">Jussara</forename><surname>Almeida</surname></persName>
							<email>jussara@dcc.ufmg.br</email>
						</author>
						<author>
							<persName><forename type="first">Matei</forename><surname>Ripeanu</surname></persName>
						</author>
						<author>
							<affiliation key="aff0">
								<orgName type="institution">University of British Columbia</orgName>
								<address>
									<settlement>Vancouver</settlement>
									<region>BC</region>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff1">
								<orgName type="institution">Univ. Federal de Minas Gerais Belo Horizonte</orgName>
								<address>
									<region>MG</region>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff2">
								<orgName type="institution">Univ. Federal de Minas Gerais Belo Horizonte</orgName>
								<address>
									<region>MG</region>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff3">
								<orgName type="institution">University of British Columbia</orgName>
								<address>
									<settlement>Vancouver</settlement>
									<region>BC</region>
									<country key="CA">Canada</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff4">
								<address>
									<postCode>01-04-2014</postCode>
									<settlement>Glasgow</settlement>
									<region>Scotland</region>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Towards Boosting Video Popularity via Tag Selection</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">90EEF79B1BA15BD97B3F4517F148A680</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T20:21+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Video content abounds on the Web. Although viewers may reach items via referrals, a large portion of the audience comes from keywordbased search. Consequently, the textual features of multimedia content (e.g., title, description, tags) will directly impact the view count of a particular item, and ultimately the advertisement-generated revenue.</p><p>This study makes progress on the problem of automating tag selection for online videos with the goal of increasing viewership. It brings two major insights: first, it describes a methodology to construct a ground truth to evaluate methods that aim to improve social content popularity; second, it provides evidence that the tags on existing YouTube videos can be improved by an automated tag recommendation process even for a sample of well curated videos; finally, it suggests a roadmap to explore low-cost techniques either based on crowdsourcing or on tag recommendation algorithms to improve the quality of tags for online video content.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Given the sheer volume content owners generate (e.g., YouTube receives 100 hours of video every minute 1 ), it is common they offload online publication and monetization tasks to specialized content management companies. Content managers publish, monitor, and promote the owner's content, and revenues are generally shared with the owner. As revenue is directly related to the number of ad prints each piece of content receives, this incentivizes managers to boost content popularity.</p><p>Although viewers may reach a content item starting from many leads (e.g., an e-mail from a friend or a promotion campaign in an online social network), a large portion of viewers relies on keyword-based search and/or tag-based navigation to find videos. An argument supporting this assertion is the fact that, as of 2/Dec/2013, 14% of the unique visitors on YouTube come from Google.com searches 2 . The integration of Google and YouTube search will likely increase the volume of search traffic that leads to views on YouTube. Moreover, YouTube itself is the third most popular site on the web.</p><p>Consequently, the textual features of a video (e.g., title, description, tags, and comments) have a major impact on the view count of each particular item and, ultimately, on the advertisement-generated revenues <ref type="bibr" target="#b4">[5,</ref><ref type="bibr" target="#b10">11]</ref>. Similarly, in other contexts, it has been shown that even simple textual features produce positive results: for example, title suggestions on eBay have benefitted both sellers, who increased revenue, and buyers, who found relevant products faster <ref type="bibr" target="#b4">[5]</ref>.</p><p>Experts can produce the textual features associated with video content via manual inspection (and our industry contacts confirm this is a still current practice <ref type="foot" target="#foot_0">3</ref> ). This solution, however, is manpower intensive and limits the scale at which content managers can operate. Therefore, mechanisms to support this process (e.g., automating tag suggestion) are desirable.</p><p>This study starts from the observation that, with the ever-increasing volume of user-generated textual content available on the Web, there is a plethora of sources from which an automated mechanism that suggests textual features, in general, and tags, in particular, could extract candidate terms that can improve multimedia content popularity. For example, Wikipedia (a peer-produced encyclopedia), MovieLens and Rotten Tomatoes (social networks where movie enthusiasts collaboratively catalog, rate, and annotate movies), New York Times movie review section (which includes over 28,000 movies) or even YouTube comments are potential sources of candidate keywords to annotate multimedia content such as videos. It is important to note that techniques to suggest textual features to improve multimedia content popularity are not restricted to movies. In fact, other types of content such as superbowl ads could benefit from a combination of information sources such as humans from a crowdsourcing service (e.g., Amazon Mechanical Turk).</p><p>To make progress on understanding whether textual information, tags in particular, associated with video content can be improved through an automated process, and on understanding what information sources provide the most valuable textual features (i.e., terms that can potentially improve videos popularity), this work focuses on the following research questions: Q1 What are the challenges in building a ground truth to evaluate popularity boosting of videos on social media via textual features optimization such as tagging with terms that can potentially improve the discoverability of the video via search? How can one leverage crowdsourcing channels such as Amazon Mechanical Turk for such purpose?</p><p>Q2 To what extent the tags currently associated with existing video content on social video-sharing websites, such as YouTube, are optimized to attract search traffic? Is there room for improvement possibly using automated tag recommendation solutions?</p><p>It is worth highlighting that, to tackle these questions, this work uses tag recommender algorithms in a different context than most previous studies: our goal is not to design novel and more efficient tag recommendation algorithms, but to study whether textual features of social content can be further optimize to improve the value of alternative data sources in providing tags to boost video popularity. In this sense, the mainstream recommender algorithms we use here provide a lower bound on the achievable quality. More complex algorithms, e.g., as proposed in <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b2">3,</ref><ref type="bibr" target="#b5">6,</ref><ref type="bibr" target="#b7">8]</ref>, can be tested and tuned using the methodology we propose here to further improve tag quality.</p><p>In particular, this study concentrates on the challenges related to constructing a ground truth to enable the evaluation information sources. Therefore, we adopt the following two-part methodology:</p><p>• Construct a ground truth by recruiting turkers from Amazon Mechanical Turk, asking them to watch YouTube videos, and to provide the keywords they would use to search for each of them, as opposed to simply describe the video (see Section 3);</p><p>• Prototype an automated tag recommendation pipeline, incorporate various recommender algorithms, and couple it with different input data sources (see Sections 2 and 4.1);</p><p>• Evaluate the tag quality of existing YouTube videos by comparing them with the ground truth (see Section 5);</p><p>In summary, the contributions of this work are:</p><p>• The production of a ground truth released to the community.</p><p>• Evidence that the tags associated with a sample of trailers of popular movies currently available on YouTube can be further optimized by an automated low-cost process. This process can either incorporate human computing engines (e.g., recruited through Amazon Mechanical Turk) at a much lower cost than using dedicated channel managers (the current industry practice), or, at an even lower cost, can use tag recommender algorithms to harness textual information from a multitude of data sources that are related to the video content.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Context of Our Assessment</head><p>This section describes the context for our investigation. Our main assumption is that annotating a video with the tags that match the terms users would use to search for it increases the chance that users view the video. This view is supported by previous studies <ref type="bibr" target="#b10">[11]</ref> and by the observation that a large portion of the traffic landing on a video comes from textual searches. As a result, textual sources that are related to the video and whose content can be automatically retrieved (e.g., movie reviews, comments, wiki pages, news items, blogs) can be used as inputs for recommenders to suggest tags for these video content items.</p><p>A recommendation pipeline that implements this idea is schematically presented in Figure <ref type="figure" target="#fig_0">1</ref>: data sources feed the pipeline with textual input data. Next, the textual data is pre-processed by filters to both clean and augment it (e.g., remove stopwords, detect named entities). This first processing step provides candidate keywords for the recommenders. The recommendation step uses the candidate keywords (and their related statistics, such as frequency and cooccurrence) to produce a ranked list according to a scoring function implemented by a given recommender algorithm. Finally, as the space available for tags provided by video sharing websites, such as YouTube or Vimeo, is limited, the selection of most valuable candidate keywords is constrained by a budget, often defined by the number of words or characters. Therefore, the final step consists of solving an instance of the 0-1-knapsack problem <ref type="bibr" target="#b1">[2]</ref> that selects a set of recommended tags from the ranked-list produced by the recommender.</p><p>In summary, the recommendation pipeline is composed of four main elements: data sources, filters, recommenders, and knapsack solver. The next paragraphs discuss each of these elements.</p><p>Data sources. This component provides the input textual data used by the tag recommenders. In particular, we are interested in peer-produced data sources such as Wikipedia and social tagging systems like MovieLens, as well as expert-produced data sources such as NYTimes movie reviews. We discuss in detail each of the data sources used in Section 4.1.</p><p>Filters. The raw textual data extracted from a data source is filtered to both clean and augment the input data, minimizing noise. We consider simple filters: stopword and punctuation removal, lowercasing, and named entity detection <ref type="foot" target="#foot_1">4</ref> .</p><p>Recommenders. A recommender scores the candidate keywords based on their relevant statistics (e.g., single word frequency, word co-occurrence frequency). Note that there are many ways of defining scoring functions; and, it is not our goal to advocate a specific one, as we focus on the value provided by various information sources. We discuss the recommenders used in this work in Section 4.2.</p><p>Knapsack Solver. Finally, after ranking candidate keywords, the final step is selecting the ones that best fit the budget. In this paper, the budget is expressed in terms of the number of characters, as done in video sharing systems such as YouTube, where one can use a limited number of characters (500) for tags. This step is formulated as a 0-1-knapsack problem.</p><p>Let v be a video and C =&lt; k i &gt;, i = 1, ..., n, be a list of candidate keywords provided by a data source when used as input to a tag recommendation algorithm. Additionally, let us denote the length of a keyword k i as w i in bytes. Therefore, the problem of selecting the best tags to improve viewership of v is equivalent to solving the following optimization <ref type="bibr" target="#b1">[2]</ref>:</p><formula xml:id="formula_0">maximize n i=1 f (k i , v)x i subject to n i=1 w i x i ≤ B</formula><p>where B is the budget in terms of number of characters allowed in the tags field, x i ∈ {0, 1} is an indicator variable, and f (k i , v) is a scoring function provided by the recommender for the keyword k i with respect to video v.</p><p>Considering that the cost<ref type="foot" target="#foot_2">5</ref> (i.e., the keyword length) and the scores are both nonnegative, we use a wellknown dynamic programming algorithm <ref type="bibr" target="#b1">[2]</ref> to solve this optimization problem.</p><p>Our goal is primarily to understand whether videos currently published on a popular social video sharing website have their tags optimized to attract search traffic. If tags can still be further optimized, one could evaluate how the choice of the data source used as input for a recommendation pipeline impacts the quality of the recommended tag-set. Next, we discuss how to build a ground truth that enables testing whether the tags assigned to a sample of videos available on a popular video sharing website are optimized. Additionally, such ground truth, in a future work, could enable the evaluation of potential data sources that provide candidate tags.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Building the Ground Truth</head><p>Our main assumption is that annotating a video with the tags that match the terms users would use to search for it increases the chance that users watch the video. As a result, textual sources that are related to the video and whose content can be automatically retrieved (e.g., movie reviews, comments, wiki-pages, news items, blogs) can be used as inputs for recommenders to suggest tags for these video content items.</p><p>The ideal method to collect the ground truth would consist of experiments that vary the set of tags associated to videos, and capture their impact on the number of views attracted. However, collecting this requires the publishing rights for the videos and implies executing experiments over a considerable duration.</p><p>We decided for an alternative solution: we built a ground truth by setting up a survey using the Amazon Mechanical Turk (AMT) <ref type="foot" target="#foot_3">6</ref> . The survey asks participants to watch a video and answer the question: What query terms would you use to search for this video? The rationale is that these terms would, if used as tags to annotate the video, maximize its retrieval by the YouTube search engine, and indirectly maximize viewership.</p><p>Content Selection. Our study focuses on movie trailers 7 . The reason is that they are often short (about 5 minutes or less), and this makes the evaluation process more dynamic, encouraging turkers (i.e., the AMT workers who accept to participate in the survey) to watch more trailers and associate more keywords to them. The dataset consists of 382 videos selected to meet the following constraints: they must be publicly available on YouTube and have available content in the data sources used to extract candidate keywords (e.g., a page on Wikipedia, a NYTimes review page).</p><p>Survey. First, we conducted a pilot survey by recruiting participants via our internal mailing lists and online social networks. Their task was to watch the trailers and provide terms they would use to search for those videos. This pilot highlighted two major issues: (i) relying only on volunteerism to mobilize participants was insufficient; and, (ii) quality control of answers (e.g., typos in the keywords) is much more difficult -all videos in the survey are in English and there was no automatic way to recruit only participants that are fluent in English.</p><p>Thus, we published an AMT task 8 requiring the turkers to watch trailers, and provide the query terms (3 to 10 keywords to each video, as queries are typically of that length <ref type="bibr" target="#b3">[4]</ref>) they would use to search for the videos they had watched. Following AMT pay guidelines, each participant was paid $0.30 per task assignment, which had an average completion time of 7 As long as there are data sources to extract candidate tags from, other content types can benefit from our methodology. 8 Links to data and code can be provided upon request. 6 minutes (total cost to conduct the survey: $345). This leads to $3 per hour, which is much cheaper than the wage paid to dedicated channel managers.</p><p>We also performed simple quality control by inspecting each answer to avoid accepting spam (which is expected to be rare, due to the reputation mechanism adopted by AMT). In fact, only one submission was rejected as unrelated URLs were assigned as answers instead of keywords.</p><p>A brief characterization of the ground truth. In total, 33 turkers submitted solutions. Figure <ref type="figure">2</ref> shows the number of videos evaluated per turker: as we can observe, 19 turkers (58%) evaluated more than 5 videos, with the maximum reaching 333 videos. Figure <ref type="figure">3</ref> shows a histogram presenting the number of different keywords each video received. Even though we asked the turkers to associate at least 3 keywords to each video, 82% of the evaluations provided more than the required minimum, which resulted in 96% of the videos with 10 or more different keywords.</p><p>Figure <ref type="figure" target="#fig_2">4</ref> presents the total number of characters in the set of unique keywords associated to each video. The length of the ground truth varies from 51 (min) to 264 (max) characters; in fact, 32% of the videos have tags summing up to 100 characters. These values guided the budget parameter in our experiments, as we explain in Section 4.3. To gain an understanding on what types of keywords would drive search traffic to these videos, we look at the set of most popular terms (overall) in the ground truth. Among the top 10% most frequent search terms provided by turkers, 68% of them are named entities (e.g., actor, director, and producer names). Another category of terms with strong presence is genre-describing terms. This suggests that a strategy that aim to boost popularity of videos by optimizing the tags associated with the content should use sources that provide named entities related to the video.</p><p>It is important to note that we found some evidence that this happens to videos other than movie trailer. In a smaller sample of Super Bowl ads videos, we observed that terms users provide as keywords they would use to search for the ads are also dominated by named entities like the brand names.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Experimental Setup</head><p>This section presents the instances of data sources and tag recommenders, as well as the success metrics used in our evaluation on whether the existing tags on YouTube videos are optimized.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Data Sources</head><p>To understand whether the tags assigned to existing online video content are optimized to attract search traffic, it is necessary to compare the current tags to a set of tags recommended by using other data sources as input.</p><p>Therefore, we use a combination of data sources as inputs to recommender algorithms to produce a comparison basis for the existing tags on the videos in our sample. Next, we describe each of these data sources:</p><p>MovieLens<ref type="foot" target="#foot_4">9</ref> is a web system where users collaboratively build and maintain a catalog of movies and their ratings. Users can create and update movie entries, annotate movies with tags, review and rate them. Based on previous user activities, MovieLens suggests movies a user may like to watch. For our evaluation, we use some of the data available in MovieLens: only the tags users produce while collaboratively annotating and bookmarking movies. This data is a publicly available trace of tag assignments <ref type="foot" target="#foot_5">10</ref> .</p><p>Wikipedia is a peer-produced encyclopedia where users collaboratively write articles about a multitude of topics. Users in Wikipedia also edit and maintain pages for specific movies <ref type="foot" target="#foot_6">11</ref> . We leverage these pages as the sources of candidate keywords for recommending tags for their respective movie trailers from our sample.</p><p>NYTimes reviews are written by movie critics considered experts on the subject. Similar to the data provided by Wikipedia, we leverage the review page of a movie as the source of candidate keywords for the tag recommendation task. The reviews are collected via the query interfaces<ref type="foot" target="#foot_7">12</ref> provided by the NYTimes API.</p><p>Rotten Tomatoes is a portal where users can rate and review movies. Moreover, users have access to critics' reviews and all credits information: actors and roles, directors, soundtrack, synopsis, etc. The portal links to critics' reviews as well. The information about the credits of a movie and the critics' reviews can be considered as produced by experts (likely the film credits are obtained from the movie producers, while the critics' reviews are similar to those from NYTimes). While users can review the movies as well (and this qualifies as peer-produced information), these reviews are available on the website, but not accessible via the API at the time of our investigation. The rest of the information about the movies together with links to the experts' reviews is available via the Rotten Tomatoes API <ref type="foot" target="#foot_8">13</ref> .</p><p>YouTube is a video-sharing website, here used to test whether the tags already assigned to videos can be further optimized. To this end, we collect the tags assigned to the YouTube videos in our sample from the HTML source of each video's page (API requests in this sense are only accessible by the video publisher). The reason for using page scraping rather than API requests is that videos' tags are accessible via the API only to the video publisher, even though these tags are still used by the search engine to match queries and are available in the HTML of the video page. YouTube data source figures in the expert-produced end of the spectrum since only the publisher can assign tags to the video (it is reasonable to assume that a publisher is an expert on the own video and aims to optimize its textual features to attract more views).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Tag Recommenders</head><p>The experiments use two tag recommendation algorithms that process the input provided by the data sources: Frequency and RandomWalk. We selected them primarily because they harness some fundamental aspects of the tag recommendation problem that more sophisticated methods (e.g., <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b5">6,</ref><ref type="bibr" target="#b8">9]</ref>) also use: tag frequency, and tag co-occurrence patterns. Moreover, our goal is to understand the relative influence of the data sources on the quality of the recommended tags. We note that the methodology we describe and the ground truth can be used to evaluate other, more sophisticated, recommender algorithms as well.</p><p>The Frequency recommender scores the candidate keywords based on how often each keyword appears in the data source. Given the movie title, our pipeline finds the documents in the data source that match the title and extract a list of candidate keywords. For example, in Wikipedia, the candidate keywords for recommendation to a given movie are extracted from the Wikipedia page about the movie, and its frequency are the number of times each one appears in that page. Similarly, in MovieLens, the frequency is the number of times a tag is assigned to a movie.</p><p>The RandomWalk recommender harnesses both the frequency and the co-occurrence between keywords. The co-occurrence is detected differently depending on the data source. In MovieLens, two keywords co-occur if they are assigned to the movie by the same user, while in NYTimes, Rotten Tomatoes, and Wikipedia two keywords co-occur if they appear in the same page related to the movie (i.e., review, movie record, and movie page, respectively). The RandomWalk recommender builds a graph based on keyword co-occurrence, where each keyword is a node.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Budget Adjustment</head><p>To make the comparison fair, for each movie trailer, we adjust the budget to the size of the tag set of that video in the ground truth. The knapsack solver uses this budget to select the recommended tags for a particular video. The reason for setting a budget per video is that a number of recommended tags greater than the ground truth size penalizes some evaluation metrics, such as the F3-measure (see definition below).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.4">Success Metrics</head><p>The final step in the experiment is to estimate, for each video and for various input data sources and recommender algorithms, the quality of the recommended tag-set against the ground truth. To this end, we use F3-measure. Let T v and S v be the set of distinct keywords in the ground truth and in the recommended </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Experimental Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>This section presents our experimental results to address the following research questions:</head><p>To what extent the tags currently associated with existing YouTube content are optimized to attract search traffic? Is there room for improvement using automated tag recommendation solutions?</p><p>To address these questions, we perform an experiment to assess the quality of tags already assigned to existing YouTube videos and whether there is room for improvement. By improvement we mean extending/modifying the tags to better match the ground truth. To this end, we compare the tags to the ground truth for each video and observe a wide gap. The dotted (blue) line on the left in Figure <ref type="figure" target="#fig_3">5</ref> presents the Complementary Cumulative Distribution Function (CCDF) for the F3-measure. A point in the curve indicates the percentage of videos (on y-axis) for which the F3-measure is larger than the corresponding value on x-axis, thus, the closer the line is to the top-right corner, the better.</p><p>To explore whether the gap than can be covered, at least partially, by automated tag recommendations, we explore the performance of the tag recommendations using as inputs all data sources combined (MovieLens, Rotten Tomatoes, Wikipedia, and NY Times). The results are presented in Figure <ref type="figure" target="#fig_3">5</ref> as the solid (red) line.</p><p>The Kolmogorov-Smirnov test of significance indicates that the performance of using All data sources is significantly higher than that achieved by the YouTube tags (Frequency: D − = 0.44, p-value = 3.9 × 10 16 ; RandomWalk: D − = 0.43, p-value = 5.5 × 10 −15 ) implying that the tags recommended by both meth-ods are better than those currently assigned to the videos on YouTube. Therefore, the tags currently assigned to the YouTube videos can still be improved by automated methods to attract more search traffic, and, hence, boost video popularity.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Related Work</head><p>The quest to improve visibility of one's content (e.g., a website, a video) is not new -the whole Search Engine Optimization segment has seen uninterrupted attention. Multiple avenues are available, ranging from some that are viewed as abusive (e.g., link-farms) to perfectly legitimate ones (e.g., better content organization, good summaries in the titlebar of web pages). Our exploration falls into this latter category.</p><p>The related literature falls into two broad categories: automated content annotation and tag value assessment. The majority of related work on automated content annotation (or tag recommendation) focuses on suggesting tags to annotate content items such that they maximize the relevance of the tag given the content <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b4">5,</ref><ref type="bibr" target="#b6">7,</ref><ref type="bibr" target="#b8">9]</ref>, with a few exceptions where authors propose to leverage other aspects such as diversity <ref type="bibr" target="#b0">[1]</ref>.</p><p>Although finding relevant tags to a given content item is an important component of improving the tags assigned to this item, previous studies fail to account for the potential improvement on the view count of the annotated content -an aspect which is valuable to content managers and publishers, as they monetize based on the audience that is able to find their content.</p><p>The study presented by Zhou et al. <ref type="bibr" target="#b9">[10]</ref> is, to the best of our knowledge, the closest to our work. However, contrary to our study that focus on testing whether tags can be further optimized to attract traffic, Zhou et al. propose to boost video popularity by suggesting ways to connect a video to other influential videos (e.g., making title and description similar to those of influential videos) as a way to leverage the related video recommendations.</p><p>Our study is different from these previous efforts, as it focuses on testing the hypothesis that textual features of social content, such as online videos, can be further optimized to potentially attract search traffic. This motivates our future work on evaluating the impact of data source choice to produce recommendations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Summary and Future Work</head><p>A large portion of traffic received by video content on the web originates from keyword-based search and/or tag-based navigation. Consequently, the textual features of this content will directly impact the popularity of a particular content item, and ultimately the advertisement generated revenue. Therefore, understanding the performance of automatic tag recommenders is important to optimize the view count of content items.</p><p>First, we discuss the challenges on building a ground truth to evaluate data sources and techniques that aim to boost the popularity of multimedia content on the web. Next, this study provides evidence that tags currently assigned to a sample of YouTube videos can be further improved to attract more search traffic. To this end, we show an experiment that compares how close the tags currently assigned to the videos in the sample and tags harnessed from a combination of data sources are to the ground truth. The results show that using simple recommenders and a combination of data sources can improve the tags.</p><p>These preliminary results suggest a few directions of future research. Initially, one may perform comparisons between data sources individually and/or grouped by type (peer-and expert-produced, structured vs. unstructured) with the goal of understanding their relative value as inputs for tag recommenders. For example, are combinations of peer-produced data sources relatively more valuable than expert-based ones in the context of boosting multimedia content popularity?</p><p>Additionally, more experiments could provide deeper explanations on the performance of peerproduced data sources. For instance, does the value of tags extracted from peer-produced sources (for boosting content popularity), such as Wikipedia or Movie-Lens, increase with the number of contributors? All these questions are part of our future efforts.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: The recommendation pipeline.</figDesc><graphic coords="3,82.35,54.07,198.90,53.62" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :Figure 3 :</head><label>23</label><figDesc>Figure 2: Histogram with number of evaluations performed by turkers</figDesc><graphic coords="4,344.88,220.04,177.84,123.47" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Histogram with the number of characters in bytes to each video.</figDesc><graphic coords="5,88.20,54.07,187.20,100.26" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: CCDF of F3-measure for YouTube tags and recommended tags. tag set, respectively, for video v. The metric is defined as follows: F3-metric. F 3 (v) = 10•P (v)R(v) 9•P (v)+R(v) , where P (v) = |Tv∩Sv| Sv and R(v) = Tv∩Sv Tv are the precision and recall of tag recommendation for video v, respectively.</figDesc><graphic coords="6,334.35,54.07,198.90,133.55" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_0">This work is motivated by our collaboration with a company specialized in promoting video content. An NDA prevents the disclosure of details.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_1">We use OpenCalais.com for entity detection.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_2">Our study can be easily extended to consider the budget as the number of tags (as in Vimeo).</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_3">http://www.mturk.com</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="9" xml:id="foot_4">http://www.movielens.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="10" xml:id="foot_5">http://www.grouplens.org/taxonomy/term/14</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="11" xml:id="foot_6">http://en.wikipedia.org/wiki/Pulp Fiction (Film)</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="12" xml:id="foot_7">http://developers.nytimes.com</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="13" xml:id="foot_8">http://developer.rottentomatoes.com/</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Exploiting Novelty and Diversity in Tag Recommendation</title>
		<author>
			<persName><forename type="first">F</forename><surname>Belém</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Martins</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Almeida</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Gonçalves</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Advances in Information Retrieval SE -32</title>
		<title level="s">Lecture Notes in Computer Science</title>
		<editor>
			<persName><forename type="first">P</forename><surname>Serdyukov</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">P</forename><surname>Braslavski</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><surname>Kuznetsov</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><surname>Kamps</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><surname>Rüger</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">E</forename><surname>Agichtein</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">I</forename><surname>Segalovich</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">E</forename><surname>Yilmaz</surname></persName>
		</editor>
		<meeting><address><addrLine>Berlin Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2013">2013</date>
			<biblScope unit="volume">7814</biblScope>
			<biblScope unit="page" from="380" to="391" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Introduction to Algorithms</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">H</forename><surname>Cormen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">E</forename><surname>Leiserson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">L</forename><surname>Rivest</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Stein</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2009-07">July 2009</date>
			<publisher>The MIT Press</publisher>
		</imprint>
	</monogr>
	<note>third edit edition</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Personalized tag recommendation using graphbased ranking on multi-type interrelated objects</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Guan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Bu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Q</forename><surname>Mei</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Wang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">SIGIR &apos;09</title>
				<meeting><address><addrLine>Boston, MA, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="540" to="547" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Query performance prediction</title>
		<author>
			<persName><forename type="first">B</forename><surname>He</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Ounis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Information Systems</title>
		<imprint>
			<biblScope unit="volume">31</biblScope>
			<biblScope unit="issue">7</biblScope>
			<biblScope unit="page" from="585" to="594" />
			<date type="published" when="2006-11">Nov. 2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">The effect of title term suggestion on e-commerce sites</title>
		<author>
			<persName><forename type="first">S</forename><surname>Huang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Bolivar</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">WIDM &apos;08</title>
				<meeting><address><addrLine>Napa Valley, California, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2008">2008</date>
			<biblScope unit="page" from="31" to="38" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Language Models and Topic Models for Personalizing Tag Recommendation</title>
		<author>
			<persName><forename type="first">R</forename><surname>Krestel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Fankhauser</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IEEE/WIC/ACM International Conference on Web Intelligence and Intelligent Agent Technology</title>
				<meeting><address><addrLine>Toronto, AB, Canada</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2010-08">2010. Aug. 2010</date>
			<biblScope unit="page" from="82" to="89" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<author>
			<persName><forename type="first">D</forename><surname>Liu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><forename type="middle">S</forename><surname>Hua</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Yang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">J</forename><surname>Zhang</surname></persName>
		</author>
		<title level="m">Tag ranking. WWW &apos;09</title>
				<meeting><address><addrLine>Madrid, Spain</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="351" to="360" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Pairwise interaction tensor factorization for personalized tag recommendation</title>
		<author>
			<persName><forename type="first">S</forename><surname>Rendle</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Schmidt-Thieme</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the third ACM international conference on Web search and data mining -WSDM &apos;10</title>
				<meeting>the third ACM international conference on Web search and data mining -WSDM &apos;10<address><addrLine>New York, New York, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM Press</publisher>
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Image annotation refinement using random walk with restarts</title>
		<author>
			<persName><forename type="first">C</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Jing</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">J</forename><surname>Zhang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">MULTIMEDIA &apos;</title>
				<meeting><address><addrLine>Santa Barbara, CA, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2006">2006</date>
			<biblScope unit="volume">06</biblScope>
			<biblScope unit="page" from="647" to="650" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Exploring social annotations for information retrieval</title>
		<author>
			<persName><forename type="first">D</forename><surname>Zhou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Bian</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Zheng</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Zha</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">L</forename><surname>Giles</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">17th International World Wide Web Conference</title>
				<meeting><address><addrLine>Beijing, China</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2008">2008</date>
			<biblScope unit="page" from="715" to="724" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Boosting video popularity through recommendation systems</title>
		<author>
			<persName><forename type="first">R</forename><surname>Zhou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Khemmarat</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Gao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Wang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Databases and Social Networks on -DBSocial &apos;11</title>
				<meeting><address><addrLine>New York, New York, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM Press</publisher>
			<date type="published" when="2011-06">June 2011</date>
			<biblScope unit="page" from="13" to="18" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
