Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Grant Glass

dblp:440/7473 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
1since 2021 · last 2026
0000-0003-3867-1494ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 1 · 1 first-author · 1 since 2021

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Databases, data mining, and information retrieval
1 paper
Information retrieval · 100%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Information retrieval
query understanding
1.012026
What's in a Name? Product Normalization for Enterprise RAG at NetApp · SIGIR 2026
Information retrieval
retrieval-augmented generation
1.012026
What's in a Name? Product Normalization for Enterprise RAG at NetApp · SIGIR 2026
Information retrieval
retrieval models
1.012026
What's in a Name? Product Normalization for Enterprise RAG at NetApp · SIGIR 2026
Information retrieval › retrieval models › neural retrieval
dense retrieval
0.312026
What's in a Name? Product Normalization for Enterprise RAG at NetApp · SIGIR 2026

Methods — techniques the papers use, named apart from their topics

dense retrieval · 1.0NPMI log-mining · 1.0BM25 · 1.0
YearPublicationVenuePosition
2026 What's in a Name? Product Normalization for Enterprise RAG at NetApp
abstract
Retrieval-Augmented Generation (RAG) systems for enterprise technical documentation face a persistent vocabulary challenge: users refer to the same product by many different names, abbreviations, and legacy terms, while the underlying search index uses a controlled product taxonomy. This mismatch degrades retrieval precision and recall, ultimately reducing answer quality. I present DOC, the production conversational assistant deployed on docs.netapp.com, and describe two complementary techniques that leverage curated product-name knowledge artifacts to close this vocabulary gap. First, a query-time product-name normalizer rewrites user queries by mapping informal or ambiguous product mentions to their canonical names and appending the latest version identifiers. Second, a product-scope filter dynamically constructs structured filter expressions from a product catalogue, ensuring that retrieval is restricted to the set of documented products. Together, these lightweight, maintainable components yield measurable improvements in retrieval relevance without retraining any model. On a stratified sample of 300 real production queries from docs.netapp.com, with slug-derived ground-truth relevance judgments, curated normalization improves Mean Reciprocal Rank by +42%, +31%, and +24% over raw queries on BM25 and on two Azure dense retrievers (text-embedding-3-small and text-embedding-3-large ), all with non-overlapping 95% bootstrap CIs. A factorial ablation reveals that the Product-Scope Filter, when driven dynamically by the same detected products, contributes a complementary +25-78% MRR gain on top of every retriever/normalizer pair, and that the curated normalizer still out-performs a hyperparameter-tuned NPMI log-mining baseline trained on 93, 028 production query-URL pairs across both filter states. I share system design details, experimental results, and operational lessons from two years of production deployment spanning 60+ enterprise storage and cloud products.
Grant Glass
SIGIR1