Arranger integrates with your underlying Elasticsearch cluster to automatically generate a powerful search API based on your configured index mapping. It consists of two main modules, Arranger Server and Arranger Components.
Arranger Server is a GraphQL API that communicates with an Elasticsearch index. Arranger Server uses a consistent and custom filter notation called SQON. SQON is designed to be user-friendly, allowing humans to easily understand and create custom filters while being straightforward for software systems to interpret and process.
Arranger Components are interactive and configurable UI components specifically designed to display and query complex datasets from a web browser.
Arranger is a core service within the Overture research software ecosystem. See our related products for more information on how Overture helps organize data and enable discovery.
-
For development resources, including set up and technical details, see our Developer Documentation.
-
For more information on installation, configuration, and usage see our User Documentation.
To install Arranger using Docker, follow these steps:
- Clone the Arranger repository
- Navigate to the project directory
- With Docker running, execute the quickstart
maketarget:
make startThe deployed services will be accessible through the following ports:
| Service | Port |
|---|---|
| Arranger Server | localhost:5050/graphql |
| Elasticsearch | localhost:9200 |
| Kibana | localhost:5601 |
Note(s):
-
To generate the API Arranger requires an Elasticsearch Instance and an index mapping. For information on setting Arranger up with a default index mapping, see our official documentation page on supplying an index mapping.
-
Arranger is undergoing refactoring work for what will become version 3+. An upgrade guide is on its way. Current users of v2 may look at the
legacybranch, meanwhile, where we will continue fixing newly reported bugs until further notice. -
You may need to add the
--legacy-peer-depsflag when integrating our modules into your apps. Along with the rewrite, we're steadily updating the internal dependencies, so this isn't necessary.
- Filing an issue
- Making a contribution
- Connect with us on Slack
- Add or Upvote a feature request
Overture is an ecosystem of research software tools, each with narrow responsibilities, designed to reduce redundant programming efforts and enable developers and data scientists to build reliable systems that organize and share big data.
All our core microservices are included in the Overture Data Management System (DMS). The DMS offers turnkey installation, configuration, and deployment of Overture software. For more information on the DMS, read our DMS documentation.
See the links below for additional information on our other research software tools:
| Software | Description |
|---|---|
| Ego | An authorization and user management service |
| Ego UI | A UI for managing Ego authentication and authorization services |
| Score | Transfer data to and from any cloud-based storage system |
| Song | Catalog and manage metadata associated to file data spread across cloud storage systems |
| Maestro | Organizing your distributed data into a centralized Elasticsearch index |
| Arranger | A search API with reusable UI components that build into configurable and functional data portals |
| DMS-UI | A simple web browser UI that integrates Ego and Arranger |
Overture is supported by grant #U24CA253529 from the National Cancer Institute at the US National Institutes of Health, and additional funding from Genome Canada, the Canada Foundation for Innovation, the Canadian Institutes of Health Research, Canarie, and the Ontario Institute for Cancer Research.
