View on GitHub

RESO Unique Licensee Identifier

Unique Licensee Matching and Resolution Service

Running the ULI Pilot Service

This repository contains the following items:

1. Preparing ULI Pilot Data for Ingest

The rest of the steps in this README are optional, but to participate in the ULI Pilot there needs to be an initial seed file created from the Member and Office data in the organization at that time.

A Template Spreadsheet has been provided for your convenience.

Please fill in the fields on the “Merged” tab of the spreadsheet and send the sheet to RESO Development. Feel free to reach out with any additional questions.

For those who are running the server locally, please proceed to the next step after filling their data into the Merged sheet.

2. Starting the Elastic Backend

Make sure you have Docker and Docker Compose installed. The Windows and MacOs installers bundle them both together. The referenced guide has instructions for how to get started with both.

Once Docker Compose is installed, change into the directory where you downloaded this source code and type the following command with the Docker service running:

  docker-compose up

This will build containers with the backend environment for you locally the first time it’s run, or if the containers are ever removed. You will see a lot of output in your console during this time.

The containers that are built will maintain the state of their data beyond a restart.

3. Ingesting Data into the Elastic Backend

Once the sheet has been filled in (step 1) and the server is running, you can use the uli-pilot-pipeline.txt file to create an ingest pipeline for your data.

If you are not familiar with Ingest Pipelines, as a shortcut, you can also use the following method to import up to 100MB of csv data and create your own Elastic index.

First, navigate to the local instance of Kibana and look for the following: upload-a-file

From there, you will be taken to the File Data Visualizer, which will allow you to upload the .csv version of the Excel spreadsheet template from step (1). See this article for more information.

If using this method, the ingest pattern you create will match what’s in the uli-pilot-pipeline.txt file and will be created in the following location in your local Elastic installation if you name it uli-pilot-pipeline.

If you are using the provided template spreadsheet, the items created will match what’s in this example as well as the queries. Make sure to name your index uli-pilot when ingesting data to match the samples.

4. Querying the Pilot Data

After you have ingested the data, you can query the server using Kibana’s Dev Tools. These will connect to the local Elastic instance, and provides a convenient place to try out queries.

In this case, you’ll want to use something similar to the query that’s posted in the ULI Pilot search endpoint:


After adjusting the query for your data set, press the “play” button to see results.