From: John H. <ho...@hs...> - 2010-03-25 20:26:20
|
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 ho...@hs... |
From: Till K. <kin...@gm...> - 2010-03-25 21:02:34
|
So you have kind of a union catalog with holdings from different libraries? I think that is a great thing, especially if you can provide users with an easy way to get items from "other libraries" if it's not available at "home"... Some technical thoughts: The ranking of "home items" on top of the result list may be done using the bq (boost query) parameter of Solr's Dismax queries. This parameter can be used to boost records matching a certain criteria (like "home library has holdings on that record"). Unfortunately bq is not supported by the standard request handler in Solr. To achieve a similar goal, you may add a boosted search for the home library of a user with OR to every standard query like this: [query] OR library:home^1000. We use that to boost items belonging to collections a user selected in her/his profile... It works, but you'll have to play a bit with the boosting values... If you want to restrict searches to one (or multiple) specific library(ies) use fq parameter (filter query) in Solr (just like the facet queries do in standard VuFind). Hmmm, we do all this in a different use case. We have collections of digital resources in an unified index and restrict searches to parts of that index based on users' access rights and boost collections based on users' preferences. Sounds just what you's like to do. It's not hard to do that. Maybe I should "generalize" our solution (at the moment it is very specific to our setup, because it needs to exchange some data, like user preferences and rights with external systems) based on your use case? First question: What would a general interface to an external system providing data to build those bq of fq queries look like? Till John Houser schrieb: > 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 > ho...@hs... > > > > > ------------------------------------------------------------------------------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- http://twitter.com/tillk |
From: Alan R. <ala...@mn...> - 2010-03-25 21:24:49
|
Hello John, My implementation of VUFind has this functionality, but is a branch of the current VUFind code. The plan here is to try to merge this functionality into VUFind this late spring/summer. My VUFind code is used in an Aleph implementation. I'm currently migrating a regional library system to Evergreen, with a go live date in May. Once I'm done with that I hope/plan to be given time for the VUFind update. Our consortia of libraries all have their own home page. They create a search box that searches only their library. So the cookie is not really needed. The libraries seem very happy with this setup. al On Thu, 2010-03-25 at 16:26 -0400, John Houser wrote: > 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 > ho...@hs... > > > > > ------------------------------------------------------------------------------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- Alan Rykhus PALS, A Program of the Minnesota State Colleges and Universities (507)389-1975 ala...@mn... |
From: Osullivan L. <L.O...@sw...> - 2010-03-26 09:34:42
|
Hi All, This functionality would also be extremely helpful for me as I am creating a vufind instance which accesses three different ILS. It would also apply to the default pickup location for Holds and Recalls. I have added a pickupLocations function to each driver to handler this. Cheers, Luke -----Original Message----- From: Alan Rykhus [mailto:ala...@mn...] Sent: 25 March 2010 21:25 To: vuf...@li... Subject: Re: [VuFind-Tech] Scoped searching and the home library Hello John, My implementation of VUFind has this functionality, but is a branch of the current VUFind code. The plan here is to try to merge this functionality into VUFind this late spring/summer. My VUFind code is used in an Aleph implementation. I'm currently migrating a regional library system to Evergreen, with a go live date in May. Once I'm done with that I hope/plan to be given time for the VUFind update. Our consortia of libraries all have their own home page. They create a search box that searches only their library. So the cookie is not really needed. The libraries seem very happy with this setup. al On Thu, 2010-03-25 at 16:26 -0400, John Houser wrote: > 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 > ho...@hs... > > > > > ------------------------------------------------------------------------ ------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- Alan Rykhus PALS, A Program of the Minnesota State Colleges and Universities (507)389-1975 ala...@mn... ------------------------------------------------------------------------ ------ 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 Vuf...@li... https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Demian K. <dem...@vi...> - 2010-03-26 12:57:51
|
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 more easily 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 query. 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 smarter 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 allow 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 before 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:ho...@hs...] > Sent: Thursday, March 25, 2010 4:26 PM > To: vuf...@li... > 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 > ho...@hs... > > > > > ----------------------------------------------------------------------- > ------- > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Osullivan L. <L.O...@sw...> - 2010-03-26 13:41:40
|
Hi Folks, With regards to 5, to sort on a specific library, the driver would have to know either the current ip (for users at a specific location) or the user preference. In the case of the later, getHoldings would have to be passed the patron array or rely on cookies etc. Here's what I'm currently using in tests: $default_library = "MyLIB"; // Needs to be defined in $patron $current_ip = "1.2.3.4"; // Needs to be extracted $valid_ip = $catalog->driver->in_ip_range($current_ip, $config['ip_range']); $ip_library = "MyLib"; // Determined by IP if(count($holdings) > 1) { // Resort Holdings based on affiliation foreach($holdings as $libkey => $system) { if($libkey == $default_library || $libkey == $ip_library) { $TopHoldings[$libkey] = $system; } else { $nonTopHoldings[$libkey] = $system; } } $holdings = array_merge($TopHoldings, $nonTopHoldings); } The foreach loop certainly needs rewriting but it creates the desired effect. Cheers, Luke -----Original Message----- From: Demian Katz [mailto:dem...@vi...] Sent: 26 March 2010 12:55 To: ho...@hs...; vuf...@li... Subject: Re: [VuFind-Tech] Scoped searching and the home library 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 more easily 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 query. 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 smarter 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 allow 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 before 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:ho...@hs...] > Sent: Thursday, March 25, 2010 4:26 PM > To: vuf...@li... > 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 > ho...@hs... > > > > > ----------------------------------------------------------------------- > ------- > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech ------------------------------------------------------------------------ ------ 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 Vuf...@li... https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: John H. <ho...@hs...> - 2010-03-26 13:39:18
|
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". 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 more 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 query. > > 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 allow > 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 befo > 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:ho...@hs...] >> Sent: Thursday, March 25, 2010 4:26 PM >> To: vuf...@li... >> 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 >> ho...@hs... >> >> >> >> >> ----------------------------------------------------------------------- >> ------- >> 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 >> Vuf...@li... >> https://lists.sourceforge.net/lists/listinfo/vufind-tech -- John Houser Technology Coordinator HSLC 215-534-6820 ho...@hs... |
From: John H. <ho...@hs...> - 2010-03-26 13:44:27
|
One thing I forgot in the list: a session time-out which results in the deletion of any session cookie. J On Mar 26, 2010, at 9:39 AM, 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". > 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 more > 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 quer > y. >> >> 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 sm > ar >> 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 allo > w >> 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 bef > o >> 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:ho...@hs...] >>> Sent: Thursday, March 25, 2010 4:26 PM >>> To: vuf...@li... >>> 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 >>> ho...@hs... >>> >>> >>> >>> >>> ----------------------------------------------------------------------- >>> ------- >>> 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 >>> Vuf...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > -- > John Houser > Technology Coordinator > HSLC > 215-534-6820 > ho...@hs... > > > > > ------------------------------------------------------------------------------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- John Houser Technology Coordinator HSLC 215-534-6820 ho...@hs... |
From: Alan R. <ala...@mn...> - 2010-03-26 13:56:41
|
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 more 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 query. > > > > 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 allow > > 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 befo > > 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:ho...@hs...] > >> Sent: Thursday, March 25, 2010 4:26 PM > >> To: vuf...@li... > >> 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 > >> ho...@hs... > >> > >> > >> > >> > >> ----------------------------------------------------------------------- > >> ------- > >> 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 > >> Vuf...@li... > >> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > -- > John Houser > Technology Coordinator > HSLC > 215-534-6820 > ho...@hs... > > > > > ------------------------------------------------------------------------------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- Alan Rykhus PALS, A Program of the Minnesota State Colleges and Universities (507)389-1975 ala...@mn... |
From: Demian K. <dem...@vi...> - 2010-03-26 13:58:19
|
Rather than having a separate session cookie for home library, perhaps it would make more sense to store the value in the server-side PHP session for the current logged-in user. That way, when the user logs out, the value goes away automatically, and PHP's existing session expiration mechanism can take care of timeouts. Since this value is tied to the logged in user's identity, I see no reason to track or expire it separately from other user-oriented session values. And just to make sure we're speaking the same language, some definitions: "session cookie" - a cookie stored on the client machine that expires when the web browser closes "PHP session" - data stored on the server machine, associated with the PHP session cookie "PHP session cookie" - a session cookie used by the server to load the appropriate PHP session for the current user It always gets confusing when you talk about session cookies and PHP sessions in the same breath! - Demian > -----Original Message----- > From: John Houser [mailto:ho...@hs...] > Sent: Friday, March 26, 2010 9:44 AM > To: ho...@hs... > Cc: vuf...@li... > Subject: Re: [VuFind-Tech] Scoped searching and the home library > > One thing I forgot in the list: a session time-out which results in the > deletion of any session cookie. > > J > > > On Mar 26, 2010, at 9:39 AM, 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". > > 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 more > > 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 quer > > y. > >> > >> 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 sm > > ar > >> 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 allo > > w > >> 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 bef > > o > >> 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:ho...@hs...] > >>> Sent: Thursday, March 25, 2010 4:26 PM > >>> To: vuf...@li... > >>> 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 > >>> ho...@hs... > >>> > >>> > >>> > >>> > >>> ------------------------------------------------------------------- > ---- > >>> ------- > >>> 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 > >>> Vuf...@li... > >>> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > > > -- > > John Houser > > Technology Coordinator > > HSLC > > 215-534-6820 > > ho...@hs... > > > > > > > > > > --------------------------------------------------------------------- > --------- > > 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 > > Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > -- > John Houser > Technology Coordinator > HSLC > 215-534-6820 > ho...@hs... > > > > > ----------------------------------------------------------------------- > ------- > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: John H. <ho...@hs...> - 2010-03-26 14:13:42
|
Luke, Holdings libraries are also indexed if you set the Institution and Building in the import/marc_local.properties or if you create your own index from values in the 852 or other MARC field. Evergreen's marc-export utility will automatically add holdings to the 882. I run a little utility to translate library codes to names before I import into VuFind. J On Mar 26, 2010, at 9:49 AM, Osullivan L. wrote: > Hi John, > > As I understand it, whether or not a library has holdings of a specific > title is determined by the getHoldings function which relies on an id > from solr. How is the link between solr and the holdings of an > individual library to be established? Would you add the information to > your Marc records and update them as items were added / removed from > each library? > > Kind Regards, > > Luke > > -----Original Message----- > From: John Houser [mailto:ho...@hs...] > Sent: 26 March 2010 13:39 > To: vuf...@li... > Subject: Re: [VuFind-Tech] Scoped searching and the home library > > 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". > 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 more 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 query. >> >> 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 allow >> 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 befo >> 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:ho...@hs...] >>> Sent: Thursday, March 25, 2010 4:26 PM >>> To: vuf...@li... >>> 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 >>> ho...@hs... >>> >>> >>> >>> >>> > ----------------------------------------------------------------------- >>> ------- >>> 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 >>> Vuf...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > -- > John Houser > Technology Coordinator > HSLC > 215-534-6820 > ho...@hs... > > > > > ------------------------------------------------------------------------ > ------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- John Houser Technology Coordinator HSLC 215-534-6820 ho...@hs... |
From: John H. <ho...@hs...> - 2010-03-26 14:21:19
|
Al, 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. J 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:ho...@hs...] >>>> Sent: Thursday, March 25, 2010 4:26 PM >>>> To: vuf...@li... >>>> 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 >>>> ho...@hs... >>>> >>>> >>>> >>>> >>>> ----------------------------------------------------------------------- >>>> ------- >>>> 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 >>>> Vuf...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >> >> >> -- >> John Houser >> Technology Coordinator >> HSLC >> 215-534-6820 >> ho...@hs... >> >> >> >> >> ------------------------------------------------------------------------------ >> 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 >> Vuf...@li... >> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > -- > Alan Rykhus > PALS, A Program of the Minnesota State Colleges and Universities > (507)389-1975 > ala...@mn... > > > ------------------------------------------------------------------------------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- John Houser Technology Coordinator HSLC 215-534-6820 ho...@hs... |
From: Alan R. <ala...@mn...> - 2010-03-26 14:32:49
|
Hello John, 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 nightmare(another nightmare). 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 them to. Maybe I'll see you in Grand Rapids next month. al On Fri, 2010-03-26 at 10:21 -0400, John Houser wrote: > Al, > 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. > > J > > > 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:ho...@hs...] > >>>> Sent: Thursday, March 25, 2010 4:26 PM > >>>> To: vuf...@li... > >>>> 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 > >>>> ho...@hs... > >>>> > >>>> > >>>> > >>>> > >>>> ----------------------------------------------------------------------- > >>>> ------- > >>>> 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 > >>>> Vuf...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech > >> > >> > >> -- > >> John Houser > >> Technology Coordinator > >> HSLC > >> 215-534-6820 > >> ho...@hs... > >> > >> > >> > >> > >> ------------------------------------------------------------------------------ > >> 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 > >> Vuf...@li... > >> https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > > > -- > > Alan Rykhus > > PALS, A Program of the Minnesota State Colleges and Universities > > (507)389-1975 > > ala...@mn... > > > > > > ------------------------------------------------------------------------------ > > 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 > > Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > -- > John Houser > Technology Coordinator > HSLC > 215-534-6820 > ho...@hs... > > > -- Alan Rykhus PALS, A Program of the Minnesota State Colleges and Universities (507)389-1975 ala...@mn... |
From: Demian K. <dem...@vi...> - 2010-03-26 14:28:14
|
> 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. Perhaps a compromise between your model and John's would be something like this: 1.) Check first for a session value indicating that the current user has intentionally overridden the default home library. If found, use that. 2.) If a home library is not yet determined, check to see if a particular $_REQUEST value has been set to specify a default home library. Using $_REQUEST would allow home library to be set by a permanent cookie as John suggested OR through a hard-coded link or form value as you suggest. 3.) If a home library is STILL not determined, and a user is logged in, check to see if they have a home library associated with their account. 4.) Last resort: default to all libraries. I think this covers all the use cases, assuming you don't object to the fact that the "default in $_REQUEST" trumps the "default in user's account." If you wanted to get even more flexible, you could add controls to allow a user to permanently change their home library and perhaps store an "always use this home library when I am logged in" setting. You could then put in a step 1.5 to check if a user setting trumps the $_REQUEST value. - Demian |
From: Alan R. <ala...@mn...> - 2010-03-26 14:45:12
|
Hello, I was thinking. John's main concern is when the patron first connects. He needs a library selected. I do it by the form on the library's home page, he needs to do it by IP address. So we could set a switch to use the ip address to determine the home library. After the patron starts searching, they determine the library. I've done it by adding a 'library=???' setting in all of my links, search cookies, etc. So in a way, we are probably talking the same thing, this search is in this library. If you look at my implementation, you would see that a search history list will include an entry for each library a search is done in if they change libraries with the same search terms. As for using the patron's home library when they log on, In my experience, you do not want to change anything here. I think that a patron does not log on until they have to. If they have been searching and finally identify an item they want, you do not want to change their search parameters. You just want to enable their ability to place a hold or ILL request. al - (patiently waiting for his conversion to finish) On Fri, 2010-03-26 at 10:24 -0400, Demian Katz wrote: > > 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. > > Perhaps a compromise between your model and John's would be something like this: > > 1.) Check first for a session value indicating that the current user has intentionally overridden the default home library. If found, use that. > 2.) If a home library is not yet determined, check to see if a particular $_REQUEST value has been set to specify a default home library. Using $_REQUEST would allow home library to be set by a permanent cookie as John suggested OR through a hard-coded link or form value as you suggest. > 3.) If a home library is STILL not determined, and a user is logged in, check to see if they have a home library associated with their account. > 4.) Last resort: default to all libraries. > > I think this covers all the use cases, assuming you don't object to the fact that the "default in $_REQUEST" trumps the "default in user's account." > > If you wanted to get even more flexible, you could add controls to allow a user to permanently change their home library and perhaps store an "always use this home library when I am logged in" setting. You could then put in a step 1.5 to check if a user setting trumps the $_REQUEST value. > > - Demian -- Alan Rykhus PALS, A Program of the Minnesota State Colleges and Universities (507)389-1975 ala...@mn... |
From: John H. <ho...@hs...> - 2010-03-26 14:59:18
|
Al, I think you have misunderstood me. I have never suggested using IP addresses for determining the home library. The process for selecting a home library outlined in Demian's last message sounded fine to me. Note that if the user has set a home library in their session, it is *not* overridden by the home library in the user's profile. My idea has been that the "permanent" home library cookie would be set during a visit to a configuration page we create somewhere on our website. This option would not be made available to regular users in the interface. As your comments have suggested, we probably want to add to the list setting the home library as the default pickup location for holds. J On Mar 26, 2010, at 10:45 AM, Alan Rykhus wrote: > Hello, > > I was thinking. > > John's main concern is when the patron first connects. He needs a > library selected. I do it by the form on the library's home page, he > needs to do it by IP address. So we could set a switch to use the ip > address to determine the home library. > > After the patron starts searching, they determine the library. I've done > it by adding a 'library=???' setting in all of my links, search cookies, > etc. So in a way, we are probably talking the same thing, this search is > in this library. If you look at my implementation, you would see that a > search history list will include an entry for each library a search is > done in if they change libraries with the same search terms. > > As for using the patron's home library when they log on, In my > experience, you do not want to change anything here. I think that a > patron does not log on until they have to. If they have been searching > and finally identify an item they want, you do not want to change their > search parameters. You just want to enable their ability to place a hold > or ILL request. > > al - (patiently waiting for his conversion to finish) > > On Fri, 2010-03-26 at 10:24 -0400, Demian Katz wrote: >>> 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. >> >> Perhaps a compromise between your model and John's would be something like this: >> >> 1.) Check first for a session value indicating that the current user has intentionally overridden the default home library. If found, use that. >> 2.) If a home library is not yet determined, check to see if a particular $_REQUEST value has been set to specify a default home library. Using $_REQUEST would allow home library to be set by a permanent cookie as John suggested OR through a hard-coded > link or form value as you suggest. >> 3.) If a home library is STILL not determined, and a user is logged in, check to see if they have a home library associated with their account. >> 4.) Last resort: default to all libraries. >> >> I think this covers all the use cases, assuming you don't object to the fact that the "default in $_REQUEST" trumps the "default in user's account." >> >> If you wanted to get even more flexible, you could add controls to allow a user to permanently change their home library and perhaps store an "always use this home library when I am logged in" setting. You could then put in a step 1.5 to check if a user > setting trumps the $_REQUEST value. >> >> - Demian > > > -- > Alan Rykhus > PALS, A Program of the Minnesota State Colleges and Universities > (507)389-1975 > ala...@mn... > > > ------------------------------------------------------------------------------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- John Houser Technology Coordinator HSLC 215-534-6820 ho...@hs... |
From: Demian K. <dem...@vi...> - 2010-03-26 14:59:56
|
I agree that users are likely to be dismayed if their search results suddenly change because they logged in. It probably only makes sense to use the home library setting from the account if we also force the user to log in up-front, which we probably don't want to do. In any case, my proposed compromise algorithm had a flaw which would have prevented the user setting from being taken into account... So let's try a revision: 1.) If session value is found, use that. 2.) If $_REQUEST value is found, set session value to match and use that. If the $_REQUEST value is not coming from a cookie, we might also want to set a cookie at this time to allow the $_REQUEST value to be reintroduced if the PHP session gets cleared by a user's subsequent log out action. 3.) If "detect by IP" setting is turned on, use IP map to determine home library, set session value to match, and use that. 4.) Set session value to "all libraries" and use that. Obviously, the user can change the session value at any time by using some sort of on-screen control... but it is never based on the user's home library setting. - Demian > -----Original Message----- > From: Alan Rykhus [mailto:ala...@mn...] > Sent: Friday, March 26, 2010 10:45 AM > To: Demian Katz > Cc: vuf...@li... > Subject: RE: [VuFind-Tech] Scoped searching and the home library > > Hello, > > I was thinking. > > John's main concern is when the patron first connects. He needs a > library selected. I do it by the form on the library's home page, he > needs to do it by IP address. So we could set a switch to use the ip > address to determine the home library. > > After the patron starts searching, they determine the library. I've > done > it by adding a 'library=???' setting in all of my links, search > cookies, > etc. So in a way, we are probably talking the same thing, this search > is > in this library. If you look at my implementation, you would see that a > search history list will include an entry for each library a search is > done in if they change libraries with the same search terms. > > As for using the patron's home library when they log on, In my > experience, you do not want to change anything here. I think that a > patron does not log on until they have to. If they have been searching > and finally identify an item they want, you do not want to change their > search parameters. You just want to enable their ability to place a > hold > or ILL request. > > al - (patiently waiting for his conversion to finish) > > On Fri, 2010-03-26 at 10:24 -0400, Demian Katz wrote: > > > 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. > > > > Perhaps a compromise between your model and John's would be something > like this: > > > > 1.) Check first for a session value indicating that the current user > has intentionally overridden the default home library. If found, use > that. > > 2.) If a home library is not yet determined, check to see if a > particular $_REQUEST value has been set to specify a default home > library. Using $_REQUEST would allow home library to be set by a > permanent cookie as John suggested OR through a hard-coded link or form > value as you suggest. > > 3.) If a home library is STILL not determined, and a user is logged > in, check to see if they have a home library associated with their > account. > > 4.) Last resort: default to all libraries. > > > > I think this covers all the use cases, assuming you don't object to > the fact that the "default in $_REQUEST" trumps the "default in user's > account." > > > > If you wanted to get even more flexible, you could add controls to > allow a user to permanently change their home library and perhaps store > an "always use this home library when I am logged in" setting. You > could then put in a step 1.5 to check if a user setting trumps the > $_REQUEST value. > > > > - Demian > > > -- > Alan Rykhus > PALS, A Program of the Minnesota State Colleges and Universities > (507)389-1975 > ala...@mn... |
From: John H. <ho...@hs...> - 2010-03-26 15:47:05
|
Demian and Al, I agree that it would be confusing to change a user's search results just because they log into the system. I have no need of an IP-based home library setting. It would be a nightmare to administer! So I would just drop #3 from this. I can live with just using the user's home library to set the default for the pick-up location and to determine display order in the holdings display. Since both uses will probably be a function of the Evergreen driver and the templates in our theme, neither use of the user's home library will impact most libraries. Make sense? J On Mar 26, 2010, at 10:57 AM, Demian Katz wrote: > I agree that users are likely to be dismayed if their search results suddenly change because they logged in. It probably only makes sense to use the home library setting from the account if we also force the user to log in up-front, which we probably don' > t want to do. In any case, my proposed compromise algorithm had a flaw which would have prevented the user setting from being taken into account... So let's try a revision: > > 1.) If session value is found, use that. > 2.) If $_REQUEST value is found, set session value to match and use that. If the $_REQUEST value is not coming from a cookie, we might also want to set a cookie at this time to allow the $_REQUEST value to be reintroduced if the PHP session gets cleared b > y a user's subsequent log out action. > 3.) If "detect by IP" setting is turned on, use IP map to determine home library, set session value to match, and use that. > 4.) Set session value to "all libraries" and use that. > > Obviously, the user can change the session value at any time by using some sort of on-screen control... but it is never based on the user's home library setting. > > - Demian > >> -----Original Message----- >> From: Alan Rykhus [mailto:ala...@mn...] >> Sent: Friday, March 26, 2010 10:45 AM >> To: Demian Katz >> Cc: vuf...@li... >> Subject: RE: [VuFind-Tech] Scoped searching and the home library >> >> Hello, >> >> I was thinking. >> >> John's main concern is when the patron first connects. He needs a >> library selected. I do it by the form on the library's home page, he >> needs to do it by IP address. So we could set a switch to use the ip >> address to determine the home library. >> >> After the patron starts searching, they determine the library. I've >> done >> it by adding a 'library=???' setting in all of my links, search >> cookies, >> etc. So in a way, we are probably talking the same thing, this search >> is >> in this library. If you look at my implementation, you would see that a >> search history list will include an entry for each library a search is >> done in if they change libraries with the same search terms. >> >> As for using the patron's home library when they log on, In my >> experience, you do not want to change anything here. I think that a >> patron does not log on until they have to. If they have been searching >> and finally identify an item they want, you do not want to change their >> search parameters. You just want to enable their ability to place a >> hold >> or ILL request. >> >> al - (patiently waiting for his conversion to finish) >> >> On Fri, 2010-03-26 at 10:24 -0400, Demian Katz wrote: >>>> 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. >>> >>> Perhaps a compromise between your model and John's would be something >> like this: >>> >>> 1.) Check first for a session value indicating that the current user >> has intentionally overridden the default home library. If found, use >> that. >>> 2.) If a home library is not yet determined, check to see if a >> particular $_REQUEST value has been set to specify a default home >> library. Using $_REQUEST would allow home library to be set by a >> permanent cookie as John suggested OR through a hard-coded link or form >> value as you suggest. >>> 3.) If a home library is STILL not determined, and a user is logged >> in, check to see if they have a home library associated with their >> account. >>> 4.) Last resort: default to all libraries. >>> >>> I think this covers all the use cases, assuming you don't object to >> the fact that the "default in $_REQUEST" trumps the "default in user's >> account." >>> >>> If you wanted to get even more flexible, you could add controls to >> allow a user to permanently change their home library and perhaps store >> an "always use this home library when I am logged in" setting. You >> could then put in a step 1.5 to check if a user setting trumps the >> $_REQUEST value. >>> >>> - Demian >> >> >> -- >> Alan Rykhus >> PALS, A Program of the Minnesota State Colleges and Universities >> (507)389-1975 >> ala...@mn... > > > ------------------------------------------------------------------------------ > 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 > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech -- John Houser Technology Coordinator HSLC 215-534-6820 ho...@hs... |
From: Alan R. <ala...@mn...> - 2010-03-26 16:46:55
|
Sounds good I agree that holds, etc. are driver dependent al On Fri, 2010-03-26 at 11:46 -0400, John Houser wrote: > Demian and Al, > I agree that it would be confusing to change a user's search results just because they log into the system. I have no need of an IP-based home library setting. It would be a nightmare to administer! So I would just drop #3 from this. I can live with just using the user's home library to set the default for the pick-up location and to determine display order in the holdings display. Since both uses will probably be a function of the Evergreen driver and the templates in our theme, neither use of the user's home library will impact most libraries. Make sense? > > J > > > > On Mar 26, 2010, at 10:57 AM, Demian Katz wrote: > > > I agree that users are likely to be dismayed if their search results suddenly change because they logged in. It probably only makes sense to use the home library setting from the account if we also force the user to log in up-front, which we probably don' > > t want to do. In any case, my proposed compromise algorithm had a flaw which would have prevented the user setting from being taken into account... So let's try a revision: > > > > 1.) If session value is found, use that. > > 2.) If $_REQUEST value is found, set session value to match and use that. If the $_REQUEST value is not coming from a cookie, we might also want to set a cookie at this time to allow the $_REQUEST value to be reintroduced if the PHP session gets cleared b > > y a user's subsequent log out action. > > 3.) If "detect by IP" setting is turned on, use IP map to determine home library, set session value to match, and use that. > > 4.) Set session value to "all libraries" and use that. > > > > Obviously, the user can change the session value at any time by using some sort of on-screen control... but it is never based on the user's home library setting. > > > > - Demian > > > >> -----Original Message----- > >> From: Alan Rykhus [mailto:ala...@mn...] > >> Sent: Friday, March 26, 2010 10:45 AM > >> To: Demian Katz > >> Cc: vuf...@li... > >> Subject: RE: [VuFind-Tech] Scoped searching and the home library > >> > >> Hello, > >> > >> I was thinking. > >> > >> John's main concern is when the patron first connects. He needs a > >> library selected. I do it by the form on the library's home page, he > >> needs to do it by IP address. So we could set a switch to use the ip > >> address to determine the home library. > >> > >> After the patron starts searching, they determine the library. I've > >> done > >> it by adding a 'library=???' setting in all of my links, search > >> cookies, > >> etc. So in a way, we are probably talking the same thing, this search > >> is > >> in this library. If you look at my implementation, you would see that a > >> search history list will include an entry for each library a search is > >> done in if they change libraries with the same search terms. > >> > >> As for using the patron's home library when they log on, In my > >> experience, you do not want to change anything here. I think that a > >> patron does not log on until they have to. If they have been searching > >> and finally identify an item they want, you do not want to change their > >> search parameters. You just want to enable their ability to place a > >> hold > >> or ILL request. > >> > >> al - (patiently waiting for his conversion to finish) > >> > >> On Fri, 2010-03-26 at 10:24 -0400, Demian Katz wrote: > >>>> 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. > >>> > >>> Perhaps a compromise between your model and John's would be something > >> like this: > >>> > >>> 1.) Check first for a session value indicating that the current user > >> has intentionally overridden the default home library. If found, use > >> that. > >>> 2.) If a home library is not yet determined, check to see if a > >> particular $_REQUEST value has been set to specify a default home > >> library. Using $_REQUEST would allow home library to be set by a > >> permanent cookie as John suggested OR through a hard-coded link or form > >> value as you suggest. > >>> 3.) If a home library is STILL not determined, and a user is logged > >> in, check to see if they have a home library associated with their > >> account. > >>> 4.) Last resort: default to all libraries. > >>> > >>> I think this covers all the use cases, assuming you don't object to > >> the fact that the "default in $_REQUEST" trumps the "default in user's > >> account." > >>> > >>> If you wanted to get even more flexible, you could add controls to > >> allow a user to permanently change their home library and perhaps store > >> an "always use this home library when I am logged in" setting. You > >> could then put in a step 1.5 to check if a user setting trumps the > >> $_REQUEST value. > >>> > >>> - Demian > >> > >> > >> -- > >> Alan Rykhus > >> PALS, A Program of the Minnesota State Colleges and Universities > >> (507)389-1975 > >> ala...@mn... > > > > > > ------------------------------------------------------------------------------ > > 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 > > Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > -- > John Houser > Technology Coordinator > HSLC > 215-534-6820 > ho...@hs... > > > -- Alan Rykhus PALS, A Program of the Minnesota State Colleges and Universities (507)389-1975 ala...@mn... |
From: Demian K. <dem...@vi...> - 2010-03-26 17:27:10
|
Since we seem to have reached something of a consensus, I have put a detailed comment in JIRA including some (untested) PHP code to demonstrate the algorithm: http://vufind.org/jira/browse/VUFIND-180 If you get a chance, please take a chance and let me know if I've missed or misrepresented anything. I can edit the comment if any changes are needed. - Demian > -----Original Message----- > From: Alan Rykhus [mailto:ala...@mn...] > Sent: Friday, March 26, 2010 12:47 PM > To: ho...@hs... > Cc: Demian Katz; vuf...@li... > Subject: Re: [VuFind-Tech] Scoped searching and the home library > > Sounds good > > I agree that holds, etc. are driver dependent > > al > > On Fri, 2010-03-26 at 11:46 -0400, John Houser wrote: > > Demian and Al, > > I agree that it would be confusing to change a user's search results > just because they log into the system. I have no need of an IP-based > home library setting. It would be a nightmare to administer! So I would > just drop #3 from this. I can live with just using the user's home > library to set the default for the pick-up location and to determine > display order in the holdings display. Since both uses will probably be > a function of the Evergreen driver and the templates in our theme, > neither use of the user's home library will impact most libraries. Make > sense? > > > > J > > > > > > > > On Mar 26, 2010, at 10:57 AM, Demian Katz wrote: > > > > > I agree that users are likely to be dismayed if their search > results suddenly change because they logged in. It probably only makes > sense to use the home library setting from the account if we also force > the user to log in up-front, which we probably don' > > > t want to do. In any case, my proposed compromise algorithm had a > flaw which would have prevented the user setting from being taken into > account... So let's try a revision: > > > > > > 1.) If session value is found, use that. > > > 2.) If $_REQUEST value is found, set session value to match and use > that. If the $_REQUEST value is not coming from a cookie, we might > also want to set a cookie at this time to allow the $_REQUEST value to > be reintroduced if the PHP session gets cleared b > > > y a user's subsequent log out action. > > > 3.) If "detect by IP" setting is turned on, use IP map to determine > home library, set session value to match, and use that. > > > 4.) Set session value to "all libraries" and use that. > > > > > > Obviously, the user can change the session value at any time by > using some sort of on-screen control... but it is never based on the > user's home library setting. > > > > > > - Demian > > > > > >> -----Original Message----- > > >> From: Alan Rykhus [mailto:ala...@mn...] > > >> Sent: Friday, March 26, 2010 10:45 AM > > >> To: Demian Katz > > >> Cc: vuf...@li... > > >> Subject: RE: [VuFind-Tech] Scoped searching and the home library > > >> > > >> Hello, > > >> > > >> I was thinking. > > >> > > >> John's main concern is when the patron first connects. He needs a > > >> library selected. I do it by the form on the library's home page, > he > > >> needs to do it by IP address. So we could set a switch to use the > ip > > >> address to determine the home library. > > >> > > >> After the patron starts searching, they determine the library. > I've > > >> done > > >> it by adding a 'library=???' setting in all of my links, search > > >> cookies, > > >> etc. So in a way, we are probably talking the same thing, this > search > > >> is > > >> in this library. If you look at my implementation, you would see > that a > > >> search history list will include an entry for each library a > search is > > >> done in if they change libraries with the same search terms. > > >> > > >> As for using the patron's home library when they log on, In my > > >> experience, you do not want to change anything here. I think that > a > > >> patron does not log on until they have to. If they have been > searching > > >> and finally identify an item they want, you do not want to change > their > > >> search parameters. You just want to enable their ability to place > a > > >> hold > > >> or ILL request. > > >> > > >> al - (patiently waiting for his conversion to finish) > > >> > > >> On Fri, 2010-03-26 at 10:24 -0400, Demian Katz wrote: > > >>>> 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. > > >>> > > >>> Perhaps a compromise between your model and John's would be > something > > >> like this: > > >>> > > >>> 1.) Check first for a session value indicating that the current > user > > >> has intentionally overridden the default home library. If found, > use > > >> that. > > >>> 2.) If a home library is not yet determined, check to see if a > > >> particular $_REQUEST value has been set to specify a default home > > >> library. Using $_REQUEST would allow home library to be set by a > > >> permanent cookie as John suggested OR through a hard-coded link or > form > > >> value as you suggest. > > >>> 3.) If a home library is STILL not determined, and a user is > logged > > >> in, check to see if they have a home library associated with their > > >> account. > > >>> 4.) Last resort: default to all libraries. > > >>> > > >>> I think this covers all the use cases, assuming you don't object > to > > >> the fact that the "default in $_REQUEST" trumps the "default in > user's > > >> account." > > >>> > > >>> If you wanted to get even more flexible, you could add controls > to > > >> allow a user to permanently change their home library and perhaps > store > > >> an "always use this home library when I am logged in" setting. > You > > >> could then put in a step 1.5 to check if a user setting trumps the > > >> $_REQUEST value. > > >>> > > >>> - Demian > > >> > > >> > > >> -- > > >> Alan Rykhus > > >> PALS, A Program of the Minnesota State Colleges and Universities > > >> (507)389-1975 > > >> ala...@mn... > > > > > > > > > ------------------------------------------------------------------- > ----------- > > > 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 > > > Vuf...@li... > > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > > > -- > > John Houser > > Technology Coordinator > > HSLC > > 215-534-6820 > > ho...@hs... > > > > > > > > > -- > Alan Rykhus > PALS, A Program of the Minnesota State Colleges and Universities > (507)389-1975 > ala...@mn... |