1.3 Folder configuration
The Goobi viewer contains various folder configurations, which are explained in more detail below
The parameters are explained in detail in the following table:
Setting
Description
configFolder
The parameter configFolder contains the path to the local configuration folder. This contains customised configuration and translation files that overwrite the default configuration.
viewerHome
The directory viewerHome is the base path of the Goobi viewer, relative to which further directories are searched.
dataRepositoriesHome
The dataRepositoriesHome directory is the path relative to which the individual repository folders are searched. The information whether a record uses a data repository or the classical folder structure is in the index and is automatically evaluated by the Goobi viewer.
indexedMetsFolder
The indexedMetsFolder folder contains the METS files that have been successfully indexed. It is from this folder that the METS resolver obtains the delivered METS files. This directory is searched relative to dataRepositoriesHome or viewerHome. For this reason, the value may only contain the name and not an absolute path.
indexedLidoFolder
The folder indexedLidoFolder contains the LIDO files that were successfully indexed. The LIDO resolver obtains the delivered LIDO files from this folder. This directory is searched relative to dataRepositoriesHome or viewerHome. For this reason, the value may only contain the name and not an absolute path.
indexedDenkxwebFolder
The directory indexedDenkxwebFolder contains the DenkXweb files that have been successfully indexed. From this folder the resolver retrieves the delivered DenkXweb files. This directory is searched relative to dataRepositoriesHome or viewerHome. For this reason the value may only contain the name and no absolute path.
indexedDublinCoreFolder
The directory indexedDublinCoreFolder contains the Dublin Core files that have been successfully indexed. From this folder the resolver retrieves the delivered Cublin Core files. This directory is searched relative to dataRepositoriesHome or viewerHome. For this reason the value may only contain the name and no absolute path.
mediaFolder
The mediaFolder directory contains media files for display in the Goobi viewer (image, audio and video files). This directory is searched relative to dataRepositoriesHome or viewerHome. For this reason, the value may only contain the name and not an absolute path.
origContentFolder
The origContentFolder contains other files belonging to the record which are made available for download within the record display (for example Born-Digital materials).
pdfFolder
The pdfFolder contains pre-rendered PDF files.
cmsMediaFolder
Folder in which media files (for example images) uploaded for the CMS pages are stored. The default value is cms_media.
cmsTextFolder
The cmsTextFolder contains extracted texts from CMS pages for indexing.
altoFolder
abbyyFolder
fulltextFolder
teiFolder
cmdiFolder
The Goobi viewer is able to deliver the original OCR files used for indexing. The corresponding folders are configured under altoFolder, abbyyFolder , fulltextFolder, teiFolder and cmdiFolder respectively.
altoCrowdsourcingFolder
fulltextCrowdsourcingFolder
Here, folders can be configured for ALTO and plaintext files that were transcribed with the crowdsourcing module. If a crowdsourced file exists for the requested page, it is preferably loaded instead of the original file.
annotationFolder
If annotations were created in the context of a crowdsourcing campaign, they are stored as JSON WebAnnotations in the annotationFolder.
hotfolder
If a record or parts of a record are to be re-indexed, the information for this must be placed in the hotfolder of the Goobi viewer indexer. The directory for the hotfolder is configured under hotfolder.
stopwordsFile
The absolute path to the stopwords file for the Solr search index is configured in the stopwordsFile element. This makes it possible to filter out stopwords from the search
Last updated
Was this helpful?