Copyright (C) 2018-2024 The Open Library Foundation
This software is distributed under the terms of the Apache License, Version 2.0. See the file "LICENSE" for more information.
- Introduction
- Dependencies
- Installation
- Running
- Building and running from Docker
- Authentication
- Access via SRU
- Obtaining information about loans
- Troubleshooting
- Additional information
z2folio is a Z39.50 server for FOLIO bibliographic and holdings data, supporting record retrieval in USMARC, OPAC, XML and JSON formats. The functionality is all provided by the Net::Z3950::FOLIO library, which is also part of this distribution. It is written in Perl, and follows standard Perl-module conventions.
The name of the Docker container is mod-z3950.
Dependencies are defined in the module descriptor but since the FOLIO Z39.50 server is strictly a client to the rest of FOLIO it does not need to be installed as a part of FOLIO itself, and can run outside of a FOLIO installation provided it is pointing to an Okapi server with the following modules enabled:
Of these, the last three are fairly ubiquitous in FOLIO installations, but mod-graphql may need to be added.
The Okapi connection details (url, tenant, username, password) are defined in the configuration file or via environment variables: see Authentication below.
To install this module type the following:
perl Makefile.PL
make
make test
make install
On some platforms (e.g. my MacBook running MacOS 10.13.6 with YAZ and libxml2 installed from Homebrew 1.8.4), installing the prerequisite SimpleServer with cpan install Net::Z3950::SimpleServer fails. I fixed it using:
C_INCLUDE_PATH=/usr/local/Cellar/libxml2/2.9.4_3/include/libxml2 cpan install Net::Z3950::SimpleServer
If you don't want to install, you can run directly from the development checkout as:
perl -I lib bin/z2folio -c etc/config -- -f etc/yazgfs.xml
terminal1$ docker build -t zfolio .
terminal1$ docker run -it --rm -p9997:9997 -e OKAPI_PASSWORD=swordfish --name run-zfolio zfolio
terminal2$ yaz-client @:9997
Z> find @attr 1=4 a
Z> format opac
Z> show 1
Note: if running in Kubernetes, it may be useful to turn off session logging by adding the -v-session parameter to the arguments. For example, perl -I lib bin/z2folio -c etc/config -- -f etc/yazgfs.xml -v-session. Session logs can be quite noisy on Kubernetes due to tcp healthchecks.
Docker containers get published as folioorg/mod-z3950 and folioci/mod-z3950.
Whichever approach to running the server you prefer, the default configuration file specifies that the password used to authenticate onto the back-end FOLIO system must be specified in the FOLIO_PASSWORD environment variable. You can provide that however seems best to you -- e.g. injecting it into a Docker container with the -e name=value as above -- or indeed use a different configuration file that hardwires the credentials.
Thanks to the magic of the protocol-polyglot YAZ GFS, the FOLIO Z39.50 server also serves the SRU (REST-like) and SRW (SOAP-based) protocols. For example, if running the server on your local host, you can use the following to obtain an XML-formatted OPAC record containing both bibliographic metadata in MARCXML format and holdings-and-item information such as might be used by an OPAC. Replace placeholder with the real database name (or tenant id).
http://localhost:9997/<dbname>?version=1.1&operation=searchRetrieve&query=title=a&maximumRecords=1&recordSchema=opac
The Z39.50 server obtains information about the holdings and items associated with each instance record from FOLIO using mod-graphql, which behind the scenes performs searches for each holding record associated with the instance, and for each item in each of those holdings -- returning the aggregated tree-shaped record. This process can be expensive on the back-end.
In order to obtain information about loans -- specifically, the availability date of those items that are on loan -- it is unfortunately necessary to have mod-graphql run yet another search for each item in the response, fetching information about that item's open loans. For records with many items, this is likely to nearly double the load on the back-end system, and the response time when fetching the record.
Rather than impose this burden on all users of the FOLIO Z39.50 service, the default configuration does not request information about loans. However, as well as the regular GraphQL query mod-search.graphql-query, which is used by the default Z39.50 server configuration, the supplied set of configuration files also includes etc/mod-search-with-loans.graphql-query, which is identical except that it does request the loan information. Clients that need availability dates should use this extended version of the GraphQL query. The easiest way to do this is to append the string |withLoans to the end of the Z39.50 database name: for example, instead of the database name books, use books|withLoans. This version of the database will include the availabilityDate field in its OPAC records.
Fetching information about loans requires the FOLIO installation to provide version 1.4 or better of the graphql interface, most likely though mod-graphql version 1.13.1 or higher.
If when you perform a search your Z39.50 client reports
Cannot query field "search_instances" on type "Query".
The problem is that the back-end FOLIO service you are searching in does not have mod-search (ElasticSearch-based searching in inventory), which was first released in FOLIO R1-2021 (Iris). In this case, you should configure the Z39.50 server to use the older approach of searching directly in mod-inventory-storage. You can most easily do this by changing the graphqlQuery entry in etc/config.json from "mod-search.graphql-query" to "instances.graphql-query". Note, however, that as of FOLIO R2-2022 (Morning Glory), searching directly in inventory will no longer work for full-text searches such as author and title, only for exact-value searches such as HRID and ISBN.
- Capabilities of this Z39.50/SRU server
- The change-log for this module.
- The
z2folioprogram. - The underlying library.
- The configuration file format.
- The FOLIO-inventory fields that are used to make holdings information
- Developer documentation about the source code
- Developer documentation about the release procedure
- Developer documentation about FOLIO's SRS system, which the Z-server uses to obtain MARC records.
- Developer documentation about the Z39.50 OPAC record format and the YAZ toolkit's XML equivalent.
Other modules are described, with further FOLIO Developer documentation at dev.folio.org
See project ZF at the FOLIO issue tracker.