Our company (Tantor Media) currently values the good reads website, and many of our employees use it as a source of information for knowing what titles are interesting, up and coming, etc.. We consider it a valuable source of information.
I am designing an internal application for our company to use. The main goal is to collect feeds from puballey & mozenda and collate them into an easily traversable list of titles. The problem is that the lists from both companies do not uniquely identify authors/publishers/series/etc... and instead just send the author/s of a book as "Mary Jane".
My original plan was to use goodreads api to feed it an isbn, and then get back a uniquely ID author/publisher/etc... so that when I add the feeds into our database, I can correctly associate "Mary Jane" author with her books, vs "Mary Jane" a different author with other books.
The problem is that due to the Goodreads Developer API TOS, #4 & #5 make this not possible.
My original plan was to store the goodreads unique id's (UID)for author (example) within our tale, so that when a future isbn is looked up, if the author UID is the same as what I already have, then I can link it internally, if not, then I'll create a new entry internally for a new author. This would violate #5 as I'd have to store the goodreads UID for longer than 24 hours.
To implement this while adhering to the TOS, I'd have to submit the isbn, along with any other isbn's of any books who's authors share the same " " as the source book, and then compare the UID's of the authors without actually storing any good reads UID data itself. This would result in a much larger overhead and bandwidth for both our app and for goodreads.
Good reads customer service suggested posting my question here since engineers frequent these forums. Can you suggest any way for our company to continue to use goodreads as a source of high quality data, without unecessary overhead, or should I seek other options? (Google Books, Open Library, etc..)
I am designing an internal application for our company to use. The main goal is to collect feeds from puballey & mozenda and collate them into an easily traversable list of titles. The problem is that the lists from both companies do not uniquely identify authors/publishers/series/etc... and instead just send the author/s of a book as "Mary Jane".
My original plan was to use goodreads api to feed it an isbn, and then get back a uniquely ID author/publisher/etc... so that when I add the feeds into our database, I can correctly associate "Mary Jane" author with her books, vs "Mary Jane" a different author with other books.
The problem is that due to the Goodreads Developer API TOS, #4 & #5 make this not possible.
My original plan was to store the goodreads unique id's (UID)for author (example) within our tale, so that when a future isbn is looked up, if the author UID is the same as what I already have, then I can link it internally, if not, then I'll create a new entry internally for a new author. This would violate #5 as I'd have to store the goodreads UID for longer than 24 hours.
To implement this while adhering to the TOS, I'd have to submit the isbn, along with any other isbn's of any books who's authors share the same " " as the source book, and then compare the UID's of the authors without actually storing any good reads UID data itself. This would result in a much larger overhead and bandwidth for both our app and for goodreads.
Good reads customer service suggested posting my question here since engineers frequent these forums. Can you suggest any way for our company to continue to use goodreads as a source of high quality data, without unecessary overhead, or should I seek other options? (Google Books, Open Library, etc..)