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  February 2016

CODE4LIB February 2016

Subject:

Re: searching metadata vs searching content

From:

"Levy, Michael" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 8 Feb 2016 09:14:00 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (190 lines)

I find that in addition to methods of managing, manipulating and searching
rich, complex, hierarchically organized metadata, there are also great
challenges in developing an effective user interface(s).  How to help users
interpret search results that may result from hits in metadata at the
entire collection level, and/or from the component/subcomponent level,
and/or that relate to a single page, and how to do that effectively for
results in a small (e.g. single-folder) or very large, complex archival
collection? In my estimation, the UX/UI issues seem at least as challenging
as the metadata/search issues. I'm sure there is community interest along
all these lines. (Is there any progress within the ArcLight project?)

On Fri, Feb 5, 2016 at 4:10 PM, Laura Buchholz <[log in to unmask]>
wrote:

> Thanks, everyone! It is always nice to hear what others do, even if it
> doesn't end up being what works for us.
>
> On Thu, Jan 28, 2016 at 4:06 AM, Owen Stephens <[log in to unmask]> wrote:
>
> > To share the practice from a project I work on - the Jisc Historical
> Texts
> > platform[1] which provides searching across digitised texts from the 16th
> > to 19th centuries. In this case we had the option to build the search
> > application from scratch, rather than using a product such as ContentDM
> > etc. I should say that all the technical work was done by K-Int [2] and
> > Gooii [3], I was there to advise on metadata and user requirements, and
> so
> > the following is based on my understanding of how the system works, and
> any
> > errors are down to me :)
> >
> > There are currently three major collections within the Historical Texts
> > platform, with different data sources behind each one. In general the
> data
> > we have for each collection consists of MARC metadata records, full text
> in
> > XML documents (either from transcription or from OCR processes) and image
> > files of the pages.
> >
> > The platform is build using the ElasticSearch [4] (ES) indexing software
> > (as with Solr this is built on top of Lucene).
> >
> > We structure the data we index in ES in two layers - the ‘publication’
> > record, which is essentially where all the MARC metadata lives (although
> > not as MARC - we transform this to an internal scheme), and the ‘page’
> > records - one record per page in the item. The text content lives in the
> > page record, along with links to the image files for the page. The ‘page’
> > records are all what ES calls ‘child’ records of the relevant publication
> > record. We make this relationship through shared IDs in the MARC records
> > and the XML fulltext documents.
> >
> > We create a whole range of indexes from this data. Obviously field
> > specific searchs like title or author only search the relevant metadata
> > fields. But we also have a (default) ’search all’ option which searches
> > through all the metadata and fulltext. If the user wants to search the
> text
> > only, they check an option and we limit the search to only text from
> > records of the ‘page’ type.
> >
> > The results the user gets initially are always the publication level
> > records - so essentially your results list is a list of books. For each
> > result you can view ‘matches in text’ which shows snippets of where your
> > search term appears in the fulltext. You can then either click to view
> the
> > whole book, or click the relevant page from the list of snippets. When
> you
> > view the book, the software retrieves all the ‘page’ records for the
> book,
> > and from the page records can retrieve the image files. When the user
> goes
> > to the book viewer, we also carry over the search terms from their
> search,
> > so they can see the same text snippets of where the terms appear
> alongside
> > the book viewer - so the user can navigate to the pages which contain the
> > search terms easily.
> >
> > For more on the ES indexing side of this, Rob Tice from Knowledge
> > Integration did a talk about the use of ES in this context at the London
> > Elasticsearch usergroup [5]. Unfortunately the interface itself requires
> a
> > login, but if you want to get a feel for how this all works in the UI,
> > there is also a screencast which gives an overview of the UI available
> [6].
> >
> > Best wishes,
> >
> > Owen
> >
> > 1. https://historicaltexts.jisc.ac.uk
> > 2. http://www.k-int.com
> > 3. http://www.gooii.com
> > 4. https://www.elastic.co
> > 5.
> >
> http://www.k-int.com/Rob-Tice-Elastic-London-complex-modelling-of-rich-text-data-in-Elasticsearch
> > 6. http://historicaltexts.jisc.ac.uk/support
> >
> > Owen Stephens
> > Owen Stephens Consulting
> > Web: http://www.ostephens.com
> > Email: [log in to unmask]
> > Telephone: 0121 288 6936
> >
> > > On 27 Jan 2016, at 00:30, Laura Buchholz <[log in to unmask]>
> > wrote:
> > >
> > > Hi all,
> > >
> > > I'm trying to understand how digital library systems work when there
> is a
> > > need to search both metadata and item text content (plain text/full
> > text),
> > > and when the item is made up of more than one file (so, think a
> digitized
> > > multi-page yearbook or newspaper). I'm not looking for answers to a
> > > specific problem, really, just looking to know what is the current
> state
> > of
> > > community practice.
> > >
> > > In our current system (ContentDM), the "full text" of something lives
> in
> > > the metadata record, so it is indexed and searched along with the
> > metadata,
> > > and essentially treated as if it were metadata. (Correct?). This causes
> > > problems in advanced searching and muddies the relationship between
> what
> > is
> > > typically a descriptive metadata record and the file that is associated
> > > with the record. It doesn't seem like a great model for the average
> > digital
> > > library. True? I know the answer is "it depends", but humor me... :)
> > >
> > > If it isn't great, and there are better models, what are they? I was
> > taught
> > > METS in school, and based on that, I'd approach the metadata in a METS
> or
> > > METS-like fashion. But I'm unclear on the steps from having a bunch of
> > METS
> > > records that include descriptive metadata and pointers to text files of
> > the
> > > OCR (we don't, but if we did...) to indexing and providing results to
> > > users. I think another way of phrasing this question might be: how is
> the
> > > full text of a compound object (in the sense of a digitized yearbook or
> > > similar) typically indexed?
> > >
> > > The user requirements for this situation are essentially:
> > > 1. User can search for something and get a list of results. If
> something
> > > (let's say a pamphlet) appears in results based on a hit in full text,
> > the
> > > user selects the pamphlet which opens to the file (or page of the
> > pamphlet)
> > > that contains the text that was matched. This is pretty normal and does
> > > work in our current system.
> > > 2. In an advanced search, a user might search for a name in the
> "author"
> > > field and a phrase in the "full text" field, and say they want both
> > > conditions to be fulfilled. In our current system, this won't provide
> > > results when it should, because the full text content is in one record
> > and
> > > the author's name is in another record, so the AND condition can't be
> > met.
> > > 3. Librarians can link description metadata records (DC in our case) to
> > > particular files, sometimes one to one, sometimes many to one,
> sometimes
> > > one to many.
> > >
> > > If this is too unclear, let me know...
> > > Thanks!
> > >
> > > --
> > > Laura Buchholz
> > > Digital Projects Librarian
> > > Reed College Library
> > > 503-517-7629
> > > [log in to unmask]
> >
>
>
>
> --
> Laura Buchholz
> Digital Projects Librarian
> Reed College Library
> 503-517-7629
> [log in to unmask]
>

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

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