Re: Items disapproved after updating. - jas...@realtracs.com - com.googlegroups.google-base-data-api

10 messages in com.googlegroups.google-base-data-apiRe: Items disapproved after updating.

From	Sent On	Attachments
jas...@realtracs.com	07 May 2008 10:14
Eric (Google)	07 May 2008 10:32
jas...@realtracs.com	07 May 2008 10:47
jas...@realtracs.com	07 May 2008 10:59
jas...@realtracs.com	07 May 2008 11:47
Eric (Google)	08 May 2008 16:26
jas...@realtracs.com	09 May 2008 04:29
Eric (Google)	09 May 2008 11:30
Celebird	09 May 2008 15:44
jas...@realtracs.com	15 May 2008 06:27

Subject:	Re: Items disapproved after updating.
From:	jas...@realtracs.com (jas...@realtracs.com)
Date:	05/15/2008 06:27:29 AM
List:	com.googlegroups.google-base-data-api

Thank you for the response. Yes, I agree an explanation would be very helpful. I don't think it has to be "immediate" feedback, just attaching some sort "reason" to the item when it's dissapproved would be helpful.

Thanks, Jason

On May 9, 1:30 pm, "Eric (Google)" <api....@google.com> wrote:

While not knowing the exact mechanics behind the disapproval process, I agree that some sort of explanation would be helpful. Still, developers would never receive immediate feedback since these items aredisapprovedafter the fact. I'll look into seeing if there's anything else you can do.

In the mean time, feel free to submit a feature request
athttp://code.google.com/p/gdata-issues/issues/entry.

Eric

On May 9, 4:29 am, jas...@realtracs.com wrote:

I understand there is an automated process and I would think that the process checks each attribute and validates them against a set of rules. It would be helpful, if during this automated process it could tell us which attribute failed and maybe what "rule" failed. Right now you don't get anything and when you ask or try to get support, you are told to check the program and editorial guides, which are very vague.

For example after hours of looking through my code and commenting it out line by line. I was able to determine that the "square feet" attribute (which is a float) was being set to a C# null. This caused the automated process to disapprove the item. Once I had set this attribute to 0.0F (when it was null) it no longer gotdisapproved. This is a perfect example of how the "program/editorial" guide does not help. If the automated process had added to the item a error description of the effect of "square feet attribute invalid". Then I could have within minutes been able to find the issue, by setting a break point on that line and looking at the value.

I don't understand the reason behind not wanting to help the developers and give a little more meaning as to "why" an item is disapprovedby the automated process, it could save hours of frustration.

On May 8, 6:26 pm, "Eric (Google)" <api....@google.com> wrote:

Hi Jason,

There's an automated approval system which is run after items have been inserted. Is it possible your original items aredisapprovedafter they've been successfully inserted?

Are you using one of the client libraries? If not, feel free to post the XML for one of thedisapproveditems and I'll take a look.

It tends to be difficult to work out this type of question through the discussion group so I recommend submitting a request through the contact-us form.

http://base.google.com/support/bin/request.py

You might also be able to find some additional tips in the Google Base help group, since item approval is an issue which is not specific to the API:

http://groups.google.com/group/base-help-discussion

Thank you,

Eric

On May 7, 11:48 am, jas...@realtracs.com wrote:

That is the problem, is any number of reasons. Why can't google base tell what the reason is?

I am inserting the item and then updating the item with exact same data. Why would it be "disapproved"?

On May 7, 12:32 pm, "Eric (Google)" <api....@google.com> wrote:

Hi,

Items can bedisapprovedand remain as drafts for a number of reasons. I would check that your items comply with the Program Policies and Editorial Guidelines. You can find that information
athttp://code.google.com/apis/base/starting-out.html#disapproved.

Cheers,

Eric

On May 7, 10:14 am, jas...@realtracs.com wrote:

I am adding items to google base through the api. I am able to do this with no problem. Next I am updating the items. however after updating them alot of them are "disapproved"... This is the problem withDISAPPROVED. is there is no message telling why, no email letting you what the problem is.. In my case I am updating the items with the same information that i using to "insert" the items. Why can google base not tell you the reason the item isdisapproved. I know it's running through some automated checks. As part of that why can it be displayed as to what caused the item to be comedisapproved?- Hide
quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -