Data import without catalogue query for the Zentralbibliothek Zurich

This import plugin for Goobi workflow allows data to be imported without a catalogue query, as is required for the Zentralbibliothek Zurich, especially for multi-volume works.

Overview

Name	Wert
Identifier	intranda_import_eth_no_catalogue
Repository	https://github.com/intranda/goobi-plugin-import-zbz-no-catalogue
Licence	GPL 2.0 or newer
Last change	23.08.2024 11:12:56

Introduction

This import plugin allows data to be imported without a previous catalogue query. It inserts data into the user interface that has previously been copied from an Excel file and where the columns are separated from each other using TAB.

Installation

To be able to use the plugin, the following files must be installed:

/opt/digiverso/goobi/plugins/import/plugin-import-zbz-no-catalogue-base.jar
/opt/digiverso/goobi/config/plugin_intranda_import_zbz_no_catalogue.xml

Once the plugin has been installed, it can be accessed from the overview of production templates by using the second blue button next to the selected production template.

Production template with additional blue button for mass import

Once the plugin has been entered, a user interface is available in which the data to be imported can be selected or uploaded.

User interface of the import plugin

Overview and functionality

After selecting the correct plugin, the data, which is either available as TAB-separated CSV data or copied from an Excel file, can be inserted into the Records field in the user interface. The data has the following structure:

Column	Metadata	Explanation
1	MMS-ID	If this contains an underscore, a multi-volume work is created, otherwise a monograph. This is a mandatory entry.
2	Shelfmark	This is a mandatory entry.
3	Title	This is an optional specification.

Immediately after inserting the data and clicking on Save, the creation of the processes starts without a catalogue being requested.

Configuration

The plugin is configured in the file plugin_intranda_import_zbz_no_catalogue.xml as shown here:

<config_plugin>
	<config>

		<!-- which workflow template shall be used -->
		<template>*</template>

		<!-- define if import shall use GoobiScript to run in the background -->
		<runAsGoobiScript>false</runAsGoobiScript>

	</config>
</config_plugin>

The following table contains a summary of the parameters and their descriptions:

Parameter	Explanation
template	This can be used to define which production template the respective config block should apply to.
runAsGoobiScript	This parameter can be used to specify whether the import should take place as GoobiScript in the background.