Goobi 1.9.1 - intranda Edition

Read-only in the property mechanism

Individual properties can now be configured in a way that allows users to read the values at the corresponding points but not to edit them.

By way of example, you can configure a property that needs to be captured during the scanning process but is then restricted to read-only access during the subsequent quality control stage.

Compulsory fields in the property mechanism

The property mechanism has been modified to allow properties to be defined as compulsory fields with the result that in some cases fields have to be completed, while in others they are optional.

Configurable title length in the structure tree

Goobi can now be configured in such a way that the titles in the METS Editor structure tree can either be limited to a certain length or displayed in full.

Optimised export function

During manual and automatic export, folders are now only generated if corresponding files also exist. Empty folders are no longer created.

Optimised Web API

As well as messages, the Web API now returns a valid HTTP status code. This makes it easier for external programs to validate the results of Web API calls automatically.

Enhanced docket generation

To make this possible, a new configuration file (goobi_exportXml.xml) was introduced that allows you to define which metadata should be available from the anchor or METS file to generate dockets using XSLT.

Enhanced import interface

The plugin-based import interface allows you to create a large number of processes on the basis of a single dataset. This makes it possible, for example, to add hundreds of volumes from a single periodical to a simple dialogue box. All you need to do is enter the information that varies between volumes.

AORDER attribute in anchor files

From now on, the ORDER attribute will be written for individual volumes in the structMap contained in the anchor files.

<mets:structMap TYPE="LOGICAL">
  <mets:div ADMID="AMD" CONTENTIDS="urn:nbn:de:12345-485679" DMDID="DMDLOG_0000" ID="LOG_0000" LABEL="Minerva" TYPE="Periodical">
    <mets:div CONTENTIDS="urn:nbn:de:12345-2493896" ID="LOG_0001" LABEL="Band 1 (1792)" ORDER="001" TYPE="PeriodicalVolume">
      <mets:mptr LOCTYPE="URL" xlink:href="http://viewer.intranda.com/metsresolver?id=1958318_001" />
    </mets:div>
    <mets:div CONTENTIDS="urn:nbn:de:12345-2493896" ID="LOG_0002" LABEL="Band 2 (1792)" ORDER="002" TYPE="PeriodicalVolume">
      <mets:mptr LOCTYPE="URL" xlink:href="http://viewer.intranda.com/metsresolver?id=1958318_002" />
    </mets:div>
  </mets:div>
</mets:structMap>

Improved error handling in the workflow

Error messages can no longer be sent to the same workflow step. Also, error messages can no longer be sent from the first step in the workflow. The same applies to specific solutions to problems. These can no longer be sent to subsequent stages if the step being worked on is the last step in the workflow.

Configurable number of information items displayed in ‘batches’

You can now configure the number of processes and batches that can be displayed in the admin screen for batches. This can be done using the following parameter “batchMaxSize” in the configuration file goobi_config.properties:

batchMaxSize=200

If the parameter is missing or no value is given, up to 100 datasets will be shown.

Improved configuration of session time-out

Logged-in users can now configure the time-out for their session themselves. For users who are not logged in, Goobi will use the value defined in the web.xml.

<session-config>
  <session-timeout>30</session-timeout>
</session-config>

Use of parameters in messages

The program logic used to translate text was extended so that users can now enter a list of parameters as well as using the existing key system.

Key= a {0} with {1} parameters

If the values ‘text’ and ‘several’ are entered into the list of parameters, the program logic will translate the key as:

„A text with several parameters."

Optimised LDAP entries

The ‘ldapLogin’ field in the edit dialogue box for users is now optional. From now on, all LDAP fields will be hidden if a directory service is not being used. In this context, the connection via SSL and TLS has also been improved.

Improved export function

When you perform an automatic export, any validation errors will now lead to the task being cancelled. You can also configure whether automatic exports should include images and OCR results or no additional data.

Improved handling of archived image folders

Goobi expects to find certain folders available at different points in the workflow. Some of these, including master and media folders, are essential, while other derivative or OCR folders are optional.

Goobi can also work with any thumbnail folders that may have been defined, even if the master and media folders have already been archived. It is no longer necessary to restore images from the archive in order to modify the METS data.

Enhanced filter syntax

It is now possible to conduct a search for step titles containing a minus.

Problems resolved in the latest version

