Image
EAN-139780874218893   EAN-13 barcode 9780874218893
Product NameFolk Culture In The Digital Age: The Emergent Dynamics Of Human Interaction
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHeight:9.06 inches / Length:6.1 inches / Weight:1.01 pounds / Width:0.79 inches
Amazon.comA Buy on Amazon ~ 0874218896
Price New24.83 US Dollars    (curriencies)
Price Used12.36 US Dollars    (curriencies)
Width1.3 inches    (convert)
Height9 inches    (convert)
Length6 inches    (convert)
Weight16.16 ounces    (convert)
Page Count220
BindingPaperback
Published11/16/2012
FeaturesUsed Book in Good Condition
Long DescriptionSmart phones, tablets, Facebook, Twitter, and wireless Internet connections are the latest technologies to have become entrenched in our culture.  Although traditionalists have argued that computer-mediated communication and cyberspace are incongruent with the study of folklore, Trevor J. Blank sees the digital world as fully capable of generating, transmitting, performing, and archiving vernacular culture. Folk Culture in the Digital Age documents the emergent cultural scenes and expressive folkloric communications made possible by digital "new media" technologies. New media is changing the ways in which people learn, share, participate, and engage with others as they adopt technologies to complement and supplement traditional means of vernacular expression. But behavioral and structural overlap in many folkloric forms exists between on- and offline, and emerging patterns in digital rhetoric mimic the dynamics of previously documented folkloric forms, invoking familiar social or behavior customs, linguistic inflections, and symbolic gestures. Folk Culture in the Digital Age provides insights and perspectives on the myriad ways in which folk culture manifests in the digital age and contributes to our greater understanding of vernacular expression in our ever-changing technological world.
Similar Items9780814742853: Fans, Bloggers, And Gamers: Media Consumers In A Digital Age
9780812211399: All Silver And No Brass: An Irish Christmas Mumming
9780700603060: The Study Of American Folklore: An Introduction (4th Edition)
9780582489042: The Study Of American Folklore: An Introduction (4th Edition)
9780582489035: The Study Of American Folklore: An Introduction (4th Edition)
9780548020463: The Study Of American Folklore: An Introduction (4th Edition)
9780521395274: The Study Of American Folklore: An Introduction (4th Edition)
9780393972238: The Study Of American Folklore: An Introduction (4th Edition)
9780253209948: Folkloristics: An Introduction
9780874211559: We Gather Together
View 10 more similar items
Created01-23-2013 1:45:00am
Modified05-01-2020 4:41:35am
MD581c527dcb013a977f0beac78eb47c919
SHA2566699397ec6fe0ec08103b1a588f24f1a96db8abe5fc0bc1a098acb2d6b71ad99
Search Googleby EAN or by Title
Query Time0.0232711

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