Wrong filename when adding a book by its ISBN

Hello,

I try to add a book (https://fernwoodpublishing.ca/book/research-is-ceremony-shawn-wilson) by its ISBN (9781552662816) in my library but instead it adds another one (http://brunswickbooks.ca/Guantanamo-North-Robert-Diab/) (ISBN : 9781552662793).

As you can see, the ISBN of the second book is not the same at the first one, so Zotero is getting wrong data. The publisher name is wrong too. (I think it's because the books are from the same publisher whom name changed between the two books).

I add the book manually but I'd like to report this error in order to make it easier for the next person who will need it.
How can I do that ?

I hope it's clear, sorry if it's not !
  • This is mis-cataloged in the US Library of Congress, where Zotero is getting the data. I'm not sure there's a good way to report this; we can't fix it in Zotero, I'm afraid.
  • You can see the incorrect LoC catalog entry here: https://lccn.loc.gov/2009367833

    I've reported the error to them via the button.
  • Ok thanks for your answer ! I suspected something like this...
  • I am having this exact issue with this exact same book...
  • It's a bit odd that this is still happening: The LoC catalog was actually promptly corrected after I reported this (and you can see that on the page), so it appears their API is somehow not up-to-date with the cataloging data. Still nothing much we can do about that, but I'll try to figure out who to report this to.
  • edited September 30, 2020
    A search for 9781552662816 on loc.gov returns both entries.

    If you look at the MARCXML record for Guantánamo North, there's this:

    <subfield code="e">tc12 2019-02-04 9781552662816 removed</subfield>

    So maybe their search/API is just picking up that field?
  • ah -- we can see if we can tighten the search in the API call, but I was pretty sure we're already querying explicitly for ISBN. Thanks for the pointer, I had missed that in the MARC
  • There's a common ISBN listed for both items: 1552662810. Maybe this is causing the issue.
Sign In or Register to comment.