Cataloging


Home Prev	Chapter 12. 3.2.0 New Features	Next

Add UPC to z39.50 search for OCLC and LOC

Add UPC as a search attribute for both OCLC and LOC targets in z39.50 for cataloging.

Asynchronous Vandelay Imports

Vandelay imports are now monitored from the browser client asynchronously, meaning the client requests updates from the server instead of waiting for the server to respond to the original import request. This changes allows for incremental progress updates in the browser client.

New Database Table

This adds a new database table vandelay.session_tracker for tracking in-progress vandelay upload activity. A new tracker row is added for each of "upload", "enqueue", and "import" actions, linked for a given session by the value stored in the "session_key" field.

The table tracks other potentially useful data, like the staff member and workstation where the action was performed.

Upgrade notes

Users of NGINX as a reverse proxy may need to set a suitable client_max_body_size value in the NGINX configuration so that large MARC record uploads are not truncated. Note that this would have always been necessary, but since this feature allows larger files to be more reliably queued and imported, the need to set client_max_body_size became more apparent.

Support for Last Inventory Date

Evergreen now provides an option to add an inventory date to items to facilitate the process of performing inventory in libraries. Staff can add an inventory date to an item in one of the following ways:

From the check in screen, there is now an Update Inventory check in modifier. When selected, scanned barcodes will have the current date/time added as the inventory date while the item is checked in.
From the Item Status screen, an action is available to add the current date/time as the inventory date to selected items.

This new feature will also store the workstation that was used when the inventory date was updated.

Parallel Ingest with pingest.pl

A program named pingest.pl is now installed to allow faster bibliographic record ingest. It performs ingest in parallel so that multiple batches can be done simultaneously. It operates by splitting the records to be ingested up into batches and running all of the ingest methods on each batch. You may pass in options to control how many batches are run at the same time, how many records there are per batch, and which ingest operations to skip.

Note

The browse ingest is presently done in a single process over all of the input records as it cannot run in parallel with itself. It does, however, run in parallel with the other ingests.

Command Line Options

pingest.pl accepts the following command line options:

--host: The server where PostgreSQL runs (either host name or IP address). The default is read from the PGHOST environment variable or "localhost."
--port: The port that PostgreSQL listens to on host. The default is read from the PGPORT environment variable or 5432.
--db: The database to connect to on the host. The default is read from the PGDATABASE environment variable or "evergreen."
--user: The username for database connections. The default is read from the PGUSER environment variable or "evergreen."
--password: The password for database connections. The default is read from the PGPASSWORD environment variable or "evergreen."
--batch-size: Number of records to process per batch. The default is 10,000.
--max-child: Max number of worker processes (i.e. the number of batches to process simultaneously). The default is 8.
--skip-browse , --skip-attrs , --skip-search , --skip-facets , --skip-display: Skip the selected reingest component.
--start-id: Start processing at this record ID.
--end-id: Stop processing when this record ID is reached.
--pipe: Read record IDs to reingest from standard input. This option conflicts with --start-id and/or --end-id.
--max-duration: Stop processing after this many total seconds have passed. The default is to run until all records have been processed.
--help: Show the help text.

View Authority Record by Database ID

A new interface allows catalogers to retrieve a specific authority record using its database ID. Catalogers can find those IDs in subfield $0 of matching fields in bibliographic records.

To use the new authority record viewer:

Click Cataloging → Retrieve Authority Record by ID.
Type in the ID number of the authority record you are interested in. Don’t include any prefixes, just the ID number.
Click Submit.
View or edit the authority record as needed.