Image
EAN-139780691148731   EAN-13 barcode 9780691148731
Product NameClimbing The Charts: What Radio Airplay Tells Us About The Diffusion Of Innovation
LanguageEnglish
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 0691148732
Price New14.95 US Dollars    (curriencies)
Price Used24.96 US Dollars    (curriencies)
Width0.9 inches    (convert)
Height9.2 inches    (convert)
Length6.4 inches    (convert)
Weight16 ounces    (convert)
AuthorGabriel Rossman
Page Count200
BindingHardcover
Published07/22/2012
FeaturesUsed Book in Good Condition
Long DescriptionDespite the growth of digital media, traditional FM radio airplay still remains the essential way for musicians to achieve commercial success. Climbing the Charts examines how songs rise, or fail to rise, up the radio airplay charts. Looking at the relationships between record labels, tastemakers, and the public, Gabriel Rossman develops a clear picture of the roles of key players and the gatekeeping mechanisms in the commercial music industry. Along the way, he explores its massive inequalities, debunks many popular misconceptions about radio stations' abilities to dictate hits, and shows how a song diffuses throughout the nation to become a massive success. Contrary to the common belief that Clear Channel sees every sparrow that falls, Rossman demonstrates that corporate radio chains neither micromanage the routine decision of when to start playing a new single nor make top-down decisions to blacklist such politically inconvenient artists as the Dixie Chicks. Neither do stations imitate either ordinary peers or the so-called kingmaker radio stations who are wrongly believed to be able to make or break a single. Instead, Rossman shows that hits spread rapidly across radio because they clearly conform to an identifiable style or genre. Radio stations respond to these songs, and major labels put their money behind them through extensive marketing and promotion efforts, including the illegal yet time-honored practice of payoffs known within the industry as payola. Climbing the Charts provides a fresh take on the music industry and a model for understanding the diffusion of innovation.
Similar Items9781161393859: Shaping Jazz: Cities, Labels, And The Global Emergence Of An Art Form
9781154921656: Everything Is Obvious: How Common Sense Fails Us
9780745652399: Twitter: Social Communication in the Twitter Age (Digital Media and Society)
9780745647456: The Culture Of Markets
9780691150888: Shaping Jazz: Cities, Labels, And The Global Emergence Of An Art Form
9780691134567: Market Rebels: How Activists Make Or Break Radical Innovations
9780691131061: Shaping Jazz: Cities, Labels, And The Global Emergence Of An Art Form
9780060896379: Everything Is Obvious: How Common Sense Fails Us
Created01-30-2013 1:04:13am
Modified04-30-2020 11:29:55pm
MD5043804d3bf93f8e8e89ea0c5db722679
SHA256b9f544e9adc45bd862436f7ddf685b445c0c0f1c116de6d0cef0bcff7835e6ce
Search Googleby EAN or by Title
Query Time0.0192940

Article of interest

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.

Close

Search

Close

Share