Jeff’s Comments (group member since May 08, 2013)

Jeff’s comments from the Goodreads Developers group.

Hi Nadia, please see my response to your question in the other thread.

Sorry we can't accomodate this request.

Hi Tuula,

You probably want to setup an ONIX feed for this data. Please contact support@goodreads.com to set this up.

Hi Nadia,

Based on your message it looks like you are asking if it's possible to upload all of our author data to your website. This is not allowed according to the Goodreads Developer API Terms of Service.

What you are asking probably violates the following terms:
#4 "Not use the API to harvest or index Goodreads data"
#9 "Not use the Goodreads data as part of a commercial product without our explicit written consent. "

In addition, any data that you get from Goodreads is subject to rule #5: "You may store information obtained from the Goodreads API for up to 24 hours."

We don't have the reading challenge API available yet, but what you could do is write some Javascript on the page to extract the info from the widgets as they load into some invisible DIV and then put them into a table.

I'm not sure how you would detect or control when those widgets load on the page, but there may be some Javascript libraries like jQuery that you might be able to

The Reading Challenge widgets were intended for individual users to host on their web page and this is probably the best you can do until we add the Reading Challenge to the API (which is in our backlog but not scheduled)

We don't provide searching by ASIN as we don't have that function in our own app.

You might have some luck with the Amazon public Product Advertising API.
http://docs.aws.amazon.com/AWSECommer...

Do you mean the image or the URL?

We don't have the the ability to redistribute the images. Regarding the URL, see #5 of the API terms:

You may store information obtained from the Goodreads API for up to 24 hours. Goodreads needs the ability to modify, remove, and update the order of our data, which caching would prevent. An exception to this rule is if the data is from your own account or the OAuth-authenticated users account, in which case the data may be stored permanently.

Thanks for trying guys. I'm not sure what else we can do on our end, especially without a technical contact at GoDaddy.

I'm commenting for the historical record.

We made a change on our server side to remove any rate limiting we did for API calls from shared hosts to see if that was the problem. It wasn't.

I think the only thing left to do is for GoDaddy users to ask GoDaddy to see if they can do more debugging on their end.

We just made change yesterday that might fix this issue by removing a capacity block for shared hosts, which includes GoDaddy users. Could you give it a try and see if it works now?

It's a long shot, but if it does end up working that will tell us something.

If it doesn't work, our sysadmin speculated that the problem could be GoDaddy's SSL validation, which requires GoDaddy to change their SSL configuration.

If you could dump the certificate info in PHP and email that to me, we might be able to rule out problems on our end.

Marianne, could you try it again now?

The problem might be related to shared hosting, so we changed something on our server to be more friendly to that.

What is your WP service provider?

These are different editions of the same work. Harry Potter #1 is book ID 3 because Otis added Harry Potter as the first few books when he created Goodreads.

I'm following up with the UBB developer today.

Do you have terminal access to your website? If so, please PM me.

There's a space in your URL between "dakota" and "cassidy". I think you might need to explicitly escape the space as "%20"

Hi Marianne, sorry you are having this problem.

I looked into our logs a bit and I found that you were able to look up a book by ISBN once in October and a few times in September and August. Is this consistent with what you are seeing?

Which functions of UBB are you unable to perform?

hey Sachin,

3) You can see this option in your user settings.
4) There is a spoiler flag on the XML API for review lists. However, this doesn't exist on the reviews iframe widget.

Our search API call doesn't provide a description in the search results because our apps don't use the description in the search results.

Recommendations are grouped by genre and similar books on your shelves.

Are your string indicies not integers? This sounds like an error check in the library you are using.

Is it a single call where you send a list of ISBNs? If not, it's a seperate call.

You can only search for one book per request.