I'm just voicing my concerns. I need this to work with my Aleph
implementation also. If there are config settings to turn things on and
off, so be it.
My consortia is very large and mostly academic libraries. We cover all
of Minnesota. Trying to keep track of ip addresses and such would be a
I did a lot of development a couple of years ago that I would like to
add to the base. I do not care to try to maintain my branch on my own.
I've found that timing is everything when it comes to Open Source
software. When I had the time to work, Vilanova was in limbo. Now that
Demian is here, I've got other priorities. My boss has told me he will
give me time to merge my work late this spring.
The bright side is that since we'll be running Evergreen for a regional
library in Minnesota, we'll probably look at implementing VuFind for
Maybe I'll see you in Grand Rapids next month.
On Fri, 2010-03-26 at 10:21 -0400, John Houser wrote:
> As I indicated in the second sentence of item 4, there would be an indication of the current scope and a way to change the scope--most likely a pull-down with the home library selected by default, much as you have.
> Our initial system is going to be made up exclusively of public libraries, many of them quite small. Most will not customize the interface. Some don't even have their own home page so I must provide a means of setting a default home library. In addition, since we are running Evergreen, holds effectively are ILL. ILL goes away except for the loans outside the system.
> On Mar 26, 2010, at 9:56 AM, Alan Rykhus wrote:
> > On Fri, 2010-03-26 at 09:39 -0400, John Houser wrote:
> >> I'm trying to get a clear picture of the desired behavior, so let me summarize my thinking, based on our discussions and everyone's comments.
> >> Interface aside, the desired behavior would be something like this:
> >> 1. When performing a search, check first for a session cookie. If one exists, take the home library from that.
> >> 2. If there is no session cookie and the user is logged in, get the home library from the user's account profile.
> >> 3. Check for a permanent home library cookie. This would be set by library staff for workstations in their buildings.
> >> 4. If you have gotten a home library from any of the above sources, apply a filter to any searches. Indicate the filter in the interface and provide a convenient way for the user to turn it off or set the home library to "All".
> > The problem I see with this is 'what if the patron wants to search a
> > different library?' Your session cookie and patron home library settings
> > are going to override their desire to search elsewhere. We are very big
> > on Interlibrary Loan in Minnesota. If a patron searches elsewhere, they
> > do get an ILL link. This behavior would stop them from searching
> > elsewhere.
> > I think you're making this too complicated. I've been running my
> > multi-library instance of VuFind for 18 months in a consortia of 75
> > libraries. They are all very happy having a search box or link from
> > their home page to the implementation. It comes up with their library
> > selected. I brand the interface to the selected library. I create links
> > for 'Ask the Librarian' directed to the chosen library.
> > If the patron does a search and gets no results, I create one of two
> > links. If there are items that match the search in the entire database,
> > they are prompted to search the entire consortia. If there are no
> > matches to the search the link suggests alternative spellings.
> > al
> >> 5. When performing a home library scoped search, show only results held by the home library. (Alternately, one could give extra weight to home library results, but I don't think this is the behavior expected by our libraries. Which would you prefer?)
> >> 6. When displaying the holdings for a given record, place the home library copies at the top of the list.
> >> 7. If a home library scoped search returns no results, suggest to the user that they expand their search to all libraries/collections.
> >> Have I missed anything?
> >> J
> >> On Mar 26, 2010, at 8:55 AM, Demian Katz wrote:
> >>> There have already been some good suggestions, but a few more thoughts:
> >>> 1.) From an architectural/configuration perspective, it probably makes sense to have a getHomeLibrary function somewhere -- maybe as part of the Solr Search Object. The point is to centralize the rules for determining a home library so they can be mor
> > e ea
> >>> sily customized (cookie, hard-coded form value, Evergreen lookup, whatever) or even (after we've seen enough use cases) controlled via .ini settings.
> >>> 2.) Another potential .ini setting might be whether to limit only to the home library or to simply boost home library holdings. This could control how the Search Object uses the result of getHomeLibrary to add filter queries or modify the main Solr qu
> > ery.
> >>> 3.) A completely different approach to consider is to introduce a checkbox facet called "Limit to my home library" to make it easy to toggle between all holdings and local holdings (though VuFind's current checkbox facet mechanism will need to be made
> > smar
> >>> ter if you want a location-based checkbox facet to coexist cleanly with a standard location facet list -- right now, it only works correctly for facet fields that are not used elsewhere on the page).
> >>> 4.) Regarding the bq boost query parameter, its restriction to Dismax is a problem right now, but this may be solvable when Solr 1.5 comes out with Extended Dismax -- that feature will introduce more Lucene capabilities to the Dismax handler and may al
> > low
> >>> us to stop using Lucene entirely (or at least restrict it to a much more limited set of circumstances). We could probably start experimenting with it in a branch even sooner using a nightly Solr build, though I prefer to wait for an official release b
> > efo
> >>> re sticking this into the trunk.
> >>> 5.) When you talk about raising home library holdings to the top, are you referring to the search results (as already discussed) or the record view item list (not discussed yet, but probably achievable through driver customizations)?
> >>> 6.) Don't forget about the existing JIRA ticket for this issue -- http://vufind.org/jira/browse/VUFIND-180. Feel free to open new, more specific tickets and link them to it and/or add comments there to keep track of our plans.
> >>> - Demian
> >>>> -----Original Message-----
> >>>> From: John Houser [mailto:houser@...]
> >>>> Sent: Thursday, March 25, 2010 4:26 PM
> >>>> To: vufind-tech@...
> >>>> Subject: [VuFind-Tech] Scoped searching and the home library
> >>>> One of our planned enhancements to VuFind is to allow users to select a
> >>>> specific library to search up front. In addition, we want the user to
> >>>> be able to set a home library for their session and scope the search
> >>>> automatically. This could be part of the user's VuFind profile (or we
> >>>> could get the home library from Evergreen). Our libraries will probably
> >>>> want to set a default home library and have the workstation reset to
> >>>> that home library after a session timeout. This could be a permanent
> >>>> cookie that is overridden by the user's session cookie. Related to
> >>>> this, we'd like the holdings display to put the user's home library
> >>>> items at the top, by default. What are your thoughts on the subject?
> >>>> J
> >>>> --
> >>>> John Houser
> >>>> Technology Coordinator
> >>>> HSLC
> >>>> 215-534-6820
> >>>> houser@...
> >>>> -----------------------------------------------------------------------
> >>>> -------
> >>>> Download Intel® Parallel Studio Eval
> >>>> Try the new software tools for yourself. Speed compiling, find bugs
> >>>> proactively, and fine-tune applications for parallel performance.
> >>>> See why Intel Parallel Studio got high marks during beta.
> >>>> http://p.sf.net/sfu/intel-sw-dev
> >>>> _______________________________________________
> >>>> Vufind-tech mailing list
> >>>> Vufind-tech@...
> >>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech
> >> --
> >> John Houser
> >> Technology Coordinator
> >> HSLC
> >> 215-534-6820
> >> houser@...
> >> ------------------------------------------------------------------------------
> >> Download Intel® Parallel Studio Eval
> >> Try the new software tools for yourself. Speed compiling, find bugs
> >> proactively, and fine-tune applications for parallel performance.
> >> See why Intel Parallel Studio got high marks during beta.
> >> http://p.sf.net/sfu/intel-sw-dev
> >> _______________________________________________
> >> Vufind-tech mailing list
> >> Vufind-tech@...
> >> https://lists.sourceforge.net/lists/listinfo/vufind-tech
> > --
> > Alan Rykhus
> > PALS, A Program of the Minnesota State Colleges and Universities
> > (507)389-1975
> > alan.rykhus@...
> > ------------------------------------------------------------------------------
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Vufind-tech mailing list
> > Vufind-tech@...
> > https://lists.sourceforge.net/lists/listinfo/vufind-tech
> John Houser
> Technology Coordinator
PALS, A Program of the Minnesota State Colleges and Universities