About
Goobi is a mature, open-source digitization solution built specifically for libraries, archives, museums, and other cultural heritage institutions. Developed and maintained by intranda GmbH since 2003, it provides a comprehensive suite of tools to plan, execute, monitor, and publish digitization projects at any scale. The platform is split into two primary components: **Goobi workflow**, which orchestrates the entire digitization pipeline — from ingest and scanning to quality control, metadata entry, and export — and **Goobi viewer**, a web-based presentation layer that makes digitized collections publicly accessible online. Goobi supports an extensive plugin architecture, enabling institutions to tailor the system to their specific processes, repository standards (such as METS/MODS, Dublin Core, and EAD), and integrations with external systems. A portable edition called **Goobi-to-go** allows teams to run the full stack in a self-contained environment without complex server setup. Backed by an active international community that participates through Goobi Days events, workshops, a public forum, and collaborative development, the project continuously evolves to meet the demands of modern digital humanities and library science. Goobi is particularly well-suited for national libraries, university libraries, state archives, and heritage organizations seeking a proven, standards-compliant workflow engine without vendor lock-in.
Key Features
- Goobi Workflow: A powerful process management engine that orchestrates every step of the digitization pipeline, from ingest and scanning to metadata creation, quality control, and export.
- Goobi Viewer: A web-based presentation layer that publishes digitized collections online, making cultural heritage materials publicly accessible with rich browsing and search capabilities.
- Extensive Plugin Architecture: A large ecosystem of plugins allows institutions to extend and customize workflows, integrate with external systems, and support various metadata standards like METS/MODS, Dublin Core, and EAD.
- Goobi-to-go: A portable, self-contained edition of the full Goobi stack that can be run locally without complex server infrastructure — ideal for smaller institutions or testing environments.
- Active Community & Documentation: Backed by a global community of institutions contributing to development via Goobi Days events, workshops, and a public forum, with comprehensive documentation available.
Use Cases
- A national library uses Goobi workflow to manage large-scale book and manuscript digitization projects, automating task assignment across scanning, metadata entry, and quality control teams.
- A state archive publishes its digitized historical records publicly online using Goobi viewer, enabling researchers worldwide to browse and search document collections.
- A university library deploys Goobi-to-go to create a portable digitization environment for offsite scanning campaigns at partner institutions.
- A museum integrates Goobi with its existing collection management system via plugins to create a seamless pipeline from physical artifacts to online digital exhibitions.
- A consortium of cultural heritage institutions collaborates through the Goobi community to co-develop shared plugins and workflow templates, reducing duplication of effort.
Pros
- Proven & Mature Platform: In continuous development since 2003, Goobi is a battle-tested solution trusted by major national libraries and archives across Europe and beyond.
- Fully Open Source: No licensing fees and no vendor lock-in — institutions retain full control over their data and infrastructure, with community-driven development ensuring long-term sustainability.
- Highly Extensible: A rich plugin system and standards-compliant architecture allow Goobi to adapt to virtually any institutional workflow or repository requirement.
- End-to-End Coverage: From raw scanning workflows to public-facing digital collections, Goobi covers the entire digitization lifecycle within a single ecosystem.
Cons
- Complex Setup & Administration: Deploying and maintaining Goobi requires significant technical expertise in server administration and Java-based systems, which may be challenging for smaller institutions without dedicated IT staff.
- Steep Learning Curve: The breadth of features, configuration options, and plugin ecosystem means new users and administrators face a considerable onboarding investment before becoming productive.
- Primarily Niche-Focused: Goobi is purpose-built for cultural heritage digitization workflows and is not a general-purpose document management or automation tool.
Frequently Asked Questions
What is Goobi used for?
Goobi is used by libraries, archives, museums, and other cultural heritage institutions to manage digitization workflows — including scanning, metadata creation, quality assurance, and publishing — and to display digital collections online.
Is Goobi free to use?
Yes, Goobi is fully open source and free to use. The source code is publicly available, and there are no licensing fees. However, institutions may choose to contract intranda GmbH for professional support, hosting (Goobi Cloud), or custom development.
What is the difference between Goobi workflow and Goobi viewer?
Goobi workflow is the back-end process management system that coordinates the digitization pipeline, while Goobi viewer is the front-end web presentation layer that makes digitized materials publicly accessible online.
What is Goobi-to-go?
Goobi-to-go is a portable, self-contained version of the Goobi platform that can be run without complex server setup, making it easy to try Goobi or use it in smaller or offline environments.
How can I get support for Goobi?
Support is available through the public community forum, official documentation, and Goobi Days events and workshops. Professional support and cloud hosting services are also offered by intranda GmbH.
