6.11 Configuring and displaying subcollections

The Goobi viewer can display digital collections with a hierarchy. The functionality is described in chapter 2.18.1.

The following shows the process chain that is necessary from the configuration in Goobi workflow to the display in the Goobi viewer.

Goobi workflow

In Goobi workflow, it must be ensured that the desired subcollections are already available in the creation mask. To do this, adjust the entries for the collections in goobi_digitalCollections.xml. The hash has proven itself as a separator: Example: flat structure:

/opt/digiverso/goobi/config/goobi_digitalCollections.xml
<DigitalCollection>Manuscripts</DigitalCollection>
<DigitalCollection>Greek manuscripts</DigitalCollection>
<DigitalCollection>Hebrew manuscripts</DigitalCollection>

Example with hierarchy:

/opt/digiverso/goobi/config/goobi_digitalCollections.xml
<DigitalCollection>Manuscripts</DigitalCollection>
<DigitalCollection>Manuscripts#Greek Manuscripts</DigitalCollection>
<DigitalCollection>Manuscripts#Hebrew Manuscripts</DigitalCollection>

The same change must also be made in goobi_metadataDisplayRules.xml. There the collection names are once again defined as DropDown, so that the spelling is always consistent:

Example: flat structure:

/opt/digiverso/goobi/config/goobi_metadataDisplayRules.xml
<item selected="false">
<label>Manuscripts</label>
<value>Manuscripts</value>
</item>
<item selected="false">
<label>Greek Manuscripts</label>
<value>Greek Manuscripts</value>
</item>
<item selected="false">
<label>Hebrew Manuscripts</label>
<value>Hebrew Manuscripts</value>
</item>

Example with hierarchy:

/opt/digiverso/goobi/config/goobi_metadataDisplayRules.xml
<item selected="false">
<label>Manuscripts</label>
<value>Manuscripts</value>
</item>
<item selected="false">
<label>Manuscripts#Greek Manuscripts</label>
<value>Manuscripts#Greek Manuscripts</value>
</item>
<item selected="false">
<label>Manuscripts#Hebrew Manuscripts</label>
<value>Manuscripts#Hebrew Manuscripts</value>
</item>

Goobi viewer Indexer

The Goobi viewer Indexer then converts this into a machine-readable string during indexing. The configuration of the DC field in solr_indexerconfig.xml is responsible for this. There, various options are set which prepare the contents of the field, among other things:

solr_indexerconfig.xml
<lowercase>true</lowercase>
<onetoken>true</onetoken>
<splittingCharacter>#</splittingCharacter>

The individual switches are described in chapter 3.7. As a result everything is written in lower case, spaces and special characters are removed and the configured splittingCharacter is replaced by a dot.

Example:

handschriften
handschriften.griechischehandschriften
handschriften.hebrischehandschriften

The Goobi viewer then displays the subcollections as a hierarchy tree. The collections can be translated as usual using the messages files.

Example:

messages_de.properties
manuscripts=Handschriften
messages_en.properties
manuscripts=Manuscripts

Alternatively, the translation can be done in the CMS backend on the collection page.

If processes already exist in Goobi workflow that are now to be added to the new subcollections, these must be opened in the metadata editor, adapted and the METS file then exported again.