With unbounded thanks to Celebird we at least have discovered why (well, when) our urls were getting clobbered. (See http://groups.google.com/group/Google-Base-data-API/browse_thread/thread/a821eea254ded873#) Note to self: Don't edit via googlebase UI.
But we have yet to find our new listing via a full text search (i.e. the standard google search-the-web approach). We have a couple of theories: 1. We've sent and "deleted forever" these item multiple times and with different unique ids (these are test items; the persistence is not maintained between runs). Some cruft this push/pull is leaving in the system is holding our publishing back? 2. The urls we're using are the real deal for these items. We're in fact resending items in test (draft) mode which are referring to pages already crawled and the "new" listings aren't get exposed because of this? 3 Imperfect listing xml? Though this is of course the most likely cause, we see no evidence of same in the data quality report nor the status of the batched items. If you have had any experience at all similar to this please chime in (with or without resolution). We're letting this sit for a bit as we're about to revamp our security model, but in the meanwhile I'll keep an eye out for any suggestions that may trickle in. TIA --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
