Re: [CODE4LIB] Library Hours Fail

2014-11-18 Thread Doug Chestnut
Sorry, fixed example link as my clipboard is acting up today: http://uvalib-components.github.io/uvalib-hours-ui/components/uvalib-hours-ui/demo.html On Tue, Nov 18, 2014 at 10:55 AM, Doug Chestnut wrote: > Hi Mary, > I'm working up a web component that will do hours from a Google

Re: [CODE4LIB] Library Hours Fail

2014-11-18 Thread Doug Chestnut
Hi Mary, I'm working up a web component that will do hours from a Google Cal. It's a bit alpha (and bleeding edge) given it's a web component and I haven't gotten around to using it in production. Feel free to ignore the rest of this email. example: https://github.com/uvalib-components/uvalib-ho

Re: [CODE4LIB] Auto-suggest and the id.loc.gov LCSH web service

2009-12-07 Thread Doug Chestnut
mod_cache might help, assuming that performance gets better as your query string grows. --Doug On Mon, Dec 7, 2009 at 11:14 AM, Ethan Gruber wrote: > It doesn't seem very efficient.  It is taking me at least 30 seconds to load > a page of 'a*' in http://id.loc.gov/authorities/search/ > > On Mon,

Re: [CODE4LIB] Blacklight + Summon at UVA

2009-10-07 Thread Doug Chestnut
Hi Emily- Our summon-enabled mobile site is here: http://summon.latest.uvalibmobile.appspot.com This version of the site is using a trial of summon and should be considered a proof of concept at this point. The more conventional approach (also the simplest) would involve adding catalog records to

Re: [CODE4LIB] a brief summary of the Google App Engine

2008-07-18 Thread Doug Chestnut
ake a closer look at the src docs... > > Keith > > > On Thu, Jul 17, 2008 at 3:01 PM, Doug Chestnut <[EMAIL PROTECTED]> > wrote: > > There is a Searchable Entity with GAE. Refer to the src for docs. It is > > fairly straight forward, it takes the text of the propert

Re: [CODE4LIB] a brief summary of the Google App Engine

2008-07-17 Thread Doug Chestnut
On Wed, Jul 16, 2008 at 6:29 AM, Keith Jenkins <[EMAIL PROTECTED]> wrote: > [...] > > So it's a bit of a hack just to get a left-anchored search. Querying > for a particular keyword anywhere within a string value would be even > more work. For small datasets, I guess you could iterate through >