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  October 2013

CODE4LIB October 2013

Subject:

Re: ANNOUNCEMENT: Traject MARC->Solr indexer release

From:

Tom Cramer <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 15 Oct 2013 15:27:43 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (112 lines)

Jonathan, Bill, 

Very interesting--thanks for the replies. While I'm not sure I understand what indexing arbitrary XML into solr might look like, this does prompt me to think it would be interesting to look at Trajecting up some EAD (may I use it as a verb?) into solr, for finding aid searchability. It is my impression that most of the effort in making finding aids searchable is in the indexing, and I'm not aware of a general purpose tool / approach for those of us using solr yet, though there have been plenty of successful approaches at individual sites. (Happy to have my ignorance rectified.)

Mike Giarlo is organizing a DLF hackfest for ArchivesSpace / Hydra integration. I wonder if Traject for EAD might be touched on there? 

- Tom



On Oct 15, 2013, at 10:28 AM, Jonathan Rochkind wrote:

> Yep, what Bill said, I have had thoughts of extending it to other types of input too, it was part of my original design goals.
> 
> In particular, I was thinking of extending it to arbitrary XML.
> 
> Unlike MARC, there are many other options for indexing XML into Solr (assuming that's your end goal), so you may or may not find traject to be better than those, although for myself there might be some benefit in using the same tool accross formats too.
> 
> There are a number of built-in 'macros' that are MARC-specific; you wouldn't use those. And might need some others that are, say, XML-specific. (Probably just a single one, extract_xpath, for XML).
> 
> Same could be done for MODS, sure -- or you could handle MODS with a (hypothetical) generic XML setup.
> 
> But yeah, if you want to take input records, and transform them into hash-like data structures -- I was thinking from the start of structuring traject to support such use cases, yep. (If you want to go to something other than a hash-like data structure, well, it might still be possible, but it's straying from traject's target a bit more).
> 
> [Oh, and I just made up 'traject'. I was looking for a word (made up or real) not already being used for any popular software, and thinking about 'projections' in the sense of mathematical transformations; and about 'trajectory' in the sense of things sent through outer space, with the Solr/Solar connection. I actually had originally decided to call it "transject", but then accidentally wrote "traject" when I created the github project, and then figured that was easier to pronounce and write anyhow.]
> 
> On 10/15/13 1:02 PM, Bill Dueber wrote:
>> 'traject' means "to transmit" (e.g., "trajectory") -- or at least it did,
>> when people still used it, which they don't.
>> 
>> The traject workflow is incredibly general: *a reader* sends *a record* to *an
>> indexing routine* which stuffs...stuff...into a context object which is
>> then sent to *a writer*. We have a few different MARC readers, a few useful
>> writers (one of which, obviously, is the solr writer), and a bunch of
>> shipped routines (which we're calling "macros" but are just well-formed
>> ruby lambda or blocks) for extracting and transforming common MARC data.
>> 
>> [see
>> http://robotlibrarian.billdueber.com/announcing-traject-indexing-software/for
>> more explanation and some examples]
>> 
>> But there's no reason why a reader couldn't produce a MODS record which
>> would then be worked on. I'm already imagining readers and writers that
>> target databases (RDBMS or NoSQL), or a queueing system like Hornet, etc.
>> 
>> If there are people at Stanford that want to talk about how (easy it is) to
>> extend traject, I'd be happy to have that conversation.
>> 
>> 
>> 
>> On Tue, Oct 15, 2013 at 12:28 PM, Tom Cramer <[log in to unmask]> wrote:
>> 
>>> ++ Jonathan and Bill.
>>> 
>>> 1.) Do you have any thoughts on extending traject to index other types of
>>> data--say MODS--into solr, in the future?
>>> 
>>> 2.) What's the etymology of 'traject'?
>>> 
>>> - Tom
>>> 
>>> 
>>> On Oct 14, 2013, at 8:53 AM, Jonathan Rochkind wrote:
>>> 
>>>> Jonathan Rochkind (Johns Hopkins) and Bill Dueber (University of
>>> Michigan), are happy to announce a robust, feature-complete beta release of
>>> "traject," a tool for indexing MARC data to Solr.
>>>> 
>>>> traject, in the vein of solrmarc, allows you to define your indexing
>>> rules using simple macro and translation files. However, traject runs under
>>> JRuby and is "ruby all the way down," so you can easily provide additional
>>> logic by simply requiring ruby files.
>>>> 
>>>> There's a sample configuration file to give you a feel for traject[1].
>>>> 
>>>> You can view the code[2] on github, and easily install it as a (jruby)
>>> gem using "gem install traject".
>>>> 
>>>> traject is in a beta release hoping for feedback from more testers prior
>>> to a 1.0.0 release, but it is already being used in production to generate
>>> the HathiTrust (metadata-lookup) Catalog (http://www.hathitrust.org/).
>>> traject was developed using a test-driven approach and has undergone both
>>> continuous integration and an extensive benchmarking/profiling period to
>>> keep it fast. It is also well covered by high-quality documentation.
>>>> 
>>>> Feedback is very welcome on all aspects of traject including
>>> documentation, ease of getting started, features, any problems you have,
>>> etc.
>>>> 
>>>> What we think makes traject great:
>>>> 
>>>> * It's all just well-crafted and documented ruby code; easy to program,
>>> easy to read, easy to modify (the whole code base is only 6400 lines of
>>> code, more than a third of which is tests)
>>>> * Fast. Traject by default indexes using multiple threads, so you can
>>> use all your cores!
>>>> * Decoupled from specific readers/writers, so you can use ruby-marc or
>>> marc4j to read, and write to solr, a debug file, or anywhere else you'd
>>> like with little extra code.
>>>> * Designed so it's easy to test your own code and distribute it as a gem
>>>> 
>>>> We're hoping to build up an ecosystem around traject and encourage
>>> people to ask questions and contribute code (either directly to the project
>>> or via releasing plug-in gems).
>>>> 
>>>> [1]
>>> https://github.com/traject-project/traject/blob/master/test/test_support/demo_config.rb
>>>> [2] http://github.com/traject-project/traject
>>> 
>> 
>> 
>> 

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

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