| Image |  |
| EAN-13 | 9780783134741  |
| Product Name | Goodnight Moon and Other Sleepytime Tales |
| Language | English |
| Category | Electronics / Photography: A/V Media: Movie / TV |
| Amazon.com |  Buy on Amazon ~ B0007N19BY |
| Model | 2221165 |
| Price New | 6.49 US Dollars (curriencies) |
| Price Used | 1.49 US Dollars (curriencies) |
| Aspect Ratio | 1.33:1 |
| Cast | Susan Sarandon |
| Genre | KIDS & FAMILY |
| Width | 5.5 inches (convert) |
| Height | 0.5 inches (convert) |
| Length | 7.5 inches (convert) |
| Weight | 3.2 ounces (convert) |
| Binding | Dvd |
| Format | Multiple Formats, Closed-captioned, Color, Dolby, Dubbed, NTSC, Subtitled, Widescreen |
| Published | 10/05/2017 |
| Run Time | 124 minutes |
| Features | Factory sealed DVD |
| Long Description | Goodnight Moon and Other Sleepytime Tales (DVD) Everybody's favorite bedtime story, "Goodnight Moon" comes to life on DVD for the very first time. Along with other beloved animated tales and lullabies, children and stars come together in a delightful exploration of the nighttime world. Children offer wise and witty reflections on a host of sleepytime topics, from the comfort of "blankies" to Native American dreamcatchers, from monsters and nightmares to the mysteries of dreamland. Susan Sarandon narrates "Goodnight Moon," Tony Bennett sings the swing classic "Hit the Road to Dreamland," Lauryn Hill lends a new rhythm to the rhyme "Hush, Little Baby," the many voices of Billy Crystal bring "There's a Nightmare in My Closet" to animated life, Natalie Coletells the tale of Faith Ringgold's "Tar Beach," Aaron Neville sings "Brahms Lullaby" and Patti LaBelle performs "Twinkle, Twinkle, Little Star." |
| Similar Items | 0883929238255: Classical Baby 0883929220496: Child's Garden Of Poetry 0883929010943: Classical Baby-Poetry Show (Dvd) 0786936695076: Very Hungry Caterpillar and Other Stories 0767685253922: Caldecott Favorites Featuring The Snowy Day 0767685115374: Where the Wild Things Are...and 5 More Stories by Maurice Sendak 0767685107201: Good Night Gorilla... And More Great Sleepytime Stories (Scholastic Storybook Treasures) 0767685107171: Chicka Chicka Boom Boom... And More Fun With Letters And Numbers (Scholastic Storybook Treasures) 0026359291920: Classical Baby-Dance (Dvd/P S/4x3 Transfer) 0026359235528: Classical Baby: The Music Show View 6 more similar items |
| Created | 10-08-2013 1:37:16am |
| Modified | 05-01-2020 1:26:17am |
| MD5 | b1ff44484d7cc87a73815ce4a36b97d3 |
| SHA256 | ec71884525c6bac80c4f0cba5d8333c3c94ea8fbe3acb6425ec877f9dc21964f |
| Search Google | by EAN or by Title |
| Query Time | 0.0187120 |
Article of interest
This feature started with version 3.3 of the API and it allows you to update many fields of a product in one call. Prior to this, each attribute for a product was updated in a separate call, causing the process to be a bit slow.
It is important to note that bulk updates only work with JSON formatted data. Because of this, you can leave the mode=json out of your call.
You should use a POST call instead of a GET to avoid over running the length limits that can be found when sending long URLs.
Required Parameters
- keycode - your normal API keycode
- update - the first product you intend to update (more info below)
- field - must be set to *bulk*
Optional Parameters
- test - If you are using GET (please don't) this should be the first parm. Set it to test=1 to avoid saving any actual data.
- imageURL - This is case sensitive. This can be any reachable image in jpg, gif, png format. You can use ftp, http, https and even data URLs here. So rather than pushing in a separate call, we will pull it.
- fields - This is the JSON formatted array of fields to be updated. Yes, this is actually optional. But without it, we won't update any field data.
Each entry in the fields array is made up of keys and data. Some keys are required and some are optional depending on the data type being used. These entries mirror the single field update calls used when updating data one field at a time.
Details of the fields entries
- field - required, the name of the field to be updated
- value - required, the new value for this field
- extra_id - optional, Some fields use 2 fields to store the data. One being a numeric value and the second being a descriptor [such as a ounces, gallons, quarts] This extra value must match the list we keep in our database. You can include the text version of this extra information at the end of the "value" field but it still needs to match what we have. You can also split the value into two fields the way we do passing the number in the "value" field and the descriptor as an index id in this "extra_id" field. For more information, see the "get=extra" in the basic overview for the v3 API.
- reason - used only when you want to delete a field. If you use this, you must set the value field to empty string and give a reason in this field. At least 13 characters are required for this reason.
An example of the JSON to update multiple fields for a single product
The order of each field in the array doesn't matter. We will process them in sequence but sequence makes no difference. So you don't have to sort them or place them in any partcular order.
You can actually update multiple products at the same time. To do this, you still need to pass some basic information for the first product in the required fields (see above). But in the fields JSON, you create an array of products, each with a fields sub-array. The product listed in the update field would be ignored for the most part but must still be valid. So it can be hardcoded when using this method as long as it is a vaild EAN code.
An example of the JSON to update multiple fields for multiple products
It doesn't matter if you are updating a single product or multiple products. When the response is returned, the top level status is always going to be code 200 assuming your required fields passed the test. Then you will see an array of products even if you only passed in one to be updated. Each product entry and each field entry will have a status so you will know if individual updates worked or failed. This includes the imageURL you passed.
An example of the JSON returned after an update call
The return results in each img or status field
- ok - The field or image processed without error
- n/a - No image was sent (not for fields)
- duplicate - The data you sent already exists. (not for images)
- Any other value is an error which may include details but may not.