Serve a text search endpoint with provenance-aware results #70

New issue

Open

opened 2026-07-01 00:59:51 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:59:51 +00:00

(Migrated from github.com)

Problem

Clients need to search liturgical text and jump to the matching office/hour/day. A search endpoint must query the index and return results that respect language and provenance constraints.

Acceptance criteria

An endpoint accepts a query (and language/scope filters) and returns ranked matches.
Each result links to the addressable response and carries provenance.
Empty and malformed queries return clear, canonical responses.
Search is covered by tests for hits, misses, and filtering.

Notes

Results must never expose text lacking provenance.

## Problem Clients need to search liturgical text and jump to the matching office/hour/day. A search endpoint must query the index and return results that respect language and provenance constraints. ## Acceptance criteria - [ ] An endpoint accepts a query (and language/scope filters) and returns ranked matches. - [ ] Each result links to the addressable response and carries provenance. - [ ] Empty and malformed queries return clear, canonical responses. - [ ] Search is covered by tests for hits, misses, and filtering. ## Notes Results must never expose text lacking provenance.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Api#70

No description provided.

Rows
Columns