• Goobi version 1.9.1 has rectified a fault that led to an error message being produced if a docket ID was missing in the variable replacer.
• The revision number that was missing after the switch from SVN to GIT has now been added to all components.
• If the ‘access’ attribute is missing in the file ‘goobi_processProperties.xml’, Goobi no longer produces an error message. Instead it takes the default value ‘read access’.
• The new version has rectified a fault that in some very rare cases led to properties on an open task page not being displayed.
• From now on, new templates have to be saved before adding steps or properties. This prevents errors when creating the template.
• It is no longer possible to add blank text to the process log..
• The check boxes used to amend filters are now displayed even if the hit list is blank..
• It is no longer possible to add multiple user groups or projects in the user admin section.
• The size of the pop-up dialogues displayed by Goobi has been adjusted.
• The new version has rectified a fault that in some very rare cases allowed users to switch the language of another user.
• IP addresses are now displayed if an Apache web server has also been installed.
• In the previous version, folders were given two underscores when exporting. This fault has now been rectified..
• The “NoClassDefFoundError” that was displayed after restarting the application server has been removed by refactoring the helper class.

Goobi 1.9 - intranda Edition

General improvements

Revised search function

Goobi 1.9 brought a huge improvement in search functionality with the option to perform a wide range of more detailed searches for specific data. At the same time, the search syntax was thoroughly revised and simplified.

In order to simplify the search process, a new search dialog box was designed that provides a clear interface allowing users to combine different search options without the need for specific training.

Batches

The batch concept was introduced to allow users to process large volumes of data for mass digitisation projects. Batching makes it possible to direct a number of individual units through the workflow in groups. The batches are created automatically by performing a mass import. If the batches subsequently need to be combined differently, there is an option to modify the combinations in the new admin dialogue box for batches.

Exporting tables

Search requests and the corresponding results in the form of tabular process lists can now be saved as Excel files. Additional statistical columns and the actual search request are saved in the Excel file as well as the table columns.

Exporting statistics as an Excel download

Users can now generate and download individual Excel files based on the statistics produced. These files can then be used for other purposes (e.g. billing ) in external programs.

Archiving projects

Projects that have expired (and for which no further volumes are to be added) can now be given the status ‘deactivated’.

Volumes from deactivated projects will not be automatically displayed in the process list. However, the administrator may choose to display them by selecting the checkbox above the table.

Hiding completed processes

Processes for which every step of the workflow has been completed are no longer displayed in the process list. However, the checkbox above the table provides an option to include completed processes in a given search and in the results display.

Web API

The previous Web API implementation was extended to work with the same plug-in mechanism as that used by mass imports. Individual Web API commands can be installed in Goobi separately during run time allowing calls to be made by external programs via URL calls.
Some examples from intranda are given below:

• closeStep
• exportDms
• addStep
• addProcess
• deleteProcess
• version
• help
• ucc
• ucc_upload
• addToProcessLog
• runScript
• processFilter
• stepFilter
• findWrongStatus
• reportProblem

Example calls:

• http://intranda.com/goobi/wi?command=addToProcessLog&token=test&processId=12&value=myErrorMessage&type=error
• http://intranda.com/goobi/wi?command=addToProcessLog&token=test&stepId=12345678&value=myDebugMessage&type=debug
• http://intranda.com/goobi/wi?command=processFilter&token=test&filter=stepopen:myOpenStepName
• http://intranda.com/goobi/wi?command=stepFilter&token=test&filter=stepopen:myOpenStepName

Message types included in process log

Goobi’s previous Wiki field was extended to include a type allocation with the result that individual messages can now be given a type when adding to the log. However, existing messages can no longer be deleted subsequently by other workflow staff, although they may add new messages. Correction messages and the corresponding solutions (as well as externally generated messages) are listed together in chronological order with a time stamp. This makes it possible to reconstruct individual workflow steps and processes with great accuracy.

Default for collections

User can now specify individual default values for specific projects when creating processes. Selecting from a collection is only necessary if that collection is not the same as the default.

Extended import interface

The plug-in import interface was extended to include an additional type. From now on, users can also select and import files directly from a server directory. The functionality depends on the individual import plug-in.

Read-only field in the metadata editor

The configuration options for the metadata editor were extended to allow users to set individual items of metadata as read-only and thus prevent them from being processed.

Extended filter options for own tasks

The range of filter options available for a user’s own tasks was extended to match those available for processes. The same uniform syntax can now be used in all areas.

Internationalisation

The language files aimed at English- and Spanish-speaking users were completely revised. All text was checked and improved with the help of qualified, mother-tongue translators.

Usability optimisation for the Enter key

In many areas of Goobi, pressing the Enter key used to have the unintended effect of cancelling. This was checked for all forms and modified to ensure that the correct default action was followed. This alone has made working with many forms much more user-friendly and intuitive.

New property mechanism

The mechanism for managing properties was completely revised allowing for the uniform processing of properties and centralised control of those properties, e.g. when calling scripts. Individual properties are now always saved to the process rather than to individual workflow steps. They can be configured selectively and displayed for in...