| Image |  |
| EAN-13 | 9780791475409  |
| Product Name | Who Gets What?: Domestic Influences on International Negotiations Allocating Shared Resources (Suny Series in Global Politics) (Suny Series in Global Politics (Paperback)) |
| Language | English |
| Category | Book / Magazine / Publication |
| Short Description | Paperback |
| Amazon.com |  Buy on Amazon ~ 0791475409 |
| SKU | Y9780791475409 |
| Price New | 21.95 US Dollars (curriencies) |
| Price Used | 13.83 US Dollars (curriencies) |
| Width | 0.44 inches (convert) |
| Height | 9 inches (convert) |
| Length | 6 inches (convert) |
| Weight | 9.6 ounces (convert) |
| Author | Aslaug Asgeirsdottir |
| Page Count | 194 |
| Binding | Paperback |
| Published | 07/01/2009 |
| Long Description | During international bargaining, who gets the better deal, and why, is one of the questions at the heart of the study of international cooperation. In Who Gets What? Aslaug Asgeirsdottir analyzes seven agreements signed throughout a twenty-year span between Iceland and Norway to allocate shared fish stocks. While the Law of the Sea regime provides specific solution concepts for negotiators, it does not dictate the final outcome. Looking at the actual negotiation process and the political and economic constraints negotiators operate under, Asgeirsdottir examines how domestic interest groups can directly influence the negotiating process, and thus affect international agreements over scarce resources. Who Gets What? demonstrates empirically that a nation with more domestic constraints on its negotiators gets a better deal. |
| Similar Items | 9780262018647: Saving Global Fisheries: Reducing Fishing Capacity to Promote Sustainability (MIT Press) 9781584653936: Capturing The Commons: Devising Institutions To Manage The Maine Lobster Industry 9780262582650: The Privatization of the Oceans (MIT Press) 9780262511797: Adaptive Governance: The Dynamics of Atlantic Fisheries Management (Global Environmental Accord: Strategies for Sustainability and Institutional Innovation) 9780262731928: Adaptive Governance: The Dynamics of Atlantic Fisheries Management (Global Environmental Accord: Strategies for Sustainability and Institutional Innovation) |
| Created | 11-20-2012 11:51:39pm |
| Modified | 05-20-2017 1:10:05am |
| MD5 | 9a8e6e8d5f457cba43799a29522f1c39 |
| SHA256 | 8a985a7c55edb3f9cd2060620a822212898691a09550519204cd113cb42fa4c1 |
| Search Google | by EAN or by Title |
| Query Time | 0.0138650 |
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.