-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding books requires identifiers #380
Comments
Because auto imports happen much faster than manual ones, they should be made in a more trustworthy way, from reliable source metadata (not the crapfest that is BWB and AMZ). That isn’t the only inconsistency to address. At
openlibrary-client/olclient/openlibrary.py Line 765 in dc9195c
DRY: let’s have one list of first-class identifiers in one place, please. That said, it would make sense to support other identifiers, not just these four. This is part of the reason we’ve had such poor uptake of pre-ISBN books from libraries outside the anglosphere, where Worldcat and LCCN coverage is less common. There are six first-class and 66 second-class identifiers listed on the edition edit page drop-down for "Select one of many…" under ID Numbers. For starters, we should pick up the BSB-ID, the Biblioteca Nacional de Español Depósito Legal, and the BnF identifiers to be treated as first-class. They are reliably and neutrally curated, far more so than Goodreads, Library Thing, Google, AMZ, and other such newcomers operating with commercial purposes. The British Library and BNB ids could also be worthwhile inclusions in the first-class list. |
|
@cclauss |
Thanks for chiming in folks!
I guess that means that the |
|
It seems that the library currently requires specifying either an ISBN or LCCN identifier in order to be able to create a new book, which differs from the behaviour of the web form for the book creation, where the identifiers are optional.
To reproduce this should work just fine
This will trigger the value error.
I'm not sure if this is expected behaviour that was designed to work like this, or whether the
openlibrary-client
is just out-of-sync with how the web-form behaves? If it's the latter I'd be happy to give it a shot to adjust it according to the web form🙂The text was updated successfully, but these errors were encountered: