Kitodo.Production is a workflow tool suite for the support of mass digitization. Kitodo.Production is part of the Kitodo Digital library Suite.
Kitodo is an open source software suite intended to support mass digitization projects for cultural heritage institutions. Kitodo is widely-used and cooperatively maintained by major German libraries and digitization service providers. The software implements international standards such as METS, MODS and other formats maintained by the Library of Congress. Kitodo consists of several independent modules serving different purposes such as controlling the digitization workflow, enriching descriptive and structural metadata, and presenting the results to the public in a modern and convenient way.
To get more information, visit the following web sites: http://www.kitodo.org
You can also follow Kitodo News on Twitter at @Kitodo_org
The software is written in Java and using Java Server Faces web technology to run on a Tomcat Servlet container backed up by a MySQL database accessed utilizing the Hibernate framework. It uses (Unix/Windows) shell scripts and is often used with Windows shares in Samba environments authenticated via LDAP.
The project structure is IDE independent. The tool for issue building, testing and packaging of the application is Maven.
Available dependencies are fetched from Maven Central. Further dependencies (not available in Maven Central) are located in Kitodo/src/main/webapp/WEB-INF/lib. Two things that are not shipped are a Tomcat specific servlet API and an ElasticSearch server. First thing should come along with the Tomcat distribution you are building against. Second, you need to download by yourself from ElasticSearch 5.1.1 and start before Maven build. On the Windows system ElasticSearch starts after open elasticsearch.bat file from bin folder. Additional information about running of ElasticSearch can be found here.
Execute "mvn clean package" and put generated war file in Tomcat.
Basic configuration files are located under src/main/resources/ directory. To provide a custom (local) configuration, create a directory config-local and put there your specific configuration files just before you create a distribution via the mvn command. The build script will then replace every default configuration file with the configuration file it finds in your config-local directory.
Most probably, you will have to adjust these four files:
- kitodo_config.properties
- contentServerConfig.xml
- hibernate.cfg.xml
- log4j2.properties
Setting up a Kitodo instance can be quite tricky. For more help on how to configure Kitodo, please check the installation guides, the GitHub Wiki or ask questions on the mailing lists.