Results 1 to 14 of 14
  1. #1
    Member
    Join Date
    January 18th, 2005
    Posts
    58
    What format for data feed do you all like to see from merchants in cj? What fields? Should all html be stripped?

  2. #2
    Affiliate Manager
    Join Date
    January 18th, 2005
    Posts
    1,056
    I am sure each person would have their own preferences on data feeds. To me, the easiest to work with is pipe seperated and no quotes.
    Example:
    productID|category|name|imageurl|produrl|retail|ourprice

    -One line per record
    -No carriage returns
    -The html doesn't need to be stripped as long as everything is on one line with no carriage returns.

    This is the type of feed that I could work with and not have any problems.

  3. #3
    Full Member
    Join Date
    January 18th, 2005
    Posts
    379
    About the only thing I would require is paragraph tags in descriptions. No carriage returns/line feeds.

    I sometimes change the case of the name but that's just a personal thing.

    <hr>
    Leave the gun, take the cannolis.

  4. #4
    Web Ho - Design B!tch ~Michelle's Avatar
    Join Date
    January 18th, 2005
    Location
    Michigan
    Posts
    2,040
    Adding to Chet's:

    productID|category|name|imageurl|produrl|retail|ourprice|description

    I mentioned this in another thread but one thing I really would like to see be the norm in a datafeed is that it be broken into sections with a blank line between them.

    Like all shoes in one section, all pants in another section, etc.

    It would save me a ton of time since most sites I index by item category and have to pick through the feeds and make a seperate one for each category.

    ~Michelle
    "All I ask is a chance to prove that money can't make me happy."
    "Work to become, not to acquire." -- Confucius

  5. #5
    I like traffic lights
    Join Date
    January 18th, 2005
    Location
    Southern hemisphere - away from Fukushima
    Posts
    2,936
    >I mentioned this in another thread but one thing I really would like to see be the norm in a datafeed is that it be broken into sections with a blank line between them.


    That's what the category field is for.

    I'd prefer no html in the feed. pipe or tab as delimiter. SKU as a seperate field.

    ****************************
    Jimmy James Inc. fan club membership # 3312

    "But Jimmy had fancy plans, and pants to match"

  6. #6
    Moderator MichaelColey's Avatar
    Join Date
    January 18th, 2005
    Location
    Mansfield, TX
    Posts
    16,232
    A detailed category is very helpful to me. For instance "Video Games > Playstation 2 > Action Games".

    Michael Coley
    Amazing-Bargains.com

  7. #7
    Action Jackson - King of the World
    Join Date
    January 18th, 2005
    Posts
    2,201
    Add to that no quotes with in the fields like in the product names, categories, and descriptions

    Jack Mitchell
    http://kattskozykorner.com
    http://clothing-to-go.com
    http://sports-to-go.com

  8. #8
    ABW Ambassador Mike O's Avatar
    Join Date
    January 18th, 2005
    Location
    Los Angeles area
    Posts
    843
    No non-ASCII characters in the text!

    -- Mike

  9. #9
    Web Ho - Design B!tch ~Michelle's Avatar
    Join Date
    January 18th, 2005
    Location
    Michigan
    Posts
    2,040
    <BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by Drewbert:
    >I mentioned this in another thread but one thing I really would like to see be the norm in a datafeed is that it be broken into sections with a blank line between them.


    That's what the category field is for.

    I'd prefer no html in the feed. pipe or tab as delimiter. SKU as a seperate field.

    ****************************
    Jimmy James Inc. fan club membership # 3312

    "But Jimmy had fancy plans, and pants to match"<HR></BLOCKQUOTE>

    Yes, but most of the feeds I have worked with so far do not get indepth.

    The say Shoes | Dress Shoes

    where I would like

    Shoes | Dress Shoes | Sandels

    Shoes | Dress Shoes | Loafers

    Most need to be broken down more.

    ~Michelle
    "All I ask is a chance to prove that money can't make me happy."
    "Work to become, not to acquire." -- Confucius

  10. #10
    Resident Genius and Staunch Capitalist Leader's Avatar
    Join Date
    January 18th, 2005
    Location
    Florida
    Posts
    12,817
    <BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR> Should all html be stripped? <HR></BLOCKQUOTE>

    Yes, yes, yes!

    A merchant's "bright" idea of formatting can really screw up the layout of a page!

    Fields I like:

    ProductName SKU Description Keywords BuyURL ImageURL Category

    Some others will want the price as well.

    Tab or pipe delimited.

    <BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>No non-ASCII characters in the text!
    <HR></BLOCKQUOTE>

    DITTO!

    I'll add:

    No all-caps fields.

    Description and keywords need to be different!

    ProductName needs to make sense, from a buyer's standpoint. No "Model 1923" stuff. Model 1923 What? Say what the thing is, then put the model number.

    If the only thing different between the names of things is the model number or the size--put that in the NAME field.

    Refrain from any "special" category names. For instance, if you have backpacks for sale, don't get cute and call them "daypacks" even if that's technically correct. Look in Wordtracker, and USE THE SAME NAME THE CUSTOMERS ARE USING for the type of item! Same thing goes for product names.

    Pluralize what should be pluralized. I don't know where clothes sellers get off with names like "Bike short." They are shortS. Call them that. Same with pantS, scissorS, and sockS. LISTEN to how people refer to things, before making a feed!

    No paragraph tags in my descriptions, please. If the tag was in the wrong place for my layout, it'd end
    up looking
    something like this, where the predone paragraph
    tag
    cuts off the sentence at a different place than the layout naturally does.

    And again, refrain from all non-ASCII characters. Hokey characters are the cause of much grief and messed up-looking datafeed sites. Also don't encode things like TM, quotes and the copyright seal, because it can end up unrendered.

    It's the most wonderful time of the year!~Old Christmas Song

  11. #11
    Full Member
    Join Date
    January 18th, 2005
    Posts
    379
    <BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR> No paragraph tags in my descriptions, please. If the tag was in the wrong place for my layout, it'd end
    up looking
    something like this, where the predone paragraph
    tag
    cuts off the sentence at a different place than the layout naturally does.<HR></BLOCKQUOTE>

    That may be so for small descriptions but what about the longer descriptions ?

    I don't expect a feed to be perfect the way I want it straight from the merchant. Sometimes I want all lowercase and sometimes I want Title Case on fields. I either run some find/replaces on the raw data or take care of issues during the processing of the feed.

    On thing I do hate is "/" in the feed. That can really make problems.

    <hr>
    Leave the gun, take the cannolis.

  12. #12
    Member
    Join Date
    January 18th, 2005
    Posts
    58
    Eeeek, that is what I thought. When I get a dump from my product database, it is loaded with HTML, that is a pain to get rid of.
    I know I can cut the tag and replace with nothing manually in access or excel, but is there a more efficient way to strip the html?

    Thanks

  13. #13
    Moderator MichaelColey's Avatar
    Join Date
    January 18th, 2005
    Location
    Mansfield, TX
    Posts
    16,232
    In Perl, it's pretty easy to remove HTML:

    $field =~ s/<[^>]*>//g;

    Or, if you would rather replicate all tags with spaces (to prevent words from running together):

    $field =~ s/<[^>]*>/ /g;

    Then you can do something like this to trim out all duplicate spaces:

    $field =~ s/ */ /g; # <-- There are three spaces before the *

    It can be really handy to process datafeeds in Perl or some other programming language.

    Michael Coley
    Amazing-Bargains.com

  14. #14
    I like traffic lights
    Join Date
    January 18th, 2005
    Location
    Southern hemisphere - away from Fukushima
    Posts
    2,936
    Yes. PERL is your friend. :^)

    ****************************
    Jimmy James Inc. fan club membership # 3312

    "But Jimmy had fancy plans, and pants to match"

  15. Newsletter Signup

+ Reply to Thread

Similar Threads

  1. How to format the data to use as normal link
    By megatonloh in forum ShareASale - SAS
    Replies: 2
    Last Post: July 26th, 2006, 12:35 PM
  2. Data Feed Formats: Does More then 1 Format Help?
    By rhkocatas in forum Programming / Datafeeds / Tools
    Replies: 4
    Last Post: February 23rd, 2006, 04:55 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •