As usual, celebird is correct. After my last submission, I sent a query and sure enough the item had the "disapproved" element. Naturally we're quite disappointed. We can put in all the obvious check (e.g. price > zero) but there are subtle values in perhaps description or title that might be construed as in appropriate and we won't know the item was disapproved, with out a follow-on query (How long does one wait for Godot?) and won't be able to advise our clients of the problem. Further there is a risk of getting that client's domain disqualified and that could be catastrophic.
We would be happy to pre-process the feed if we could have a lists of tests from google. Seems GB might save themselves the burden if they would certify certain "applications" as pre-verified. On Jan 30, 1:35 am, Celebird <[email protected]> wrote: > i believe there's a bit of waiting for godot here. > > (1) the return-stream generally won't indicate any > disapproval since disapproval happens after inserts -- > either via automation or a google-base specialist; > otherwise illegal values should get status-code 200 -- > barring an account-wide disapproval that tom mentioned. > > (2) by definition disapproved items get a draft-status > and by definition app:draft items aren't indexed. > > (3) if the atom:id is known or possibly found via a > get of the item's feed then hasGmDisapproved should > return true; but it's waiting for godot with respect > to any other context by virtue of (1) and (2). > > at least that's my current understanding. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
