LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2007

CODE4LIB January 2007

Subject:

Re: Solr indexing -- why XSL is the wrong choice

From:

Andrew Nagy <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 19 Jan 2007 17:35:50 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (77 lines)

Casey, we have had great successes with XSL for MARCXML to SOLR, so I
can't agree to everything you are saying.  However I anxiously await
your presentation on your successes with SOLR so you can persuade me to
the dark side :)

Casey Durfee wrote:
>
> I think there are many good reasons why XSLT is absolutely the wrong tool for the job of indexing MARC records for Solr.
>
> 1) Performance/Speed: In my experience even just transforming from MARCXML to MODS takes a second or two (using the LoC stylesheet), due to the stylesheet's complexity and inefficiency of doing heavy-duty string manipulation in XSL.  That means you're looking at an indexing speed of around 1 record/second.  If you've got 1,000,000 bib records, it'll take a couple of weeks just to index your data.  For comparison, the indexer of our commercial OPAC does about 50 records per second (~6 hours for a million records) and the one I've written in Jython (by no means the fastest language out there) that doesn't use XSL can do about 150 records a second (about 2 hours for 1 million records).
>
I can transform 500,000 records from marcxml to solrxml in about 4
hours.  Then about 2 hours for importing to SOLR.
Considering time is NOT truly a factor, I think at this point it is
totally based on developer preference (assuming your XSLT process is not
2 weeks long).  Once you have your records in SOLR, you are all set.
You only need to re-run your transformation on a periodic basis to catch
records that change.  In our instance that might only be 5 - 10 records
per day.
>
> 2) Reusability:  What if you want to change how a field is indexed?  You would have to edit the XSLT directly (or have the XSL stylesheet automatically generated based on settings stored elsewhere).
>
> a) Users of the indexer shouldn't have to actually mess with programming logic to change how it indexes.  You shouldn't have to know a thing about programming to change the setup of an index.
>
> b) It should be easy for an external application to know how your indexes have been built.  This would be very difficult with an XSL stylesheet.  Burying configuration inside of programming logic is a bad idea.
>
> c) The Solr schema should be automatically generated from your index setup so all your index configuration is in one place.  I guess you could write *another* XSL stylesheet that would transform your indexing stylesheet into the Solr schema file, but that seems ridiculous.
>
> d) Automatic code generation is evil.  Blanchard's law: "Systems that require code generation lack sufficient power to tackle the problem at hand."  If you find yourself considering automatic code generation, you should instead be considering a more dynamic programming language.
>
I agree with your argument of abstracting your programming from your
data so that a non-tech-savvy librarian could modify the solr settings.
But if you modify the solr settings, you need to (at this point)
reimport all of your data which mean that you either have to change your
XSLT or your transformation application.  I personally feel that a
less-tech savvy individual can pickup XSLT easier than coding java.
Maybe I am understanding you incorrectly though.
>
> 3) Ease of programming.
>
> a) Heavy-duty string manipulation is a pain in pure XSLT.  To index MARC records have to do normalization on dates and names and you probably want to do some translation between MARC codes and their meanings (for the audience & language codes, for instance).  Is it doable?  Yes, especially if you use XSL extension functions.  But if you're going to have huge chunks of your logic buried in extension functions, why not go whole hog and do it all outside of XSLT, instead of having half your programming logic in an extension function and half in the XSLT itself?
>
I can see your argument for this, however I like to abstract my layers
of applications as mentioned above.  So in this aspect, I have a script
the runs the XSLT.  Inside the script is also some logic that the XSLT
refers back to for the manipulation and massaging of the data.  I can
keep all XML related transformation logic in my XSL and all of my coding
logic in my script.  Again, I think it boils down to preference.
>
> b) Using XSLT makes object-oriented programming with your data harder.
That's a bold statement.
>   Your indexer should be able to give you a nice object representation of a record (so you can use that object representation within other code).  If you go the XSLT route, you'd have to parse the MARC record, transform it to your Solr record XML format, then parse that XML and map the XML to an object.  If you avoid XSLT, you just parse the MARC record and transform it to an object programmatically (with the object having a method to print itself out as a Solr XML record).
>
> Honestly, all this talk of using XSLT for indexing MARC records reminds me of that guy who rode across the United States on a riding lawnmower.  I am looking forward to there being a standard, well-tested MARC record indexer for Solr (and would be excited to contribute to such a project), but I don't think that XSL is the right tool to use.
>
I can agree with your OO style of design in which you have one Record
object that is responsible for all of the work (converting to solr, and
back again) but again, this all seems to be based on preference.
I have an import script that is completely independent of our SOLR
libraries.  I have a main SOLR class that is responsible for interacting
with SOLR and as well creating Record objects (using XSLT of course).

Also, I am sure there are plenty of folks attending the SOLR
preconference who are not experienced software developers and may have
an easier time developing some XSLT stylesheets -- and an even easier
time if we come up with a standard xslt doc for marcxml -> solr -- than
learning how to do what you are describing so they can create a nice
search engine for their catalog.

I feel that your arguments for not using XSLT are based on preference
and do not lend toward a "better" design at this point.

But I love to be proved wrong ... Im currently finishing up my masters
in Computer Science/Software Engineering  ... so I love these kinds of
debates since they are all thats on my head at the moment.

Andrew

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager