I hit reply and sent this to just David, but I think it should go to the whole list:
Hi David, I want to do 2 kinds of things with Solr.... Maybe 3 in the future 1. I want to use it on our website so that a customer can filter down products by different attributes. So suppose we have: Inventory --- ABC, 10 DEF, 15 s Attributes ---- ABC,Brand,ACME Brand ABC,Water Pump Style,Short DEF,Brand,Engine Builders DEF,Water Pump Style, Long Vehicle Applicatins ABC, 1999, Toyota, Camry, 3.1L ABC, 2000, Toyota, Camry, 3.1L DEF, 1997, Ford, Focus, 2.5L DEF, 1998, Ford, Focus, 2.5L I would like to be able to handle two things: 1. Give the person a list of all the unique years. When they pick one, show them all the Makes for that year. When they pick that, show all the Models. Alternatively: 1. Give them a list of makes, then models, then engine, etc... Also, it would be nice to if I could give Solr a Part#(Sku) and have it get all the attributes for that sku, alternatively, I'd love to be able to drill-down by the attributes such as Brand, Water Pump Style, etc. Please let me know if this email is still not clear... -- Vladimir Landman Northern Auto Parts ________________________________________ From: Smiley, David W. [mailto:dsmi...@mitre.org] Sent: 2009-08-19 10:42 AM To: solr; Vladimir Landman Subject: Re: Data Modeling This is the sort of Solr fundamentals question my book (chapter 2) will help you with. Think about what your user interface is. What are users searching for? That is, what exactly comes back from search results? It's not clear from your description what your search scenario is. ~ David Smiley Author: http://www.packtpub.com/solr-1-4-enterprise-search-server On 8/19/09 10:31 AM, "Vladimir Landman" <v...@northernautoparts.com> wrote: Hi, I am trying to create a schema for Solr. Here is a relational model of what our data might look like: Inventory ----------------- Sku Price Weight Attributes ----------------------- AttributeName AttributeValue Applications ---------------------- Id (Auto-Incrementing) Sku VehicleYear VehicleMake VehicleModel VehicleEngine There can be multiple Application(s) records. Also, Attributes can also have duplicates. Basically I want to store basic information about our inventory, attributes, and applications. If I didn't have the applications, I would simply have: <field name="id" ...> <field name="sku" ...> <field name="price" ...> <field name="weight" ...> <!-- Attributes --> <field name="OilPumpVolume" ...> <field name="FuelType" ...> Since one part might have 3 or 4 attributes, but 100 applications, I want to try to avoid having 400 records, but maybe that is just what I will have to do. I appreciate any help. -- Vladimir Landman Northern Auto Parts
