You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mapper: choose the latest release by default, and mark which versions support semantic search #2906
Part of OpenConceptLab/ocl_online#464 (critical user journey 1).
After you choose a target repository, Version stays empty and turns red at once ("Select a target repository version before saving"). The options are bare IDs (for LOINC: 2.81, 2.71.21AA, 2.70.21AA, HEAD), with no dates, no "latest" mark, and no sign that only 2.81 supports the OCL Semantic Algorithm.
Acceptance criteria
Choosing a repository fills Version with the latest released version that supports semantic search, else the latest release, else HEAD.
Each option shows its release date and badges for "Latest" and "Semantic search" (the version's match_algorithms includes llm).
No error state until someone tries to save without a version.
An existing project's saved version never changes.
The body lists four testable acceptance criteria and names the components to change (MapProject.jsx, RepoVersionSearchAutocomplete.jsx, ConfigurationForm.jsx). The work is moderate: default-version selection logic, release-date and badge display, and deferring the error state. It stays within the Mapper UI and relies on the existing versions/?verbose=true API and match_algorithms field. Risk is low because it is UI-only, as long as saved project versions are left unchanged (the last criterion).
Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5.5 (openrouter).
Choosing a Mapper target repository now fills Version with its latest semantic-search release (else its latest release, else HEAD); options show release dates and Latest and Semantic search badges; Version turns red only after a save without one; saved projects keep their version.
Activity
ocl-automation commentedon Oct 13, 2026
Automated Triage — 2026-10-13
Decision:
decision/ai-readyType:
type/featureSignals:
signal/low-risk,signal/well-specifiedThe body lists four testable acceptance criteria and names the components to change (MapProject.jsx, RepoVersionSearchAutocomplete.jsx, ConfigurationForm.jsx). The work is moderate: default-version selection logic, release-date and badge display, and deferring the error state. It stays within the Mapper UI and relies on the existing
versions/?verbose=trueAPI andmatch_algorithmsfield. Risk is low because it is UI-only, as long as saved project versions are left unchanged (the last criterion).Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5.5 (openrouter).
closes OpenConceptLab/ocl_issues#2906 | Reuse the llm check, and let …
paynejd commentedon Oct 14, 2026
Octoad's session worker opened OpenConceptLab/oclmap#101 for this ticket. It's ready for review.
Choosing a Mapper target repository now fills Version with its latest semantic-search release (else its latest release, else HEAD); options show release dates and Latest and Semantic search badges; Version turns red only after a save without one; saved projects keep their version.
Codex review passes: 1. Session worker
worker-v0.11, recipelean-loop, flowpublic>public. Runopenconceptlab-ocl-issues-2906-20261014-120733, sessionocl-issu-2906-1014-120733-a1e263.Merge pull request #101 from OpenConceptLab/OpenConceptLab/ocl_issues…
OpenConceptLab/ocl_issues#2906 | Start a new target on its latest sem…