Repository navigation
Mapper: offer Custom Match Algorithm without the OCL Online API #2966
Description
The open OCL Mapper has all the code a custom matching algorithm needs: the API URL and token fields in MultiAlgoSelector.jsx, and the batched POST in MapProject.jsx, whose request and response follow $match. But the Mapper only lists Custom Match Algorithm when the algorithm catalog at OCL_ONLINE_API_URL (/match-algorithms/) serves it. A Mapper built without OCL_ONLINE_API_URL offers only OCL Search and OCL Semantic.
Add Custom Match Algorithm to the built-in algorithms (useAlgos in src/components/map-projects/algorithms.jsx), so every build offers it. The catalog can still override it: MapProject.jsx already merges catalog entries over built-in ones by id and type (custom, custom).
Acceptance criteria
- With no
OCL_ONLINE_API_URL, the Matching Algorithm picker lists Custom Match Algorithm, and AutoMatch runs with it. - With the catalog configured, the picker lists it once.
- Its name and description come from locale strings, like OCL Search and OCL Semantic.
Context: the Matching Algorithms page in OCL Docs (#2817, OpenConceptLab/ocl-docs#75) documents Custom Match Algorithm as part of the open Mapper.
Activity
OpenConceptLab/ocl_issues#2817 | Matching Algorithms: open Mapper fir…
ocl-automation commentedon Oct 26, 2026
Automated Triage — 2026-10-26
Decision:
decision/ai-readyType:
type/bugSignals:
signal/quick-win,signal/low-risk,signal/small-scope,signal/well-specifiedThe issue names the file (
useAlgosinalgorithms.jsx), the merge behaviour already inMapProject.jsx, and three testable acceptance criteria, so it is a small change plus locale strings. It is labelled type/bug, but it asks for a built-in algorithm to be offered in every build, so I classed it as a feature. The linked docs work (#2817, ocl-docs#75, #2816) is closed and does not block it. [Type: LLM suggested 'feature' but keeping human-applied 'bug'.]Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5.5 (openrouter).
snyaggarwal commentedon Oct 27, 2026
@paynejd We should discuss this before picking this up