Hi,

I'd like to create a tabular view containing some Amazon data (1st column: image for an item; 2nd column: node title with link to a node reviewing the item). Currently the "Amazon" module exposes only one kind of image to views: "Large image". There are other image derivates available, but they're not exposed to views, at least not as isolated images (e.g. "small image and basic info"). As far as I know, I can't get rid of the "...and basic info part" in my tabular view.

So simply this is a feature request to expose the data provided by Amazon in a more fine-granular way, especially the smaller image derivates. Also it'd be nice to gain access to the other data provided by Amazon ECS (e.g. publishing date, binding, ISBN, etc.).

Thank you & greetings, -asb

CommentFileSizeAuthor
#12 field-asin-unavailable.jpg10.06 KBasb
#12 field-asin-unavailable.jpg10.06 KBasb

Comments

rfay’s picture

Version: » 6.x-1.0-beta7

You do get access to a surprising number of things when you create a relationship on the ASIN field. Please try that and see if it resolves your issue. There are examples views and CCK exports at http://drupal.org/node/524296.

Let me know if this resolves the issue.

rfay’s picture

Status: Active » Postponed (maintainer needs more info)
asb’s picture

> You do get access to a surprising number of things when you create a relationship on the ASIN field.
> Please try that and see if it resolves your issue. There are examples views and CCK exports at http://drupal.org/node/524296.

Thanks for the link; at least in my setup the data provided doesn't change if I create a required relationship on the ASIN field. In the view's configuration I still have four "Format" options for the CCK ASIN field: "Small image and basic info", "Small image and full info", "Large image", and "Title as link". What I want is somethink like "Small image without any info".

The link you provided applies to the "Amazon Store" module which I don't use; maybe this is required to harvest more data from Amazon?

Thanks & greetings, -asb

rfay’s picture

Status: Postponed (maintainer needs more info) » Fixed

I've just committed a views extension that allows you to specify an image, what size you want it to be, and how you want it linked. Please try out tonight's dev module and see if this is helpful to you.

You do have to create a relationship on the asin field to be able to use it.

BTW: Although the link I gave is in support of Amazon Store, the information is plain-jane Amazon. It's just a CCK type with ASIN, and a view to support it. If you turn on Amazon Store, the links to to the Amazon Store page.

Please note that we're looking for more and better documentation of how to use CCK and views with Amazon, so please consider contributing as you get it sorted out. An example with screenshots and the new image selection stuff would be great.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

asb’s picture

Version: 6.x-1.0-beta7 » 6.x-1.0-beta9
Status: Closed (fixed) » Active

Damn. Sorry that I have to re-open this, also.

In the view's configuration I still have four "Format" options for the CCK ASIN field (no relationship configured):

* "Small image and basic info",
* "Small image and full info",
* "Large image", and
* "Title as link".

What I want is somethink like "Small image without any info".

> You do have to create a relationship on the asin field to be able to use it.

That might be the missing piece. But a relation from where to what?

There's some documentation about this: Using Views with the Amazon CCK Type. Whatever I do, I'm not getting anything but those four "Format" options. The only thing that happens If I configure a required relationship to one of the 'asin'-fields is that the view becomes empty.

Also, I'm not getting the mentioned 'Amazon Example' view.

Thanks & greetings, -asb

rfay’s picture

Status: Active » Fixed

I think you'll like the new Amazon documentation and the example view provided. Please take a look - it's linked to from the project page.
http://drupal.org/node/595464

rfay’s picture

Ooops - I see that you already found the documentation, so either you're not reading well or I'm not writing well.

If you turn on the provided example view, you'll see how it's done. If features is installed, you can do that at admin/build/features. Then you'll have the view and the content type. Add some content and experiment.

The relationship must be established on the field that is an ASIN-type field. Just add a relationship to Content: ASIN, or whatever you've called your ASIN field. Require the relationship. Then you have lots and lots of options.

Note that the Amazon Store documentation at http://drupal.org/node/524296 also provides an example of this, with a downloadable content type and views export.

Hoping it will make sense and work for you.

-Randy

asb’s picture

> If you turn on the provided example view, you'll see how it's done.

As mentioned above, I'm not getting an 'Amazon Example' view. Neither in my Testing site, nor in my D5-D6 migration sandbox, nor in a productive site. Please notice: All of them were upgraded from previous versions of the 'Amazon' module.

> Just add a relationship to Content: ASIN, or whatever you've called your ASIN field. Require the relationship. Then you have lots and lots of options.

Yes, I'Ve read this in the documentaion. However, I'm not getting more options, but either the same view as before - or simpy nothing.

Let's get descriptive: ./admin/content/types/fields lists two fields of field type 'Amazon item':

* 'field_asin_multiple' - available on content type 'Rezension' (= review, supposed to allow for multiple ASINs)
* 'field_asin_single' - available on content type 'Produkt' (= product, supposed to allow just one ASIN)

This is very simple and straight forward, isnt it?

OK, now have a look at the view 'publications', again as simple and straight forward as it can get (I'm trying to translate from German into English):

* Relations: none
* Arguments: none
* Fields:
** Content: ISBN/ASIN Large image
** Node: Title
* Sort criteria: Node: Post date desc
* Filter:
** Node: Published or admin
** (some more on Node Type and Taxonomy)

Result: a tabular listing with a large cover image of a reviewed book and a link to the review node (live example @ taxidi.org, view embedded into Panels 3; currently rather ugly, right?). In this listing I'd like a smaller cover image, like the thumbnail cover images in AAT or the default search result images at Amazon. Currently I'm not getting those as field formatters in views.

Now add a relation to one of those two 'Amazon item' type fields mentioned above:

* Inhalt: ISBN/ASIN (field_asin_multiple) - Amazon item - Appears in: Rezension

** Defaults: Configure Relationship Inhalt: ISBN/ASIN (field_asin_multiple)
** Label: field_asin_multiple_asin
** Require this relationship (Checked)

Click on "Update", the live preview becomes empty.

Click on "Fields", Content: ISBN/ASIN Large image. There's no option to use a relationship.

Add a new "Content" field of 'Amazon item' field type, there's also no option to use a relationship.

* Inhalt: ISBN/ASIN (field_asin_single) - Amazon item - Appears in: Produkt

(same as before)

Configurions a Relation does work when I'm using another CCK field type like 'Node reference'.

What am I doing wrong?

Thanks & Greetings, -asb

rfay’s picture

@asb - Sorry this is frustration. It would be easier for me to share my screen with you and demo it.

Here's a screencast: http://www.youtube.com/watch?v=xwUQIRcoYRk

Please see if this squares with anything you see.

In addition, I added more information to the documentation at http://drupal.org/node/595464#amazon_examples about how to get the Amazon Examples feature running for you.

BTW: To get the Amazon Example view, you need to go to admin/build/features and enable the Amazon Example feature. Let me know if you find that there.

asb’s picture

> To get the Amazon Example view, you need to go to admin/build/features and enable the Amazon Example feature.

OK, installed the 'features' module. At ./admin/build/features Im seeing one entry: "Amazon Examples. Provides Amazon module CCK type and view as a demo". When enabling this, I'm getting:

Field field_asin was not created for amazon_example because a conflict was detected for the following properties: required, multiple

Nodes created through ./node/add/amazon-example do not have a 'amazon field', and ./amazon_example_view is empty even if I have an 'amazon field' on another content type. If I try to add an item there, I cant enter an ASIN (please see screenshot in #12).

> Here's a screencast: [...] Please see if this squares with anything you see.

Thank you for the screencast, It's always a pleasure to look a dev over the shoulder ;)

However, the essential difference is that I'm getting data from Amazon.de (!). But we were looking in the wrong place: Content: ISBN/ASIN Large image still offers nothing else but those data I mentioned before; but when filtering for group 'Amazon', I'm getting:

* Amazon: ASIN - The product ID of the item.
* Amazon: All participants - The names of all individuals who participated in the creation of a product, grouped as a single field.
* Amazon: Aspect ratio - The aspect ratio of an Amazon video product.
* Amazon: Audience rating - The Audience rating of an Amazon video product (G, PG, etc).
* Amazon: Bezeichnung - The label that published an Amazon music product.
* Amazon: Bezeichnung - The name of the label that published the product.
* Amazon: Binding - The style of binding used for the product.
* Amazon: Detail page URL - The URL of the product's page on Amazon.com.
* Amazon: Dewey decimal number - Error: missing help
* Amazon: ESRB age rating - The age rating of an Amazon software product.
* Amazon: Edition - The edition of an Amazon book product.
* Amazon: Genre - The genre of an Amazon software product.
* Amazon: Hardware platform - The hardware platform required by an Amazon software product.
* Amazon: Invalid ASIN - If nonzero, the ASIN is invalid or discontinued by Amazon
* Amazon: List price - The current list price of the item. (Unformatted)
* Amazon: Manufacturer - The manufacturer of the product.
* Amazon: Number of discs - The number of discs included in an Amazon music product.
* Amazon: Operating system - The operating systems required by an Amazon software product.
* Amazon: Part number - The Manufacturer's own part number for the product.
* Amazon: Participant name - The name of an individual who participated in the creation of a product.
* Amazon: Participant role - The role the participant had in creating the product (author, artist, etc).
* Amazon: Platform - The platform required by an Amazon software product.
* Amazon: Product group - The Amazon grouping the product is categorized in.
* Amazon: Product image - A photo of the Amazon product in question.
* Amazon: Product type name - The Amazon internal product-type code for the product.
* Amazon: Publication date - The publication date of the item
* Amazon: Publisher - The publisher of the product.
* Amazon: Region code - The region code of an Amazon DVD product.
* Amazon: Release date - The release date of the product.
* Amazon: Running time - The length of an Amazon video product, in minutes.
* Amazon: Sales rank - The current sales ranking of the product on Amazon.com.
* Amazon: Seiten - The number of pages in an Amazon book product.
* Amazon: Studio - The name of the studio that published the product.
* Amazon: Studio - The studio that published an Amazon music product.
* Amazon: Theatrical release date - The theatrical release date of an Amazon video product.
* Amazon: Titel - The name of the product.

So this problem is solved, indeed. Thank you!

Greetings, -asb

asb’s picture

StatusFileSize
new10.06 KB
new10.06 KB
rfay’s picture

Interesting - you already had a field by the name of ASIN, so it failed. And fields are hard to get rid of. I think you'll do fine using the technique in my videocast. The examples features is not as important to you.

I'll be happy to share my screen and show you how to do it if the videocast doesn't do it for you.

-Randy

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.