Goodreads Librarians Group discussion
Questions (not edit requests)
>
Editions that have BOTH an ASIN and ISBN
date
newest »
newest »
It is a known bug that has been going on for some time. If you go to the edit page and it enter (without changing anything), it should fix the book page display.
Scott wrote: "It is a known bug that has been going on for some time. If you go to the edit page and it enter (without changing anything), it should fix the book page display."Yeah, I had seen this bug before, years ago, and thought it had been fixed.
I was doing the work-around you mention, but it doesn't seem to be sticking. There are ASIN editions that I "edited" 2+ days ago that are still showing the ISBN. I guess I'll keep doing it and hope it sticks.
It shows the ASIN on the book page for me (book you linked in msg 1). It might also be a cache issue, try clearing you cache, closing your browser, and then search again and see what displays.
When you go to a book page from a search, there is extra information added at the end of the URL. The result can be that the ASIN wouldn't be displayed. Check the difference between these two URL's:
https://www.goodreads.com/book/show/2...
(https:// www. goodreads .com/book/show/25616247-deer-dancer)
https://www.goodreads.com/book/show/2...
(https:// www. goodreads .com/book/show/25616247-deer-dancer?from_search=true&from_srp=true&qid=0BpZ5gFa0Q&rank=1)
When you delete the last part (?from_search=true&from_srp=true&qid=0BpZ5gFa0Q&rank=1) from the second URL, the ASIN will display on the book page of this Kindle edition.


However, I've come across many auto-imported Kindle editions that can be searched for by their ASIN, but what actually displays on the book page is the ISBN. (Like this one: https://www.goodreads.com/book/show/2....) If you go to edit any details of the edition, the edit details page shows the ASIN. Once saved, the ASIN displays on the page.
But! If you search for the book by ASIN or ISBN again, the ISBN is displaying on the page again.
Does anyone know what's going on here? Is it a bug that should be reported to support?