From: Ranju U. <Ran...@nu...> - 2012-07-10 09:23:30
|
Hi Demian, This is quite interesting, yesterday I made changes in several files to enable Dewey and disable LOC. I modified config.ini to use Dewey for browse. I modified facets.ini to use dewey-hundreds.I also modified the Advanced section of the same file to use dewey. I modified searches.ini to sort the results by dewey. And all of that worked for me except for the basic search. For instance in my simple search box I put 8 and then selected the limiter to be call number thinking this would bring back all the records whose call number start with 8 i.e. 810 etc but it said no results fould. And then I put a term music in the simple search box and used the limiter call number and that returned some results for me. So that made me think that that the limiter in simple search was still using loc rather that dewey call number. But this morning when I repeated the same thing , the result is the opposite!!!!vufind returned result when I used 8 and no result when I used music. So I think it is now using dewey instead of loc.But why was it so stubborn yesterday? I think I have seen similar behaviour when it has been very resistive to change when I was trying to use my computername instead of localhost in the url.It took a while for some of the links to start using computername and not localhost. Thanks Ranju. ----- Original Message ----- From: Demian Katz <dem...@vi...> Date: Monday, July 9, 2012 4:57 pm Subject: RE: [VuFind-General] dewey call number in basic search To: Ranju Upadhyay <Ran...@nu...>, "vuf...@li..." <vuf...@li...> <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --> ----------------------------------------------------------- | > The search options are defined in web/conf/searchspecs.yaml. If you look at the existing Call Number search definition, it should search both LC and Dewey. The default “All Fields” search is not designed to search call numbers at all, though you may pick up some incidental call number fragments from the “all fields” field. > > If this is not helpful, perhaps you could share some specific search URLs and expected results and I can look more closely to see what is going wrong. > > thanks, > Demian > > From: Ranju Upadhyay [mailto:Ran...@nu...] > Sent: Monday, July 09, 2012 11:10 AM > To: vuf...@li... > Subject: [VuFind-General] dewey call number in basic search > > Hi all, > > How can I get the basic search box drop down to use Dewey call number rather than LOC? I manged to enable dewey for other i.e. for browse and limiters in advanced search but the basic search box still seem to look for LOC rather than dewey. > > We are using Blueprint theme. > > Any ideas? > > Thanks > Ranju. |----------------------------------------------------------- |