After your Elasticsearch index mapping has been created and supplied, a project must be created in Arranger. The project will reference the mapping and allow an administrator to configure the search filters, result columns, and so on that need to be exposed to the front-end data portal.
There are several parts to this:
NOTE: Although multiple projects can be created and exist in the Arranger Admin UI, currently only ONE project can be actively in use by the front-end data portal at a time. Your UI application must specify in its interactions with Arranger (e.g. queries) which project to use.
When creating a new project, several JSON files need to be imported. They describe the metadata configurations for your project. These files need to be created in advance to reflect the fields in your index mapping that need to be configured within Arranger.
For reference, we provide a set of sample JSON files for the default file_centric_1.0
index here as a guide.
The required JSON files are:
File | Description |
---|---|
aggs-state.json | Configures the search filters and aggregations in the data portal's facet panel. |
columns-state.json | Configures the data columns in the data portal's search results table. |
extended.json | Extended (extra) configurations for your Elasticsearch index mapping. |
matchbox-state.json | Configures the quick search settings for specified fields in the data portal. |
For your own custom index mapping, you only need to replace the fields in the JSON files with the fields you wish to configure in Arranger. You do NOT need to supply the actual configuration values, since you can do that in the UI once they are imported. Just make sure the JSON files are in the correct format per the default example, but with the list of fields from your own mapping instead of the default ones.
To add a new project to the Arranger Admin UI, do the following:
localhost:8080
. The Admin UI is displayed with no projects listed:snake_case
and dashes (-
) are not allowed. If you are using the default sample index, you can simply enter file
.file
.index_config.json
file. If you are using the default sample index, then enter file_centric_1.0
.aggs-state.json
columns-state.json
extended.json
matchbox-state.json
For details on how to configure the project metadata, see the relevant sections in the User Guide:
Once Arranger is completely configured, you will need to index actual data into Elasticsearch so that it can be explored in your data portal.
If you are using Arranger with the full Overture product suite, you can learn how to upload and index data with our DMS platform bundle here.
However, if you are using Arranger and Elasticsearch standalone without other Overture components, you will need to index the data into ES yourself. See the Elastic documentation for guidance.