OHDSI / OHDSI/WebAPI

Add support for changing Solr Vocab core

Open
#2,287 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
151
Forks
183
Avg merge
14m
Merged PRs (30d)
2

Description

Expected behavior

If your Solr endpoint has multiple cores, we should be able to pick which one to use for searching. Much like the default vocabulary for the app and session are today.

Actual behavior

The first core is used only.

Steps to reproduce behavior

Set up a Solr endpoint and have WebAPI point to it. Have multiple omop vocab cores.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how WebAPI currently selects the first Solr vocabulary core when multiple OMOP vocabulary cores are configured. Confirm how the app and session vocabulary defaults are represented, then make the selected core configurable and verify that searches use it instead of always using the first core.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.