Goodreads Librarians Group discussion
Questions (not edit requests)
>
(answered) Bot created garbled book record: Report or Fix?
date
newest »
newest »
Correction: ASIN B00DWWHE48 does exist on Amazon (oops). It didn't appear with an Amazon search, but DuckDuckGo found it.However, it's just that same garbled "book" listing.
https://www.amazon.com/Peril-Grafton-...
I guess my bigger question is: How should librarians handle the incorrect or incomplete GR book records that bots seem to be creating in ever-increasing numbers? Should we report a bot-created problem entry to Support, or just fix problems as we find them?
Actually it's probably a duplicate of an existing mmpb, so you can mark it invalid. But I would still report the bot activity. I've been seeing a lot of these "unknown author" records lately.
If it's not a duplicate, I'd fix it. Flag as many as you can be bothered to flag; maybe something will eventually get done.
Mesembryanthemum wrote: "I guess my bigger question is: How should librarians handle the incorrect or incomplete GR book records that bots seem to be creating in ever-increasing numbers? Should we report a bot-created prob..."I see dozens of them everyday. I neither fix nor report. The reason I don't is because a couple of months (or 3?) ago, I reported one. I had separated the edition with the ASIN and the matching ISBN. I reported the edition with which they should be recombined after the merge. The staff person didn't understand what I was reporting, took 4 days to do nothing, by which time another librarian had recombined those editions I had taken the extra time to separate. GR seems not to mind this garbage and I figure those extra editions aren't actually hurting anything so I leave them.
Thanks for the helpful information. I hadn't realized that I could flag the original creation. (I'm a newbie who's still learning the basics.)For this one, I'll flag it & mark it as invalid, because now I have my teeth into it (i.e., it's bugging me). Also, I'd like to practice these tasks on something
But I suspect I will quickly change to the strategy of leaving these types of records unfixed, because there are so many of them. There are other things I'd rather spend my librarian time on. And, as Elizabeth (Alaska) said, it seems that GR doesn't mind if they're in the database.


Should I leave the entry alone and report the problem to GR Support?
Or should I assume that this was a one-off problem and try to fix this entry? (If, that is, I can figure out what ISBN it is supposed to have.)