Skip to main content

What Overture is made of

Eight components, grouped by what they do. Take one where you have a gap, or the whole stack as a platform.

ComponentWhat it doesDocumentationUsed by
CollectGetting data in and keeping it describable. A dictionary defines what the platform accepts, and the submission, metadata and transfer services hold you to it.
ComponentWhat it doesDocumentationUsed by
Dictionary ManagerLectern
Defines and version-tracks the data dictionaries a platform validates submissions against.Documentation4 deployments
Tabular SubmissionLyric
Validates and commits tabular submissions against a dictionary, keeping every change auditable.Documentation2 deployments
File ManagerSong
Catalogs file metadata across repositories, assigning global identifiers and controlling what gets published.Documentation3 deployments
File TransferScore
Moves large files to and from cloud storage, with resumable transfers and BAM/CRAM slicing.Documentation3 deployments
ExploreMaking what you collected findable. Distributed metadata becomes one index, the index becomes a search API, and the API becomes a portal people can use.
ComponentWhat it doesDocumentationUsed by
Indexing ServiceMaestro
Indexes metadata from File Manager and Tabular Submission repositories into one searchable index.Documentation2 deployments
SearchArranger
Builds a search API and matching UI components from any Elasticsearch or OpenSearch index.Documentation7 deployments
Portal UIStage
A React framework for a data portal's front end, themed and extended per deployment.Documentation4 deployments
ControlAccess and authorization sit around both groups rather than inside them. Every component delegates to Keycloak, so a deployment applies its own institution's identity rules across the whole stack, and an Overture provider extension adds API keys for command line and programmatic access.Configuring access and authorization
ComponentWhat it doesDocumentationUsed by
TBD
In development: an authorization service that works with Keycloak, so administrators can define their data access policy declaratively, in common spoken language, across every Overture component.GitHub repository2 deployments