Yep that making sense. But I was afraid it was the only solution. Since I finished to wrote my email I started to create a php script to create the same file but compatible with Solr.
thx for your quick answer ;) On Tue, Jul 7, 2009 at 4:40 PM, Matt Mitchell <goodie...@gmail.com> wrote: > Saeli, > > Solr expects a certain XML structure when adding documents. You'll need to > come up with a mapping, that translates the original structure to one that > solr understands. You can then search solr and get those solr documents > back. If you want to keep the original XML, you can store it in a field > within the solr document. > > original data -> mapping -> solr XML document (with a field for the > original > data) > > Does that make sense? Can you describe what it is you want to do with > results of a search? > > Matt > > On Tue, Jul 7, 2009 at 10:25 AM, Saeli Mathieu <saeli.math...@gmail.com > >wrote: > > > Hello. > > > > I'm a new user of Solr, I already used Lucene to index files and search. > > But my programme was too slow, it's why I was looking for another > solution, > > and I thought I found it. > > > > I said I thought because I don't know if it's possible to use solar with > > this kind of XML files. > > > > <lom xsi:schemaLocation="http://ltsc.ieee.org/xsd/lomv1.0 > > http://ltsc.ieee.org/xsd/lomv1.0/lom.xsd";> > > <general> > > <identifier> > > <catalog>STRING HERE</catalog> > > <entry> > > STRING HERE > > </entry> > > </identifier> > > <title> > > <string language="fr"> > > STRING HERE > > </string> > > </title> > > <language>fr</language> > > <description> > > <string language="fr"> > > STRING HERE > > </string> > > </description> > > </general> > > <lifeCycle> > > <status> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </status> > > <contribute> > > <role> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </role> > > <entity>STRING HERE > > </entity> > > </contribute> > > </lifeCycle> > > <metaMetadata> > > <identifier> > > <catalog>STRING HERE</catalog> > > <entry>STRING HERE</entry> > > </identifier> > > <contribute> > > <role> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </role> > > <entity>STRING HERE > > </entity> > > <date> > > <dateTime>STRING HERE</dateTime> > > </date> > > </contribute> > > <contribute> > > <role> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </role> > > <entity>STRING HERE > > </entity> > > <entity>STRING HERE</entity> > > <entity>STRING HERE > > </entity> > > <date> > > <dateTime>STRING HERE</dateTime> > > </date> > > </contribute> > > <metadataSchema>STRING HERE</metadataSchema> > > <language>STRING HERE</language> > > </metaMetadata> > > <technical> > > <location>STRING HERE > > </location> > > </technical> > > <educational> > > <intendedEndUserRole> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </intendedEndUserRole> > > <context> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </context> > > <typicalAgeRange> > > <string language="fr">STRING HERE</string> > > </typicalAgeRange> > > <description> > > <string language="fr">STRING HERE</string> > > </description> > > <description> > > <string language="fr">STRING HERE</string> > > </description> > > <language>STRING HERE</language> > > </educational> > > <annotation> > > <entity>STRING HERE > > </entity> > > <date> > > <dateTime>STRING HERE</dateTime> > > </date> > > </annotation> > > <classification> > > <purpose> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </purpose> > > </classification> > > <classification> > > <purpose> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </purpose> > > <taxonPath> > > <source> > > <string language="fr">STRING HERE</string> > > </source> > > <taxon> > > <id>STRING HERE</id> > > <entry> > > <string language="fr">STRING HERE</string> > > </entry> > > </taxon> > > </taxonPath> > > </classification> > > <classification> > > <purpose> > > <source>STRING HERE</source> > > <value>STRING HERE</value> > > </purpose> > > <taxonPath> > > <source> > > <string language="fr">STRING HERE </string> > > </source> > > <taxon> > > <id>STRING HERE</id> > > <entry> > > <string language="fr">STRING HERE</string> > > </entry> > > </taxon> > > </taxonPath> > > <taxonPath> > > <source> > > <string language="fr">STRING HERE</string> > > </source> > > <taxon> > > <id>STRING HERE</id> > > <entry> > > <string language="fr">STRING HERE</string> > > </entry> > > </taxon> > > </taxonPath> > > </classification> > > </lom> > > > > I don't know how I can use this kind of file with Solr because the XML > > example are this one. > > > > <add> > > <doc> > > <field name="id">SOLR1000</field> > > <field name="name">Solr, the Enterprise Search Server</field> > > <field name="manu">Apache Software Foundation</field> > > <field name="cat">software</field> > > <field name="cat">search</field> > > <field name="features">Advanced Full-Text Search Capabilities using > > Lucene</field> > > <field name="features">Optimized for High Volume Web Traffic</field> > > <field name="features">Standards Based Open Interfaces - XML and > > HTTP</field> > > <field name="features">Comprehensive HTML Administration > > Interfaces</field> > > <field name="features">Scalability - Efficient Replication to other Solr > > Search Servers</field> > > <field name="features">Flexible and Adaptable with XML configuration and > > Schema</field> > > <field name="features">Good unicode support: héllo (hello with an > > accent over the e)</field> > > <field name="price">0</field> > > <field name="popularity">10</field> > > <field name="inStock">true</field> > > <field name="incubationdate_dt">2006-01-17T00:00:00.000Z</field> > > </doc> > > </add> > > > > I understood Solr need this kind of architecture, by Architecture I mean > > <field + name="keyword">Value</field> > > or as you can see I can't use this kind of architecture because I'm not > > allow to change my XML files. > > > > I'm looking forward to read you. > > > > Mathieu Saeli > > -- > > Saeli Mathieu. > > > -- Saeli Mathieu.
