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: article discovery platforms -- post-implementation assessment?

From:

"Harper, Cynthia" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 16 Feb 2016 20:55:03 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (103 lines)

Thanks for the very complete reply! I'll be at IUG and look for your presentation there!

Cindy Harper
VTS

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Thomale, Jason
Sent: Tuesday, February 16, 2016 2:02 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] article discovery platforms -- post-implementation assessment?

Hi Cindy,

Sure, and thank you for the compliment! [And, thanks Terry for the pointer to our report the other day, as well.]

It is homegrown. Regarding sharing, I'm currently in the process of switching that app (and several related projects) from local subversion to the UNT Libraries' GitHub space, but they're not there yet. Personally, I'm also in the process of making the (long overdue) switch from svn to git, so there's a little bit of a mental shift there on my part. My goal is to have everything moved over by mid-March, in time for the Innovative User Group conference--I'll be presenting about our local Catalog API project, which the bento box uses for some of its results, and I'd like to have that whole set of apps available for folks to look at, if possible. Though, it is only a few weeks away, so I may only manage to get the Catalog API up by then--we'll see.

The bento box consists of two components, a backend API and front-end app.

1. The backend API is implemented in Python Django, using Django REST Framework. It provides a simple interface for the front-end app to query and does the job of communicating with bento box search targets and returning the data needed for display as JSON. New search targets can be added pretty easily by extending a base class and overriding methods that define how to query the target and how to translate results into the output format. Different targets can return different fields, and you can use whatever fields are available in views and templates in the front-end app.

2. The front-end is a JS app that uses Backbone.js, RequireJS, and Bootstrap, skinned with our website template. It also ties into Google Analytics, with lots of custom events to record exactly what results people click on; how often "best bets" (from the Summon API) show up, for what queries, and how often they're clicked on; how often each target returns no results and for what queries, and fun things like that.

Search targets include:

* "Articles" retrieves results from Summon via their API.
* "Books and More" scrapes our III Web catalog (ouch). That's why that search tends to perform a little slowly compared to the others.
* "Librarians" hits a Solr instance where we've indexed our LibGuides and staff directory data, in an attempt to serve up a relevant librarian for a given query.
* "Journals" and "Databases" both hit our homegrown Catalog API.
* "Website" hits our Google Custom Search that services the Library website search.
* "Guides" hits our local Solr index of LibGuides.
* "Digital Collections" hits the Solr index for our digital library.
* "Background Materials" is another Summon API search, limited to reference materials.

The reason we're scraping our catalog for Books and More instead of pulling results from our catalog API is because the results the bento box displays needs to mirror what the catalog displays, and attempting to replicate III's relevance ranking ourselves wasn't something we wanted to do. Soon we'll be looking at possibly implementing a Blacklight layer on top of the same Solr index our catalog API uses, at which point we'd switch Books and More so it pulls results from the API instead of scraping the III catalog.

I hope that gives you a good idea, and I'm happy to answer any additional questions on or off list! Thanks for asking.

Jason Thomale
Resource Discovery Systems Librarian
User Interfaces Unit, UNT Libraries



> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf 
> Of Harper, Cynthia
> Sent: Tuesday, February 16, 2016 11:01 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] article discovery platforms -- post- 
> implementation assessment?
> 
> Jason Thomale - can you tell us about your bento-box application? Is 
> it homegrown?  Is it shareable?  I like it a lot.
> 
> Cindy Harper
> Virginia Theological Seminary
> 
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf 
> Of Terry Reese
> Sent: Thursday, February 11, 2016 1:10 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] article discovery platforms -- post- 
> implementation assessment?
> 
> I'm not sure if this was exactly what you are looking for -- but a 
> talk derived from this report was given at C4L last year.
> http://digital.library.unt.edu/ark:/67531/metadc499075/
> 
> --tr
> 
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf 
> Of Tom Cramer
> Sent: Thursday, February 11, 2016 12:55 PM
> To: [log in to unmask]
> Subject: [CODE4LIB] article discovery platforms -- post-implementation 
> assessment?
> 
> I’ve seen many reviews of article discovery platforms (Ebsco Discovery 
> Service, Ex Libris Primo Central, Serials Solutions Summon) before an 
> implementations as part of a selection process—typically covering 
> things like content coverage, API features, integrability with other 
> content / sites. I have not seen any assessments done after an implementation.
> 
> - what has usage of the article search been like?
> - what is the patron satisfaction with the service?
> - has anyone gone from blended results to bento box, or bento box to 
> blended, based on feedback?
> - has anyone switched from one platform to another?
> - knowing what you know now, would you do anything different?
> 
> I’m particularly interested in the experiences of libraries who use 
> their own front ends (like Blacklight or VUFind), and hit the 
> discovery platform via an API.
> 
> Does anyone have a report or local experience they can share? On list 
> or directly?
> 
> It would be great to find some shoulders to stand on here. Thanks!
> 
> - Tom

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