Add Z3950 and OpenLibrary

[meteos77]

misspelled names are imported with OpenLibrary
exemples
9782259203043 Le Coeur a 2 places par Françoise Dorin
9782221091319 IL ETAIT MINUIT CINQ A BHOPAL

names well spelled with
[Z39.50-1]
database_name = abes-z39-public
format = "utf-8"
hostname = carmin.sudoc.abes.fr
name = Sudoc
password =
port = 10646
proxy_host =
proxy_port =
record_syntax = unimarc
username =

the 2nd one is the "Bibliothèque Nationale de France - BNF" but I don't know if we can use it without authorization, I'm asking for information.

with OpenLibrary probably a small encoding problem

test-add-Z3950-and-OpenLibrary.sqlite.tar.gz

good courage :-)

[meteos77]

I did some tests and here is my feedback

report_with_OpenLibrary_queries.txt

report_with_Zz3950-BnF_queries.txt

[textbrowser]

https://en.wikipedia.org/wiki/Z39.50

The syntax may be because of the limitations of computers in the 1970s.

[meteos77]

Libraries are like ocean liners, changes are made over a long period of time, so a change represents a lot of work, so the international standards ...

[meteos77]

if I have followed everything correctly we went from Z3950 with marc; unimarc ...
to SRU with marcXML

[textbrowser]

That's right. :)

[textbrowser]

If you can query the Z39.50 server openly, we can assume that you don't need permission. :)

[meteos77]

I have progressed since 1 month :-)

[textbrowser]

Submitting good information is a gift. You're doing well.

[meteos77]

the improvement of the software is above all for the users
so as a user trying to help you with our possibilities seems normal to me we are in the world of free software

the accented letters do not concern you I believe so if the languages which use them do not give you this information ...

[textbrowser]

I'll try removing the enumerations in the biblioteq.conf file. For example [Z39.50-1] to [Z39.50].

[textbrowser]

this is an impression but isn't there more information on the documents by Z3950 than by SRU?

I don't know. :)

[meteos77]

no no it was an impression : I just checked between the Z3950 of BiblioteQ and the file retrieved by firefox from SRU, there are the same fields with the same information

[textbrowser]

SRU is XML? If so, it can provide the same information as Z39.50.

[textbrowser]

catalogue général de la BnF

Please test the recent change. The codec has been set to UTF-8 when accessing the INI (biblioteq.conf) file.

[meteos77]

cool it works

[meteos77]

is it easier for you to manage xml rather than unimarc?

[textbrowser]

The easiest has always been direct SQL. Zero parsing.

[meteos77]

I would ask the person at the departmental library if the file they provide us with when they lend us books can be in another format than unimarc with zone 995, you never know, that they use sql (even if I don't see how it works because the fields in their database are surely not the same as biblioteQ?)

[textbrowser]

SQL does not require parsing. You simply need to have some definitions on the schema. Then you can do whatever you wish with the data.

Schema design is difficult and I'm sure BQ's schema is not perfect.

[textbrowser]

With newer PostgreSQL engines, BQ supports row-level security. It's a very good feature. This means that a patron cannot read another patron's information (history, reserved items, etc.). Even if BQ prevented this, it ultimately falls on the database and PQ has this feature.

[textbrowser]

https://www.postgresql.org/docs/current/ddl-rowsecurity.html

[textbrowser]

SQLite, for example, requires one to enable foreign-key support at runtime.

https://www.sqlite.org/foreignkeys.html

PostgreSQL is much better with this.

[textbrowser]

BQ does not enable the support (via PRAGMA) because it's aware of the relationships. Even if it did enable it, people familiar with SQLite could violate the data by editing it through SQLite. With PostgreSQL, this is nearly impossible.

[textbrowser]

xbook_db=# select max(item_oid) from book_copy_info;
max

143
(1 row)

xbook_db=# update book_copy_info set item_oid = 150 where item_oid = 143;
ERROR: insert or update on table "book_copy_info" violates foreign key constraint "book_copy_info_item_oid_fkey"
DETAIL: Key (item_oid)=(150) is not present in table "book".

[meteos77]

it's sure that postgresql has more functionalities than Sqlite but they are not as old as Sqlite, see the additions that Sqlite will have in the future
If BiblioteQ hadn't proposed sqlite as a data support, I wouldn't have invested in it :-)
BiblioteQ with sqlite allows the transparency of the database just a file and it is GREAT in spite of the lesser functionalities.

[textbrowser]

SQLite was a request. I think.

April 12, 2008.

Released version 4.02.
SQLite 3.x is now supported.

[meteos77]

excellent idea in 2008 :-)