alexmarquardt
So I built two small OSS pipelines that convert open product sources into a clean, stable NDJSON schema you can bulk-index into Elasticsearch/OpenSearch. One outputs ~100K grocery products (Open Food Facts) and the other ~1M electronics-style products (Open Icecat), with strict “no image = no entry” quality gates and a shared schema contract.
Would love feedback on: • what fields you consider essential for a convincing search/relevance demo dataset • whether the schema choices (flat attrs for faceting + searchable description) match what you’ve seen work in practice
Additive vs. multiplicative boosting for business signals in BM25 ranking
Ranking by Profit and Popularity in Elasticsearch
Ecommerce: You don't need ML to do personalization
One Does Not Simply “Create a Visualization” from Unstructured Data
When I worked as a database consultant, I often saw conversations similar to the following at clients:Manager: Hey Data Analyst! We have a huge amount of data in our data lake, and I would like you to use it to provide us with some analysis and visualizations. Could you get that to me next week?Data Analyst: Not really. The data that we have in the data lake is unstructured, and I can't do much...