Menu
▾
▴
Re: [VuFind-Tech] Mutli-Site Architecture
|
From: John W. <joh...@un...> - 2011-07-06 18:28:44
|
Demian, No question here, I thought I would show you where I'm at with the whole multisite setup. The information you sent helped considerably. I've got some work to do, but there is enough here for our folks who are evaluating it to understand what is possible. I set it up so that it will take the scope from POST, GET, or COOKIE so that users can start in an interface. Here are some URLS to see the mult-site approach to vufind. I was asked to test it without an "unscoped"(no institution filter) interface in this iteration. I will add it if asked. UNI http://vhost1.lib.uni.edu/vufind/?myscope=1 HCC http://vhost1.lib.uni.edu/vufind/?myscope=2 CFPL http://vhost1.lib.uni.edu/vufind/?myscope=3 WPL http://vhost1.lib.uni.edu/vufind/?myscope=7 AC http://vhost1.lib.uni.edu/vufind/?myscope=8 WC http://vhost1.lib.uni.edu/vufind/?myscope=9 On 7/1/2011 9:54 AM, John Wynstra wrote: > Clue was definitely in the patch. The caching mechanism in Home.php > under search was keeping header.tpl from rerunning. I set it to 0, as a > test, and my control updates itself properly. > > I'll see what needs to be done to set this up properly in Home.php. > > On 7/1/2011 9:21 AM, Demian Katz wrote: >> Could you share your template code you're using to display the jumpmenu? I have some ideas, but I can probably give a better-targeted suggestion if I see the code. Also, did you look at the patch at http://vufind.org/jira/secure/attachment/10285/library_selection.patch ? Perhaps that can answer your question too. >> >> - Demian >> >>> -----Original Message----- >>> From: John Wynstra [mailto:joh...@un...] >>> Sent: Friday, July 01, 2011 10:16 AM >>> To: Demian Katz >>> Cc: vuf...@li... >>> Subject: Re: [VuFind-Tech] Mutli-Site Architecture >>> >>> OK. I finally got around to playing with this, but I have an odd >>> mechanical problem that I'm guessing has to do with caching somehow. >>> >>> I have a dropdown jumpmenu configured exactly like the language >>> dropdown >>> jumpmenu. (http://vhost1.lib.uni.edu/vufind -- upper right) >>> >>> The behind the scenes behavior that this "scope" control is doing >>> right >>> now is setting a cookie much like the language jumpmenu and internally >>> setting the scope in the Interface.php. >>> >>> The odd behavior is that the jumpmenu does NOT hold the selected value >>> within the control even though it is properly setting the cookie. I've >>> looked the code over multiple times, and have not found a logic issue. >>> It is only the rendered control that is not changing. >>> >>> The language menu has no problem retaining whatever setting is >>> selected. >>> >>> So simply put, any ideas as to why the jumpmenu is not being updated? >>> I'm using the blueprint as my base them. >>> >>> >>> >>> >>> >>> On 6/21/2011 9:09 AM, Demian Katz wrote: >>>> I think meeting your needs should be relatively straightforward. >>> I've recently been working with another library to help them set up a >>> drop-down control that limits the collection to a particular location. >>> It works like this: >>>> >>>> 1.) Their import process is set up to populate the "institution" >>> field of the index. >>>> 2.) They have added a drop-down library selection list to their page >>> template. >>>> 3.) They have modified web/index.php to process the submission of the >>> drop-down (similar to the way language selection currently works), >>> setting a cookie to retain the user preference. >>>> 4.) In web/sys/SearchObject/Solr.php, they use the cookie value to >>> apply a hidden filter to the search object (via the addHiddenFilter >>> method) in order to filter search results without affecting the visible >>> facet list. >>>> >>>> I think this is at least half of what you need. The branding piece >>> could be achieved through the UInterface class in web/sys/Interface.php >>> -- right now, the constructor loads the theme settings from config.ini, >>> but you could dynamically adjust the theme value based on the location >>> cookie. Since VuFind supports theme inheritance, you could then >>> override only the templates that need to be changed for each location's >>> needs; everything else would inherit from the base theme. There's more >>> on theme inheritance here if you are not already familiar with how it >>> works: >>>> >>>> http://vufind.org/wiki/customization >>>> >>>> I hope this helps get you started. Please let me know if you need >>> more specifics on anything. In the meantime, I will see if I can get a >>> copy of the latest existing library selection code to share with you. >>>> >>>> - Demian >>>> >>>>> -----Original Message----- >>>>> From: John Wynstra [mailto:joh...@un...] >>>>> Sent: Tuesday, June 21, 2011 9:50 AM >>>>> To: vuf...@li... >>>>> Subject: [VuFind-Tech] Mutli-Site Architecture >>>>> >>>>> We have been experimenting with vufind for a few months, and my task >>>>> this summer is to get a vufind instance that implements a >>>>> multi-interface site allowing for significant unique branding of >>> each >>>>> library's interface. My question is what is the best way to do this >>> at >>>>> both the data level (indexing) and at the presentation layer with >>>>> vufind. Any guidance or pointers would be appreciated. >>>>> >>>>> The vufind prototype that I am experimenting with is here: >>>>> http://vhost1.lib.uni.edu/vufind/ >>>>> >>>>> I have looked at a couple of mutli-library(MnPALS and Marmot) sites >>>>> already, but I want to do more than change the banner at the top >>> when >>>>> looking at an individual library. >>>>> >>>>> MnPALS: http://plus.mnpals.net/ >>>>> St. Cloud State University: >>> http://plus.mnpals.net/vufind/catalog/SCS >>>>> >>>>> -------------------------------------------------------------------- >>> --- >>>>> Some Background >>>>> -------------------------------------------------------------------- >>> --- >>>>> >>>>> We are a consortium of 9 libraries that share a single Innovative >>>>> Interfaces(III) catalog. We utilize III's scoping feature to allow >>>>> each >>>>> library to have a uniquely branded interface that searches its own >>>>> records by default, but allows for searching the whole catalog if >>>>> selected. The scoping feature is integrated at the record level >>>>> (indexing) and is integrated into the presentation layer via >>>>> proprietary hooks and configuration settings. Each scope in our >>>>> consortium represents an individual library and all of its unique >>>>> locations (reference, stacks, gov docs, etc.) >>>>> >>>>> Here are 4 different interfaces to our III catalog. >>>>> >>>>> * Cedar Valley Library Consortium: http://unistar.uni.edu/ >>>>> * University of Northern Iowa: http://unistar.uni.edu/search~S1/ >>>>> * Waterloo Public: http://unistar.uni.edu/search~S7/ >>>>> * Wartburg College: http://unistar.uni.edu/search~S9/ >>>>> >>>>> -- >>>>> <><><><><><><><><><><><><><><><><><><> >>>>> John Wynstra >>>>> Library Information Systems Specialist >>>>> Rod Library >>>>> University of Northern Iowa >>>>> Cedar Falls, IA 50613 >>>>> wy...@un... >>>>> (319)273-6399 >>>>> <><><><><><><><><><><><><><><><><><><> >>>>> >>>>> -------------------------------------------------------------------- >>> --- >>>>> ------- >>>>> EditLive Enterprise is the world's most technically advanced content >>>>> authoring tool. Experience the power of Track Changes, Inline Image >>>>> Editing and ensure content is compliant with Accessibility Checking. >>>>> http://p.sf.net/sfu/ephox-dev2dev >>>>> _______________________________________________ >>>>> Vufind-tech mailing list >>>>> Vuf...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/vufind-tech >>>> >>>> >>> >>> -- >>> <><><><><><><><><><><><><><><><><><><> >>> John Wynstra >>> Library Information Systems Specialist >>> Rod Library >>> University of Northern Iowa >>> Cedar Falls, IA 50613 >>> wy...@un... >>> (319)273-6399 >>> <><><><><><><><><><><><><><><><><><><> >> >> > -- <><><><><><><><><><><><><><><><><><><> John Wynstra Library Information Systems Specialist Rod Library University of Northern Iowa Cedar Falls, IA 50613 wy...@un... (319)273-6399 <><><><><><><><><><><><><><><><><><><> |