This step plugin for Goobi workflow allows you to edit metadata directly from an open task without using the METS editor.
| Name | Wert |
|---|---|
This plugin allows the editing of configurable properties and metadata within the user interface of an open task without having to enter the METS editor. In addition to editing the metadata, it is also possible to search for other processes and to selectively transfer metadata from found processes. With the integrated thumbnail display, the representative of the object can also be set.
To install the plugin, the following two files must be installed:
To configure how the plugin should behave, various values can be adjusted in the configuration file. The configuration file is usually located here:
To put the plugin into operation, it must be activated for one or more desired tasks in the workflow. This is done as shown in the following screenshot by selecting the plugin intranda_step_metadata_edition from the list of installed plugins.
After the plugin has been completely installed and set up, it is available to the editors of the corresponding tasks. After entering a task, it is now possible to edit the metadata in the right-hand area of the user interface.
Depending on the configuration, the corresponding metadata is displayed here and can be edited. Depending on the configuration, a search for other processes is also possible here by clicking on the search icon.
Within the dialogue with the processes found, it is now possible to select which of the displayed metadata of the processes found should be taken over.
A click on one of the displayed thumbnails allows the representative to be set.
Please note that the edits are only saved when the button provided is clicked.
The configuration of the plugin is structured as follows:
The block <config> can occur repeatedly for different projects or workflow steps in order to be able to perform different actions within different workflows. The other parameters within this configuration file have the following meanings:
For each metadata to be displayed, an element <displayfield> can be defined. This controls the display and storage of the respective data.
For the search for other processes, it is possible to specify which of their metadata should be displayed and, if necessary, adopted.
| Value | Description |
|---|---|
| Value | Description |
|---|---|
| Value | Description |
|---|---|
Identifier
intranda_step_metadata_edition
Repository
Licence
GPL 2.0 or newer
Last change
25.07.2024 11:57:05
project
This parameter determines for which project the current block <config> should apply. The name of the project is used here. This parameter can occur several times per <config> block.
step
This parameter controls for which workflow steps the block <config> should apply. The name of the workflow step is used here. This parameter can occur several times per <config> block.
thumbnailsize
This parameter determines the size of the thumbnails to be displayed for determining the representative.
hideEmptyFields
This element can have the values true and false. The element also has the attribute onlyEmptyReadOnlyFields. If the element has the value true, empty metadata fields are hidden. The attribute onlyEmptyReadOnlyFields can also be used to control whether only empty ReadOnly fields (true) or all empty fields (false) should be hidden. The default value of onlyEmptyReadOnlyFields is true.
imageFolder
This parameter determines from which directory the images are to be used for display. Common values here are, for example, master or media.
preselectFields
This parameter can be used to specify whether the metadata found within the process search of this plugin should already be preselected so that a simple transfer of the metadata can take place.
showImages
This parameter determines whether the image area for selecting the representative is to be displayed.
showImportMetadata
This parameter controls whether the button for searching in existing processes and their data transfer should be possible.
source
This specifies where the field should get its content from. Possible values for this are property, metadata and person.
name
The parameter defines the internal name of the field.
type
The parameter type defines how the field should look like. Possible values for this are text, checkbox, multivalue or list.
required
The value required defines whether the value must be filled in by the user.
helpText
Here an explanatory help text can be defined for the field content, which the user can display.
validationRegex
This parameter can be used to define a regular expression to check the field content for validity.
validationErrorText
Here you can define the message to be displayed if the validation was not successful.
label
The parameter can be used to define a label that is displayed to users for the field.
structType
This parameter defines the structural element from which the metadata is to be used for the display (e.g. anchor).
defaultValue
Here you can define a default value to be set if no value is available.
searchable
This parameter can be used to define whether the content of this field is to be used for the execution of a search.
suffix
This allows you to specify a suffix to be added to the search query when searching for other processes with the same field content.
vocabularyName
The name of the vocabulary is defined here if it is to be used for the display of selectable data records (e.g. technical terms).
searchParameter
This paremeter is optional and repeatable. It is used to further restrict records from the vocabulary (e.g. type=AccessLocations)
rulesetName
The parameter specifies the name of the metadata type as defined in the ruleset.
label
This parameter defines the label of the field to be displayed for the metadata.
selectable
The parameter can be used to determine whether the metadata can be selected for a transfer to data.
