A library open-data RAG allows cross-collection search that mixes youth-services records with general catalog FAQs. What segregation control is needed?
Select an answer to reveal the explanation.
Short Explanation
Youth records and catalog FAQs don't belong in the same search blender. Keep sensitive collections walled off so a casual FAQ query can't pull a restricted youth file into context.
Full Explanation
Segregating sensitive youth-services collections so vector search cannot cross into general FAQ retrieval is the required control. Cross-collection search that mixes youth-services records with catalog FAQs allows a general library query to pull restricted youth-related content into context. Collection-level segregation, with FAQ clients bound only to public catalog indexes, restores purpose limitation and confidentiality expected for youth services in a municipal library setting.
Merging all library collections into one index to maximize recall fails by concept: recall without isolation maximizes leakage of sensitive youth records into casual FAQ answers. Publishing youth records publicly so isolation is unnecessary fails by expanding disclosure contrary to privacy and program rules. Claiming BM25 keyword search cannot mix collections fails because keyword search across a merged or federated corpus can still return youth documents when terms overlap; the retrieval mode does not create segregation by itself.
Exam caveat: Sensitive municipal program data (youth, health, housing) needs collection isolation even inside one “library RAG” product. Maximize-recall merges are an anti-pattern for mixed sensitivity.
Operational check: Split youth-services embeddings into a restricted collection, remove them from the open FAQ search scope, run FAQ queries with youth-program keywords and confirm no restricted hits, and review librarian role permissions for the sensitive index separately.