Configuring manatus
Manatus uses data from configuration files to direct harvests and transformations.
Manatus looks for configuration files in a three step process
envar
setting envars
home dir….
mod dir …
Auto build from CLI
The status subcommand of the CLI can be used to view located configs, ENtries can be added and deleted as well from the CLI.
manatus.cfg
Main program configuration. Multiple profiles can be defined with [<profile name>]
CONFIG ENTRIES
InFilePath
- path to input filesOutFilePath
- path to write output files toOutFilePrefix
- (optional) prefix written to output file nameCustomMapPath
- path to custom maps directoryCustomMapTestPath
- path to custom map testing fileCustomMapTestName
- name of custom maps testing fileLogPath
- file path for writing log filesLogLevel
- level to set the default loggerProvider
- provider name as it will appear inedm:provider
manatus_harvests.cfg
Contains data about harvest data providers. Each provider begins with a section header [<provider>]
CONFIG ENTRIES FOR EACH SECTION
oaiendpoint
- URL where data is available (OAI or API)setlist
- comma separated list of setSpecsmetadataprefix
- metadata format to harvest
manatus_scenarios.cfg
Provides manatus information required during the transformation process. Each provider begins with a section header [<provider>]
CONFIG ENTRIES FOR EACH SECTION
scenario
-manatus.scenario
to apply to data providermap
- name of transformation map to apply to datadataprovider
- data provider’s name as it will appear in theedm:dataProvider
elementintermediatedataprovider
- (optional) intermediate data provider’s name as it will appear in thedpla:intermediateDataProvider
element