Truncated error message when searching by ISBN with hyphens included

ConversazioniBug Collectors

Iscriviti a LibraryThing per pubblicare un messaggio.

Truncated error message when searching by ISBN with hyphens included

1ArlieS
Modificato: Ott 6, 2022, 9:20 pm

I have pretty much always included hyphens in my ISBNs, e.g when searching at https://www.librarything.com/addbooks

Until today, that's worked fine.

Today I searched for 978-0-52251183-0 and got an error message saying "No results found for '978-0-522511'" (quotes in original were ")

I then searched for 9780522511830 - still no luck, but at least the error message was correct: No results found for "9780522511830"

Then I noticed I'd mistyped the ISBN, searched for 978-0-52551183-0, and successfully found the book I wanted to add to my collection.

I'm at least 90% certain I'd have noticed an error message with a truncated ISBN in the course of cataloguing large numbers of other books; this isn't my first typo, or even my hundredth.

So this is probably a newly introduced bug.

2bnielsen
Ott 6, 2022, 4:16 pm

I think you need to tell us which source you were using if we are to be able to reproduce the bug.

3ArlieS
Ott 6, 2022, 9:04 pm

>2 bnielsen: I default to Overcat.

But I got the same misbehaviour just now from Library of Congress and British Library - but not Amazon UK books, which just says "no results found for your request."

4gilroy
Ott 7, 2022, 8:03 am

From what I remember, the add books search doesn't allow for the hyphens in the ISBN. (Unless they've changed that lately. It was a no go for the first at least 10 years.)

5SandraArdnas
Ott 7, 2022, 9:51 am

>4 gilroy: I've added it numerous times with hyphens when copy pasting the ISBN from ebooks, it worked fine and just stripped the hyphens

6knerd.knitter
Feb 28, 2023, 4:34 pm

The bug reported in >1 ArlieS: seemed to actually be about the message truncating. That was happening because the incorrect ISBN you entered qualified as a UPC so it truncates it to 12 characters. Since the ISBN was wrong anyway, this does not seem like a bug to me.