Ah well I would validate on receipt from our client, for whom we have the responsibility to produce good listings. Then once the data is in my control, I can send to google secure in the knowledge that it will be acceptable. I see no advantage in just sending stuff up then groping through a typically bad web UI to edit errant values. Simply doesn't scale.
On Dec 1, 9:19 pm, Celebird <[EMAIL PROTECTED]> wrote: > i bothered implementing a modified luhn > before the google-base quality feature -- > so now i feel i've wasted the effort. > > but since the ~70 other validation checks take > under a few minutes per 50,000 items they can > sometimes save time when typos are an issue. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
