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
Implementation order: 05 of 11 category issues. 20/298 reviewed August zero-result events (6.7%).
A concrete retrieval path for patrons who already know the item or map series they want.
Dependencies: Reuse the shared suggestion/count interface in #396; this can proceed independently of geographic parsing. This sequence is a recommended work queue, not a requirement to close every earlier issue. See #396 for the complete order.
August 2026 completed top-100 zero-result review: Known map, title, citation, or creator accounts for 7 of 100 ranked query rows, representing 20 recorded zero-result searches. The September 10 export ranks all 885 distinct non-empty zero-result queries without a minimum-frequency cutoff; the top 100 represent 298 events. All 100 August queries are present and categorized, and monthly totals reconcile. These are recorded searches, not unique patrons; category assignments infer intent rather than prove failure causes.
Evidence: frontend/src/data/analytics/zeroResultQueries2026.json (exported September 10, 2026; August 1 inclusive–September 1 exclusive UTC). Ordering is count descending, then query using database collation, with case preserved. Full category inventory: docs/frontend/zero-result-query-review-2026-08.md in the working change. This issue contains its complete query evidence below.
Recognize likely map titles and pasted citations; propose extracted title, series, creator, or identifier searches with clear labels.
Handle punctuation, dates, and citation URLs without requiring every citation token to match metadata.
Use existing indexed identifiers and source links where available; distinguish an exact item match from related series or editions.
If the item is unavailable, offer related collections and a help path without promising holdings or an exact match.
Test full titles, plat-book titles, and a citation containing a source URL; preserve original input and make edits reversible.
Track suggestion impressions, acceptance, next-search nonzero results, and subsequent resource engagement using category/action aggregates; avoid collecting additional raw address or coordinate text. Distinguish lookup errors from genuine no-match outcomes.
Implementation context: frontend/src/components/search/NoResultsSearchHelp.tsx already offers keyword and Nominatim suggestions, but builds fresh search URLs that discard filters. frontend/src/__tests__/pages/SearchPage.test.tsx explicitly expects the location map to be hidden for zero results. Extend this existing experience and update focused behavior/accessibility tests. Related: #270 (zero-result analytics), #231 (Advanced Search location field).
Tracking: #396. Shared recovery, constraint preservation, and baseline validation are coordinated there. The top-100 evidence audit is complete.
Support creator/publisher names and partial non-English map titles as distinct candidate interpretations, preserving language and avoiding an exact-item claim without a match.
Implementation order: 05 of 11 category issues. 20/298 reviewed August zero-result events (6.7%).
A concrete retrieval path for patrons who already know the item or map series they want.
Dependencies: Reuse the shared suggestion/count interface in #396; this can proceed independently of geographic parsing. This sequence is a recommended work queue, not a requirement to close every earlier issue. See #396 for the complete order.
August 2026 completed top-100 zero-result review: Known map, title, citation, or creator accounts for 7 of 100 ranked query rows, representing 20 recorded zero-result searches. The September 10 export ranks all 885 distinct non-empty zero-result queries without a minimum-frequency cutoff; the top 100 represent 298 events. All 100 August queries are present and categorized, and monthly totals reconcile. These are recorded searches, not unique patrons; category assignments infer intent rather than prove failure causes.
Evidence:
frontend/src/data/analytics/zeroResultQueries2026.json(exported September 10, 2026; August 1 inclusive–September 1 exclusive UTC). Ordering is count descending, then query using database collation, with case preserved. Full category inventory:docs/frontend/zero-result-query-review-2026-08.mdin the working change. This issue contains its complete query evidence below.Interpretation notes:
Acceptance criteria:
Implementation context:
frontend/src/components/search/NoResultsSearchHelp.tsxalready offers keyword and Nominatim suggestions, but builds fresh search URLs that discard filters.frontend/src/__tests__/pages/SearchPage.test.tsxexplicitly expects the location map to be hidden for zero results. Extend this existing experience and update focused behavior/accessibility tests. Related: #270 (zero-result analytics), #231 (Advanced Search location field).Tracking: #396. Shared recovery, constraint preservation, and baseline validation are coordinated there. The top-100 evidence audit is complete.