Closed deltz025 closed 2 years ago
Would you like an alternate identifier?
I think additional identifiers, like the Open Library ID or Library of Congress Control Number, would make it easier to import data for books that don't have ISBNs.
The CN is already present.
LC Control Number.
I do not wish to add identifiers which are specific to protocols and the Open Library really is a protocol. Unless of course the Open Library contains actual PDFs. If it does, like BQ, then adding its identifiers is acceptable. In a proper library, books have physical representations. PDFs and/or books.
Storing only information about things is lazy. People should be able to store the representations of those things. Videos, games, PDFs, songs. BQ can do that.
Alright, I'll just look for another app that does what I need, then.
I wrote that we can define new identifiers. You mentioned one and I responded that it already exists: LC Control Number. I prefer that the new one be not named Open Library ID because if Open Library is abandoned, we're stuck with an identifier. In the database, it can be labeled as foreign_identifier_1 and BQ can be smart to display a custom label for you such as Open Library Identifier.
There are endless possible things and they can be customized to your environment.
If you're concerned about Open Library being abandoned, why does BiblioteQ use it to quickly import data? And if it's importing data from Open Library, it would be far more efficient to allow data import from Open Library ID or LC Control as well as ISBN, because there are a vast number of books that simply don't have ISBNs attached to them.
Open Library was requested and that's how it was attached to BQ. :)
SRU and Z39.50 mechanisms require ISBNs because it was logical to do so years ago. It was natural to implement this with Open Library. This can be changed and it can be changed so that they function with multiple keys. For example. BQ can attempt the query if an ISBN exists. If one does not, it can attempt it with another key and another key and another key and another key until it has exhausted all known keys.
You asked and that is the beginning. :)
So I will add a new identifier and it will include a new Others Option where you assign it a label and that label will percolate throughout the software. In the database it will be known as foreign_identifier_1. Google has a system as well and it may have its own identifiers. There is a request to add Google too but I am not so interested in doing that right now.
New column alternate_id_1 prepared for PQ and SQLite.
Open Library query via OL completed for books.
Now for OL image query via OL identifier.
Looks great, thanks!
Completed. Available with the next release.
I come back on this great idea of having an alternative identifier to isbn
the alternative_id_1 field allows the user to enter an identifier
is alternative_id_1 dedicated to OpenLibrary or could BiblioteQ store another identifier from another online service (I think about the Ark identifier from BnF) or alternative_id_2 ?
in the Z3950 analysis (003 http://catalogue.bnf.fr/ark:/12148/cb452115699)
or
in the SRU analysis (
and place the information "ark:XXXXXXX" in this field alternative_id_1.
this variable is then used for the search of the covers h_t_t_p://catalogue.bnf.fr/couverture?&appName=NE&idArk=alternative_id_1&couverture=1&largeur=100&hauteur=250 http://catalogue.bnf.fr/couverture?&appName=NE&idArk=ark:/12148/cb452115699&couverture=1&largeur=100&hauteur=250
Thank you for this new alternative for the cover images.
BiblioteQ is a great tool, and makes cataloguing my books far easier, but I've run into this problem a few times. A few of my books are older and rarer, and while they're listed on Open Library, they haven't been issued an ISBN. The ability to search by other cataloging IDs, especially Open Library's own, would make this a non-issue.
Thanks for your hard work!