Its recommended to use one of the predefined product types, to allow Google Base to better categorize your products with others.
In my mind vehicle parts is accurate for 99% of car parts the others cover the rest nicely : car audio,car radar and car video. car parts is covered by the broader vehicle parts, i see no need for a 'car parts' type. There also an 'accessories' type that cover some other areas, where ever you can though use a product type from that list. Tom Wilson Freelance Google Base Developer and Consultant www.tomthedeveloper.com Google Base Tools - http://dev.tomthedeveloper.com/googlebase On Sep 12, 4:49 pm, icebackhaz <[EMAIL PROTECTED]> wrote: > I hadn't noticed that in the list of 474 product_types (at last > count). This would be an improvement in that it deals with parts of > vehicles. Since there are there "car {audio,radar,video}" as well as > "bicycle parts" and "parts", why no "car parts"? But Anil may be > selling tire pressure gauges, which aren't part of the vehicle, aren't > parts at all, so "automotive" may do just fine. > > On Sep 11, 1:35 pm, Tom Wilson <[EMAIL PROTECTED]> wrote: > > >http://base.google.com/support/bin/answer.py?hl=en&answer=66818 > > > Theres 'vehicle parts' ? > > > Tom Wilson > > Freelance Google Base Developer and Consultantwww.tomthedeveloper.com > > Google Base Tools -http://dev.tomthedeveloper.com/googlebase > > > On Sep 11, 6:42 pm, icebackhaz <[EMAIL PROTECTED]> wrote: > > > > To date GB doesn't have a special top-level category for automotive > > > parts, so you'll have to live in the products group and set the > > > product_type to automotive. > > > > gentry.getGoogleBaseAttributes().addTextAttribute("Product_type","automotiv > > > e"); > > > ... > > > gentry.getGoogleBaseAttributes().addIntAttribute("psi", 30); > > > > You will have to either categorize you products such that you can list > > > related ones with a single Entry builder or keep and value-to- > > > attribute map for each of your products. With the latter approach you > > > may only need a single Entry builder. You do have some up-front work > > > in setting the mappings. > > > > for (String attrName : myProduct.getGoogleAttributes() ) { //Your > > > code > > > String value = myProduct.getValue(attrName); //Your code > > > gentry.getGoogleBaseAttributes().addTextAttribute(attrName; value); > > > > } > > > > On Sep 10, 9:58 pm, "Anil Pathak" <[EMAIL PROTECTED]> wrote: > > > > > My products are autoparts, They have diverse attribute sets. For example > > > > attribute "pressure" only applied to certain set of products. > > > > More than that, i thought perhaps feeding individual products will help > > > > with > > > > changing prices. > > > > > On Wed, Sep 10, 2008 at 9:38 PM, icebackhaz <[EMAIL PROTECTED]> wrote: > > > > > > Have you seen this list of recommended attributes by type of item > > > > > listed? > > > > >http://base.google.com/base/api/itemTypeDocs. They're all(?) in the > > > > > "g:" namespace, which is where > > > > > gentry.getGoogleBaseAttributes().addXXXXAttribute(<recommended-attr- > > > > > name>, <XXXX-typed-value>) gets you. > > > > > > On Sep 8, 4:40 pm, aniljava <[EMAIL PROTECTED]> wrote: > > > > > > Lots of my products do not share attributes between each other, > > > > > > thought of migrating from bulk upload to API based upload. > > > > > > > If anyone have gone through this or knows about it please advise me, > > > > > > whether i should i remove existing products before starting. > > > > > > > Thanks > > > > > > Anil --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
