From: Osullivan L. <L.O...@sw...> - 2012-05-21 13:23:05
|
Hi Folks, One of our subject librarians has asked us to change the way results are displayed when a callnumber search is performed. Basically, if someone searches for PQ239, she would like the results returned to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, PQ2390 etc At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our results... The problem I see it two fold - To get what she ideally wants, we'd need to restrict all callnumber search to exact matches using the callnumber-a field and then create more fields to provide sorting for the rest of the callnumber. Has anyone done something similar? Thanks, Luke |
From: Demian K. <dem...@vi...> - 2012-05-21 13:56:55
|
I'm copying this message to solrmarc-tech since I believe Naomi Dushay has done a lot of work with call numbers and might have some suggestions. (And maybe there are some other non-VuFind users out there who are doing fancy call number indexing as well). Another possibility might be to consider directing call number searches directly to the alphabetical browse module, which may provide functionality closer to what is expected. - Demian > -----Original Message----- > From: Osullivan L. [mailto:L.O...@sw...] > Sent: Monday, May 21, 2012 9:22 AM > To: vuf...@li...; vuf...@li... > Subject: [VuFind-General] Call Number Searching / Browsing > > Hi Folks, > > One of our subject librarians has asked us to change the way results are > displayed when a callnumber search is performed. > > Basically, if someone searches for PQ239, she would like the results returned > to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, PQ2390 etc > > At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our > results... > > The problem I see it two fold - To get what she ideally wants, we'd need to > restrict all callnumber search to exact matches using the callnumber-a field > and then create more fields to provide sorting for the rest of the callnumber. > Has anyone done something similar? > > Thanks, > > Luke > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: Osullivan L. <L.O...@sw...> - 2012-05-21 14:36:35
|
Hi Demian, Thanks for that - ideally, I think we want the functionality of the Alphabetical Browse module but with items listed as the search results. Cheers, Luke ________________________________________ From: Demian Katz [dem...@vi...] Sent: 21 May 2012 14:56 To: Osullivan L.; vuf...@li...; vuf...@li... Cc: sol...@go... Subject: RE: Call Number Searching / Browsing I'm copying this message to solrmarc-tech since I believe Naomi Dushay has done a lot of work with call numbers and might have some suggestions. (And maybe there are some other non-VuFind users out there who are doing fancy call number indexing as well). Another possibility might be to consider directing call number searches directly to the alphabetical browse module, which may provide functionality closer to what is expected. - Demian > -----Original Message----- > From: Osullivan L. [mailto:L.O...@sw...] > Sent: Monday, May 21, 2012 9:22 AM > To: vuf...@li...; vuf...@li... > Subject: [VuFind-General] Call Number Searching / Browsing > > Hi Folks, > > One of our subject librarians has asked us to change the way results are > displayed when a callnumber search is performed. > > Basically, if someone searches for PQ239, she would like the results returned > to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, PQ2390 etc > > At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our > results... > > The problem I see it two fold - To get what she ideally wants, we'd need to > restrict all callnumber search to exact matches using the callnumber-a field > and then create more fields to provide sorting for the rest of the callnumber. > Has anyone done something similar? > > Thanks, > > Luke > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: Demian K. <dem...@vi...> - 2012-05-21 14:51:31
|
It might be interesting to see what happens if you create an alphabrowse index which uses title as the main field but callnumber as the sort field. That might or might not get you the functionality you desire. (If it's close but not exactly right, perhaps a little tweaking of the Java code could get it the rest of the way). - Demian > -----Original Message----- > From: Osullivan L. [mailto:L.O...@sw...] > Sent: Monday, May 21, 2012 10:36 AM > To: Demian Katz; vuf...@li...; vufind- > ge...@li... > Cc: sol...@go... > Subject: RE: Call Number Searching / Browsing > > Hi Demian, > > Thanks for that - ideally, I think we want the functionality of the > Alphabetical Browse module but with items listed as the search results. > > Cheers, > > Luke > ________________________________________ > From: Demian Katz [dem...@vi...] > Sent: 21 May 2012 14:56 > To: Osullivan L.; vuf...@li...; vufind- > ge...@li... > Cc: sol...@go... > Subject: RE: Call Number Searching / Browsing > > I'm copying this message to solrmarc-tech since I believe Naomi Dushay has > done a lot of work with call numbers and might have some suggestions. (And > maybe there are some other non-VuFind users out there who are doing fancy call > number indexing as well). > > Another possibility might be to consider directing call number searches > directly to the alphabetical browse module, which may provide functionality > closer to what is expected. > > - Demian > > > -----Original Message----- > > From: Osullivan L. [mailto:L.O...@sw...] > > Sent: Monday, May 21, 2012 9:22 AM > > To: vuf...@li...; vuf...@li... > > Subject: [VuFind-General] Call Number Searching / Browsing > > > > Hi Folks, > > > > One of our subject librarians has asked us to change the way results are > > displayed when a callnumber search is performed. > > > > Basically, if someone searches for PQ239, she would like the results > returned > > to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, PQ2390 > etc > > > > At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our > > results... > > > > The problem I see it two fold - To get what she ideally wants, we'd need to > > restrict all callnumber search to exact matches using the callnumber-a field > > and then create more fields to provide sorting for the rest of the > callnumber. > > Has anyone done something similar? > > > > Thanks, > > > > Luke > > ---------------------------------------------------------------------------- > -- > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > VuFind-General mailing list > > VuF...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: Tod O. <to...@uc...> - 2012-05-21 15:52:30
|
Luke, In our current discovery tool, we've adopted NCSU's virtual shelf browse, and have it configured sort of like a results page: http://vshelf.lib.uchicago.edu/browse/?callNumber=HD8072.5%20.R58%202010 Is that the sort of thing you mean? -Tod On May 21, 2012, at 9:40 AM, Demian Katz wrote: > It might be interesting to see what happens if you create an alphabrowse index which uses title as the main field but callnumber as the sort field. That might or might not get you the functionality you desire. (If it's close but not exactly right, perhaps a little tweaking of the Java code could get it the rest of the way). > > - Demian > >> -----Original Message----- >> From: Osullivan L. [mailto:L.O...@sw...] >> Sent: Monday, May 21, 2012 10:36 AM >> To: Demian Katz; vuf...@li...; vufind- >> ge...@li... >> Cc: sol...@go... >> Subject: RE: Call Number Searching / Browsing >> >> Hi Demian, >> >> Thanks for that - ideally, I think we want the functionality of the >> Alphabetical Browse module but with items listed as the search results. >> >> Cheers, >> >> Luke >> ________________________________________ >> From: Demian Katz [dem...@vi...] >> Sent: 21 May 2012 14:56 >> To: Osullivan L.; vuf...@li...; vufind- >> ge...@li... >> Cc: sol...@go... >> Subject: RE: Call Number Searching / Browsing >> >> I'm copying this message to solrmarc-tech since I believe Naomi Dushay has >> done a lot of work with call numbers and might have some suggestions. (And >> maybe there are some other non-VuFind users out there who are doing fancy call >> number indexing as well). >> >> Another possibility might be to consider directing call number searches >> directly to the alphabetical browse module, which may provide functionality >> closer to what is expected. >> >> - Demian >> >>> -----Original Message----- >>> From: Osullivan L. [mailto:L.O...@sw...] >>> Sent: Monday, May 21, 2012 9:22 AM >>> To: vuf...@li...; vuf...@li... >>> Subject: [VuFind-General] Call Number Searching / Browsing >>> >>> Hi Folks, >>> >>> One of our subject librarians has asked us to change the way results are >>> displayed when a callnumber search is performed. >>> >>> Basically, if someone searches for PQ239, she would like the results >> returned >>> to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, PQ2390 >> etc >>> >>> At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our >>> results... >>> >>> The problem I see it two fold - To get what she ideally wants, we'd need to >>> restrict all callnumber search to exact matches using the callnumber-a field >>> and then create more fields to provide sorting for the rest of the >> callnumber. >>> Has anyone done something similar? >>> >>> Thanks, >>> >>> Luke >>> ---------------------------------------------------------------------------- >> -- >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> VuFind-General mailing list >>> VuF...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-general > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: Robert H. <rh...@vi...> - 2012-05-21 18:55:28
|
In SolrMarc in the Utils class there is a method that Naomi Dushay created that takes a LC call number and transforms it into an expanded version that should be directly sortable. So for a random sampling of records with LC call numbers "near" PQ239 PQ239.Z56 PQ239.H63 2008 PQ239.S62 1982 PQ239.B68 1983 PQ2390.S35 A5 PQ2390.S35 B8 1898 PQ2389 .R65 F3 1854 t.1 PQ239.A7 1969 PQ2.N6 1959 PQ22.A4 D47 1949 PQ238.L57 1985 the expanded sortable version returned by Naomi's routine would be:- PQ 0239.000000 Z0.560000 PQ 0239.000000 H0.630000 002008 PQ 0239.000000 S0.620000 001982 PQ 0239.000000 B0.680000 001983 PQ 2390.000000 S0.350000 A0.500000 PQ 2390.000000 S0.350000 B0.800000 001898 PQ 2389.000000 R0.650000 F0.300000 001854 T.000001 PQ 0002.000000 N0.600000 001959 PQ 0022.000000 A0.400000 D0.470000 001949 PQ 0238.000000 L0.570000 001985 Which is easily sorted to produce the desired ordering. I don't know whether there is an existing "standard" indexing function that invokes the CallNumUtils.getLCShelfkey() method that produces the above expanded strings, but it could be easily added as a custom method, or as a scripted method. -Bob Haschart On 5/21/2012 10:40 AM, Demian Katz wrote: > It might be interesting to see what happens if you create an alphabrowse index which uses title as the main field but callnumber as the sort field. That might or might not get you the functionality you desire. (If it's close but not exactly right, perhaps a little tweaking of the Java code could get it the rest of the way). > > - Demian > >> -----Original Message----- >> From: Osullivan L. [mailto:L.O...@sw...] >> Sent: Monday, May 21, 2012 10:36 AM >> To: Demian Katz; vuf...@li...; vufind- >> ge...@li... >> Cc: sol...@go... >> Subject: RE: Call Number Searching / Browsing >> >> Hi Demian, >> >> Thanks for that - ideally, I think we want the functionality of the >> Alphabetical Browse module but with items listed as the search results. >> >> Cheers, >> >> Luke >> ________________________________________ >> From: Demian Katz [dem...@vi...] >> Sent: 21 May 2012 14:56 >> To: Osullivan L.; vuf...@li...; vufind- >> ge...@li... >> Cc: sol...@go... >> Subject: RE: Call Number Searching / Browsing >> >> I'm copying this message to solrmarc-tech since I believe Naomi Dushay has >> done a lot of work with call numbers and might have some suggestions. (And >> maybe there are some other non-VuFind users out there who are doing fancy call >> number indexing as well). >> >> Another possibility might be to consider directing call number searches >> directly to the alphabetical browse module, which may provide functionality >> closer to what is expected. >> >> - Demian >> >>> -----Original Message----- >>> From: Osullivan L. [mailto:L.O...@sw...] >>> Sent: Monday, May 21, 2012 9:22 AM >>> To: vuf...@li...; vuf...@li... >>> Subject: [VuFind-General] Call Number Searching / Browsing >>> >>> Hi Folks, >>> >>> One of our subject librarians has asked us to change the way results are >>> displayed when a callnumber search is performed. >>> >>> Basically, if someone searches for PQ239, she would like the results >> returned >>> to be PQ239, PQ239> ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, PQ2390 >> etc >>> At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our >>> results... >>> >>> The problem I see it two fold - To get what she ideally wants, we'd need to >>> restrict all callnumber search to exact matches using the callnumber-a field >>> and then create more fields to provide sorting for the rest of the >> callnumber. >>> Has anyone done something similar? >>> >>> Thanks, >>> >>> Luke >>> ---------------------------------------------------------------------------- >> -- >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> VuFind-General mailing list >>> VuF...@li... >>> https://lists.sourceforge.net/lists/listinfo/vufind-general > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: Osullivan L. <L.O...@sw...> - 2013-01-11 11:35:23
|
Hi Tod, Apologies for the delay in replying - I lost this e-mail in the mountain of e-mails I had after the New Year. I have managed to get the items to display in the correct order with some custom indexing but I hit a snag with the ultimate goal of my attempts which was to add call number range searching. getFullNormalizedLCCN.bsh import org.marc4j.marc.Record; import org.solrmarc.tools.CallNumUtils; org.solrmarc.index.SolrIndexer indexer = null; /** * Normalize a single LCCN * @param lccn * @return Normalized LCCN */ public String getFullNormalizedLCCN(Record record, String lccn) { if (lccn != null) { lccn = indexer.getFirstFieldVal(record, lccn); String recordID = "1"; // Need to assign real value from record? if (lccn != null) { String normal = CallNumUtils.getLCShelfkey(lccn, recordID); if (normal != null) { // Send back normalized LCCN: return normal; } } } // If we got this far, we couldn't find a valid value: return null; } marc_local.properties callnumber-norm_str= script(getFullNormalizedLCCN.bsh), getFullNormalizedLCCN(852hi) schema.xml <field name="callnumber-search" type="string" indexed="true" stored="true"/> searches.ini [Sorting] ; Use the "callnumber" line for LC or the "dewey-sort" line for Dewey Decimal. ; If you want to enable both systems for sorting, you can uncomment both lines, ; but you will need to add some custom text to distinguish between the two. callnumber-norm_str = sort_callnumber [DefaultSortingByType] CallNumber = callnumber-norm_str Cheers, Luke On 12/27/2012 02:36 PM, Tod Olson wrote: Luke, Did you ever come up with a solution to this problem? We're in a similar way, wanting the call number browse to reflect call number shelving order. -Tod On May 21, 2012, at 8:22 AM, Osullivan L. <L.O...@sw...><mailto:L.O...@sw...> wrote: Hi Folks, One of our subject librarians has asked us to change the way results are displayed when a callnumber search is performed. Basically, if someone searches for PQ239, she would like the results returned to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, PQ2390 etc At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our results... The problem I see it two fold - To get what she ideally wants, we'd need to restrict all callnumber search to exact matches using the callnumber-a field and then create more fields to provide sorting for the rest of the callnumber. Has anyone done something similar? Thanks, Luke ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ VuFind-General mailing list VuF...@li...<mailto:VuF...@li...> https://lists.sourceforge.net/lists/listinfo/vufind-general -- Luke O'Sullivan Systems Developer Web Team Swansea University, Singleton Park, Swansea SA2 8PP, UK l.o...@sw...<mailto:l.o...@sw...> 01792 602772 @l_os_cymru |
From: Nathan T. <nta...@gm...> - 2013-01-11 14:30:08
|
On a related, but separate note, we'd like a similar feature. Most of our call numbers are really collection numbers, and sometimes expressed as ranges in the MARC record (099 field). For example, "MS-564" or "SC-5464 to SC-5468". The default call number sorting (in alpha browse) doesn't really work for our records, because you get things like, MS-1, MS-10, MS-100 instead of MS-1, MS-2, and so on. We'd like to have the second scenario work out. And perhaps add the title in the display as well. The other, and more relevant note, has to do with ranges. When a MARC record has SC-5464 to SC-5468 and someone searches SC-5465, they get no results. Would it be possible to return the record with SC-5464 to SC-5468? Our old OPAC did this. The tricky wicket is that ranges are not always entered the same way. Sometimes it's what I've already described (using "to") and sometimes it's a hyphen (SC-5464-SC5468 or SC-5464-5648). I think I've been told the first scenario is doable, I've just no idea how to do it. Not sure if the second is possible, given that the way ranges are expressed varies in the records. Thanks! Nathan On Fri, Jan 11, 2013 at 6:34 AM, Osullivan L. <L.O...@sw...> wrote: > Hi Tod, > > Apologies for the delay in replying - I lost this e-mail in the mountain of > e-mails I had after the New Year. > > I have managed to get the items to display in the correct order with some > custom indexing but I hit a snag with the ultimate goal of my attempts which > was to add call number range searching. > > getFullNormalizedLCCN.bsh > > import org.marc4j.marc.Record; > import org.solrmarc.tools.CallNumUtils; > org.solrmarc.index.SolrIndexer indexer = null; > > /** > * Normalize a single LCCN > * @param lccn > * @return Normalized LCCN > */ > public String getFullNormalizedLCCN(Record record, String lccn) { > > if (lccn != null) { > > lccn = indexer.getFirstFieldVal(record, lccn); > > String recordID = "1"; // Need to assign real value from record? > > if (lccn != null) { > > String normal = CallNumUtils.getLCShelfkey(lccn, recordID); > > if (normal != null) { > // Send back normalized LCCN: > return normal; > } > } > } > > // If we got this far, we couldn't find a valid value: > return null; > } > > marc_local.properties > callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > getFullNormalizedLCCN(852hi) > > schema.xml > <field name="callnumber-search" type="string" indexed="true" stored="true"/> > > searches.ini > [Sorting] > ; Use the "callnumber" line for LC or the "dewey-sort" line for Dewey > Decimal. > ; If you want to enable both systems for sorting, you can uncomment both > lines, > ; but you will need to add some custom text to distinguish between the two. > callnumber-norm_str = sort_callnumber > > [DefaultSortingByType] > CallNumber = callnumber-norm_str > > Cheers, > > Luke > > On 12/27/2012 02:36 PM, Tod Olson wrote: > > Luke, > > Did you ever come up with a solution to this problem? > > We're in a similar way, wanting the call number browse to reflect call > number shelving order. > > -Tod > > On May 21, 2012, at 8:22 AM, Osullivan L. <L.O...@sw...> wrote: > > Hi Folks, > > One of our subject librarians has asked us to change the way results are > displayed when a callnumber search is performed. > > Basically, if someone searches for PQ239, she would like the results > returned to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, > PQ2390 etc > > At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our > results... > > The problem I see it two fold - To get what she ideally wants, we'd need to > restrict all callnumber search to exact matches using the callnumber-a field > and then create more fields to provide sorting for the rest of the > callnumber. Has anyone done something similar? > > Thanks, > > Luke > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ______________________________ > _________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general > > > -- > Luke O'Sullivan > Systems Developer > Web Team > Swansea University, Singleton Park, Swansea SA2 8PP, UK > l.o...@sw... > 01792 602772 > @l_os_cymru > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > |
From: Alan R. <ala...@mn...> - 2013-01-11 14:43:30
|
Hello, I've been working with Mark Triggs' AlphaBrowse code and have the AlphaBrowse working for call numbers. The one issue I'm having problems with is seeding into the correct spot. I plan on looking at that next week. But the full call numbers are sorting in order. I've added code to bring in any additional fields you might want from the records. At this time I'm adding the titles to the display in the browse screen. Today I'm rebuilding my Solr db on a machine that could use more memory. The indexing job will not finish until tomorrow or Sunday. Monday I'll have my sites up where you can see this. This won't allow you to search on a range, but you can browse through the numbers. al On Fri, 2013-01-11 at 11:34 +0000, Osullivan L. wrote: > Hi Tod, > > Apologies for the delay in replying - I lost this e-mail in the > mountain of e-mails I had after the New Year. > > I have managed to get the items to display in the correct order with > some custom indexing but I hit a snag with the ultimate goal of my > attempts which was to add call number range searching. > > getFullNormalizedLCCN.bsh > > import org.marc4j.marc.Record; > import org.solrmarc.tools.CallNumUtils; > org.solrmarc.index.SolrIndexer indexer = null; > > /** > * Normalize a single LCCN > * @param lccn > * @return Normalized LCCN > */ > public String getFullNormalizedLCCN(Record record, String lccn) { > > if (lccn != null) { > > lccn = indexer.getFirstFieldVal(record, lccn); > > String recordID = "1"; // Need to assign real value from > record? > > if (lccn != null) { > > String normal = CallNumUtils.getLCShelfkey(lccn, recordID); > > if (normal != null) { > // Send back normalized LCCN: > return normal; > } > } > } > > // If we got this far, we couldn't find a valid value: > return null; > } > > marc_local.properties > callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > getFullNormalizedLCCN(852hi) > > schema.xml > <field name="callnumber-search" type="string" indexed="true" > stored="true"/> > > searches.ini > [Sorting] > ; Use the "callnumber" line for LC or the "dewey-sort" line for Dewey > Decimal. > ; If you want to enable both systems for sorting, you can uncomment > both lines, > ; but you will need to add some custom text to distinguish between the > two. > callnumber-norm_str = sort_callnumber > > [DefaultSortingByType] > CallNumber = callnumber-norm_str > > Cheers, > > Luke > > On 12/27/2012 02:36 PM, Tod Olson wrote: > > > Luke, > > > > Did you ever come up with a solution to this problem? > > > > We're in a similar way, wanting the call number browse to reflect call number shelving order. > > > > -Tod > > > > On May 21, 2012, at 8:22 AM, Osullivan L. <L.O...@sw...> wrote: > > > > > Hi Folks, > > > > > > One of our subject librarians has asked us to change the way results are displayed when a callnumber search is performed. > > > > > > Basically, if someone searches for PQ239, she would like the results returned to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, PQ2390 etc > > > > > > At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our results... > > > > > > The problem I see it two fold - To get what she ideally wants, we'd need to restrict all callnumber search to exact matches using the callnumber-a field and then create more fields to provide sorting for the rest of the callnumber. Has anyone done something similar? > > > > > > Thanks, > > > > > > Luke > > > ------------------------------------------------------------------------------ > > > Live Security Virtual Conference > > > Exclusive live event will cover all the ways today's security and > > > threat landscape has changed and how IT managers can respond. Discussions > > > will include endpoint security, mobile security and the latest in malware > > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > > > VuFind-General mailing list > > > VuF...@li... > > > https://lists.sourceforge.net/lists/listinfo/vufind-general > > -- > Luke O'Sullivan > Systems Developer > Web Team > Swansea University, Singleton Park, Swansea SA2 8PP, UK > l.o...@sw... > 01792 602772 > @l_os_cymru > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > 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... "It's hard to lead a cavalry charge if you think you look funny on a horse" ~ Adlai Stevenson |
From: Demian K. <dem...@vi...> - 2013-01-11 14:50:14
|
I think you can solve all of these problems with custom indexing scripts. To get sorting right, you need a function that normalizes call numbers into a sortable format. e.g. explode on the hyphen, then pad the number with zeroes to a fixed length. (Obviously for this to work best, you would need separate fields for displaying vs. sorting call numbers). To get the ranges right, you would need a function that takes in the single call number string and converts it into an array of call number values... i.e. input = "SC-5464-SC-5468", output = array("SC-5464", "SC-5465", "SC-5466", "SC-5467", "SC-5468"). To address the inconsistency, your function would just need to be able to handle all the different cases (and perhaps throw an exception if it doesn't understand the string in order to help you find cases you're not already aware of). Easier said than done, I realize, but definitely possible. - Demian ________________________________________ From: Nathan Tallman [nta...@gm...] Sent: Friday, January 11, 2013 9:29 AM To: Osullivan L. Cc: vuf...@li... Subject: Re: [VuFind-Tech] [VuFind-General] Call Number Searching / Browsing On a related, but separate note, we'd like a similar feature. Most of our call numbers are really collection numbers, and sometimes expressed as ranges in the MARC record (099 field). For example, "MS-564" or "SC-5464 to SC-5468". The default call number sorting (in alpha browse) doesn't really work for our records, because you get things like, MS-1, MS-10, MS-100 instead of MS-1, MS-2, and so on. We'd like to have the second scenario work out. And perhaps add the title in the display as well. The other, and more relevant note, has to do with ranges. When a MARC record has SC-5464 to SC-5468 and someone searches SC-5465, they get no results. Would it be possible to return the record with SC-5464 to SC-5468? Our old OPAC did this. The tricky wicket is that ranges are not always entered the same way. Sometimes it's what I've already described (using "to") and sometimes it's a hyphen (SC-5464-SC5468 or SC-5464-5648). I think I've been told the first scenario is doable, I've just no idea how to do it. Not sure if the second is possible, given that the way ranges are expressed varies in the records. Thanks! Nathan On Fri, Jan 11, 2013 at 6:34 AM, Osullivan L. <L.O...@sw...> wrote: > Hi Tod, > > Apologies for the delay in replying - I lost this e-mail in the mountain of > e-mails I had after the New Year. > > I have managed to get the items to display in the correct order with some > custom indexing but I hit a snag with the ultimate goal of my attempts which > was to add call number range searching. > > getFullNormalizedLCCN.bsh > > import org.marc4j.marc.Record; > import org.solrmarc.tools.CallNumUtils; > org.solrmarc.index.SolrIndexer indexer = null; > > /** > * Normalize a single LCCN > * @param lccn > * @return Normalized LCCN > */ > public String getFullNormalizedLCCN(Record record, String lccn) { > > if (lccn != null) { > > lccn = indexer.getFirstFieldVal(record, lccn); > > String recordID = "1"; // Need to assign real value from record? > > if (lccn != null) { > > String normal = CallNumUtils.getLCShelfkey(lccn, recordID); > > if (normal != null) { > // Send back normalized LCCN: > return normal; > } > } > } > > // If we got this far, we couldn't find a valid value: > return null; > } > > marc_local.properties > callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > getFullNormalizedLCCN(852hi) > > schema.xml > <field name="callnumber-search" type="string" indexed="true" stored="true"/> > > searches.ini > [Sorting] > ; Use the "callnumber" line for LC or the "dewey-sort" line for Dewey > Decimal. > ; If you want to enable both systems for sorting, you can uncomment both > lines, > ; but you will need to add some custom text to distinguish between the two. > callnumber-norm_str = sort_callnumber > > [DefaultSortingByType] > CallNumber = callnumber-norm_str > > Cheers, > > Luke > > On 12/27/2012 02:36 PM, Tod Olson wrote: > > Luke, > > Did you ever come up with a solution to this problem? > > We're in a similar way, wanting the call number browse to reflect call > number shelving order. > > -Tod > > On May 21, 2012, at 8:22 AM, Osullivan L. <L.O...@sw...> wrote: > > Hi Folks, > > One of our subject librarians has asked us to change the way results are > displayed when a callnumber search is performed. > > Basically, if someone searches for PQ239, she would like the results > returned to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, > PQ2390 etc > > At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our > results... > > The problem I see it two fold - To get what she ideally wants, we'd need to > restrict all callnumber search to exact matches using the callnumber-a field > and then create more fields to provide sorting for the rest of the > callnumber. Has anyone done something similar? > > Thanks, > > Luke > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ______________________________ > _________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general > > > -- > Luke O'Sullivan > Systems Developer > Web Team > Swansea University, Singleton Park, Swansea SA2 8PP, UK > l.o...@sw... > 01792 602772 > @l_os_cymru > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Vufind-tech mailing list Vuf...@li... https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Demian K. <dem...@vi...> - 2013-01-11 14:51:16
|
Oh, one other important detail -- obviously this would require a multi-valued call number field. Since you can't sort on a multi-valued field, that's another reason you'll need separate fields for sorting vs. searching/displaying. - Demian ________________________________________ From: Demian Katz Sent: Friday, January 11, 2013 9:50 AM To: Nathan Tallman; Osullivan L. Cc: vuf...@li... Subject: RE: [VuFind-Tech] [VuFind-General] Call Number Searching / Browsing I think you can solve all of these problems with custom indexing scripts. To get sorting right, you need a function that normalizes call numbers into a sortable format. e.g. explode on the hyphen, then pad the number with zeroes to a fixed length. (Obviously for this to work best, you would need separate fields for displaying vs. sorting call numbers). To get the ranges right, you would need a function that takes in the single call number string and converts it into an array of call number values... i.e. input = "SC-5464-SC-5468", output = array("SC-5464", "SC-5465", "SC-5466", "SC-5467", "SC-5468"). To address the inconsistency, your function would just need to be able to handle all the different cases (and perhaps throw an exception if it doesn't understand the string in order to help you find cases you're not already aware of). Easier said than done, I realize, but definitely possible. - Demian ________________________________________ From: Nathan Tallman [nta...@gm...] Sent: Friday, January 11, 2013 9:29 AM To: Osullivan L. Cc: vuf...@li... Subject: Re: [VuFind-Tech] [VuFind-General] Call Number Searching / Browsing On a related, but separate note, we'd like a similar feature. Most of our call numbers are really collection numbers, and sometimes expressed as ranges in the MARC record (099 field). For example, "MS-564" or "SC-5464 to SC-5468". The default call number sorting (in alpha browse) doesn't really work for our records, because you get things like, MS-1, MS-10, MS-100 instead of MS-1, MS-2, and so on. We'd like to have the second scenario work out. And perhaps add the title in the display as well. The other, and more relevant note, has to do with ranges. When a MARC record has SC-5464 to SC-5468 and someone searches SC-5465, they get no results. Would it be possible to return the record with SC-5464 to SC-5468? Our old OPAC did this. The tricky wicket is that ranges are not always entered the same way. Sometimes it's what I've already described (using "to") and sometimes it's a hyphen (SC-5464-SC5468 or SC-5464-5648). I think I've been told the first scenario is doable, I've just no idea how to do it. Not sure if the second is possible, given that the way ranges are expressed varies in the records. Thanks! Nathan On Fri, Jan 11, 2013 at 6:34 AM, Osullivan L. <L.O...@sw...> wrote: > Hi Tod, > > Apologies for the delay in replying - I lost this e-mail in the mountain of > e-mails I had after the New Year. > > I have managed to get the items to display in the correct order with some > custom indexing but I hit a snag with the ultimate goal of my attempts which > was to add call number range searching. > > getFullNormalizedLCCN.bsh > > import org.marc4j.marc.Record; > import org.solrmarc.tools.CallNumUtils; > org.solrmarc.index.SolrIndexer indexer = null; > > /** > * Normalize a single LCCN > * @param lccn > * @return Normalized LCCN > */ > public String getFullNormalizedLCCN(Record record, String lccn) { > > if (lccn != null) { > > lccn = indexer.getFirstFieldVal(record, lccn); > > String recordID = "1"; // Need to assign real value from record? > > if (lccn != null) { > > String normal = CallNumUtils.getLCShelfkey(lccn, recordID); > > if (normal != null) { > // Send back normalized LCCN: > return normal; > } > } > } > > // If we got this far, we couldn't find a valid value: > return null; > } > > marc_local.properties > callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > getFullNormalizedLCCN(852hi) > > schema.xml > <field name="callnumber-search" type="string" indexed="true" stored="true"/> > > searches.ini > [Sorting] > ; Use the "callnumber" line for LC or the "dewey-sort" line for Dewey > Decimal. > ; If you want to enable both systems for sorting, you can uncomment both > lines, > ; but you will need to add some custom text to distinguish between the two. > callnumber-norm_str = sort_callnumber > > [DefaultSortingByType] > CallNumber = callnumber-norm_str > > Cheers, > > Luke > > On 12/27/2012 02:36 PM, Tod Olson wrote: > > Luke, > > Did you ever come up with a solution to this problem? > > We're in a similar way, wanting the call number browse to reflect call > number shelving order. > > -Tod > > On May 21, 2012, at 8:22 AM, Osullivan L. <L.O...@sw...> wrote: > > Hi Folks, > > One of our subject librarians has asked us to change the way results are > displayed when a callnumber search is performed. > > Basically, if someone searches for PQ239, she would like the results > returned to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, > PQ2390 etc > > At present, we are getting a lot of PQ2391, PQ2392 etc at the top of our > results... > > The problem I see it two fold - To get what she ideally wants, we'd need to > restrict all callnumber search to exact matches using the callnumber-a field > and then create more fields to provide sorting for the rest of the > callnumber. Has anyone done something similar? > > Thanks, > > Luke > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ______________________________ > _________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general > > > -- > Luke O'Sullivan > Systems Developer > Web Team > Swansea University, Singleton Park, Swansea SA2 8PP, UK > l.o...@sw... > 01792 602772 > @l_os_cymru > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Vufind-tech mailing list Vuf...@li... https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: anna h. <an...@gm...> - 2013-02-07 19:54:13
|
Hi Alan, Any additional detail on what you did to accomplish this would be greatly appreciated. Is all your work in AlphaBrowse? Did you also create / change indexing rules? How are you normalizing the user input? We'd like to do this based on the browse functionality, as well, and then enhance that page to show more info about each item. Anna On Fri, Jan 11, 2013 at 9:43 AM, Alan Rykhus <ala...@mn...> wrote: > Hello, > > I've been working with Mark Triggs' AlphaBrowse code and have the > AlphaBrowse working for call numbers. > > The one issue I'm having problems with is seeding into the correct spot. > I plan on looking at that next week. But the full call numbers are > sorting in order. I've added code to bring in any additional fields you > might want from the records. At this time I'm adding the titles to the > display in the browse screen. > > Today I'm rebuilding my Solr db on a machine that could use more memory. > The indexing job will not finish until tomorrow or Sunday. Monday I'll > have my sites up where you can see this. > > This won't allow you to search on a range, but you can browse through > the numbers. > > al > > > On Fri, 2013-01-11 at 11:34 +0000, Osullivan L. wrote: > > Hi Tod, > > > > Apologies for the delay in replying - I lost this e-mail in the > > mountain of e-mails I had after the New Year. > > > > I have managed to get the items to display in the correct order with > > some custom indexing but I hit a snag with the ultimate goal of my > > attempts which was to add call number range searching. > > > > getFullNormalizedLCCN.bsh > > > > import org.marc4j.marc.Record; > > import org.solrmarc.tools.CallNumUtils; > > org.solrmarc.index.SolrIndexer indexer = null; > > > > /** > > * Normalize a single LCCN > > * @param lccn > > * @return Normalized LCCN > > */ > > public String getFullNormalizedLCCN(Record record, String lccn) { > > > > if (lccn != null) { > > > > lccn = indexer.getFirstFieldVal(record, lccn); > > > > String recordID = "1"; // Need to assign real value from > > record? > > > > if (lccn != null) { > > > > String normal = CallNumUtils.getLCShelfkey(lccn, recordID); > > > > if (normal != null) { > > // Send back normalized LCCN: > > return normal; > > } > > } > > } > > > > // If we got this far, we couldn't find a valid value: > > return null; > > } > > > > marc_local.properties > > callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > > getFullNormalizedLCCN(852hi) > > > > schema.xml > > <field name="callnumber-search" type="string" indexed="true" > > stored="true"/> > > > > searches.ini > > [Sorting] > > ; Use the "callnumber" line for LC or the "dewey-sort" line for Dewey > > Decimal. > > ; If you want to enable both systems for sorting, you can uncomment > > both lines, > > ; but you will need to add some custom text to distinguish between the > > two. > > callnumber-norm_str = sort_callnumber > > > > [DefaultSortingByType] > > CallNumber = callnumber-norm_str > > > > Cheers, > > > > Luke > > > > On 12/27/2012 02:36 PM, Tod Olson wrote: > > > > > Luke, > > > > > > Did you ever come up with a solution to this problem? > > > > > > We're in a similar way, wanting the call number browse to reflect call > number shelving order. > > > > > > -Tod > > > > > > On May 21, 2012, at 8:22 AM, Osullivan L. <L.O...@sw...> > wrote: > > > > > > > Hi Folks, > > > > > > > > One of our subject librarians has asked us to change the way results > are displayed when a callnumber search is performed. > > > > > > > > Basically, if someone searches for PQ239, she would like the results > returned to be PQ239, PQ239 > ABC, PQ239 .A22 2011, PQ239 .W55 2011, PQ240, > PQ2390 etc > > > > > > > > At present, we are getting a lot of PQ2391, PQ2392 etc at the top of > our results... > > > > > > > > The problem I see it two fold - To get what she ideally wants, we'd > need to restrict all callnumber search to exact matches using the > callnumber-a field and then create more fields to provide sorting for the > rest of the callnumber. Has anyone done something similar? > > > > > > > > Thanks, > > > > > > > > Luke > > > > > ------------------------------------------------------------------------------ > > > > Live Security Virtual Conference > > > > Exclusive live event will cover all the ways today's security and > > > > threat landscape has changed and how IT managers can respond. > Discussions > > > > will include endpoint security, mobile security and the latest in > malware > > > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > _______________________________________________ > > > > VuFind-General mailing list > > > > VuF...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vufind-general > > > > -- > > Luke O'Sullivan > > Systems Developer > > Web Team > > Swansea University, Singleton Park, Swansea SA2 8PP, UK > > l.o...@sw... > > 01792 602772 > > @l_os_cymru > > > ------------------------------------------------------------------------------ > > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > > much more. Get web development skills now with LearnDevNow - > > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > > SALE $99.99 this month only -- learn more at: > > http://p.sf.net/sfu/learnmore_122812 > > _______________________________________________ > > 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... > "It's hard to lead a cavalry charge if you think you look funny on a > horse" ~ Adlai Stevenson > > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > |
From: Alan R. <ala...@mn...> - 2013-02-07 20:45:26
|
Hello Anna, I was sure I posted a tarball to JIRA, but I can't find it. oh well Here is a README of what I changed: What needs to be done to implement the new Alphabetic Browse functionality? 1. Indexing * biblio/conf/schema.xml * change topic_browse and author_browse to stored=true * marc_local.properties * callnumber * uses getFullCallNumber from callnumber.bsh * This is for searching and is the default as delivered in Vufind * callnumber-norm_str * uses getFullCallNumberNormalized * need to add to callnumber.bsh * uses org.solrmarc.tools.CallNumUtils function * callnumber_display_str * uses getFullCallNumberDisplay * need to add to callnumber.bsh * same as getFullCallNumber, just do not strip spaces * name needs to be a '_', Smarty does not like '-'s * biblio/conf/solrconfig.xml * For the lcc configuration use callnumber instead of callnumber-a 2. New jar files * browse-indexing.jar * put in /srv/vufind/import * browse-handler.jar * put in /srv/vufind/solr/lib 3. New sqlite build scripts * Build all indexes using StoredFieldLeech * I don't have auth library, don't know what effect this will have * topic_browse * author_browse * callnumber instead callnumber-a * This is a full call number field * callnumber-norm_str for sort field * New parameter -Dbuildfield * This builds an additional field in sqlite to allow limits to an institution * Can be omitted if you do not need a limit 4. config.ini change * new section [AlphaBrowse_Extras] * Allows you to retrieve additional fields from database for display purposes * I use it to get the callnumber_display_str and title fields for the call numbers 5. web/sys/Solr.php * altered function alphabeticBrowse to handle new parameters 6. web/services/AlphaBrowse/Results.php * Altered code to handle new config and page parameters 7. web/interface/themes/mnpals/AlphaBrowse/home.tpl * links are different * When browsing forward and back, the rowid is in the link from the initial browse * Additions to display extra fields 8. web/interface/themes/mnpals/css/styles.css * added .alphaBrowseLCCHeading and .alphaBrowseTitleHeading entries for callnumber table If you have more questions, let me know. al On Thu, 2013-02-07 at 14:53 -0500, anna headley wrote: > Hi Alan, > > > Any additional detail on what you did to accomplish this would be > greatly appreciated. > > > Is all your work in AlphaBrowse? Did you also create / change > indexing rules? How are you normalizing the user input? > > > We'd like to do this based on the browse functionality, as well, and > then enhance that page to show more info about each item. > > > Anna > > > > > On Fri, Jan 11, 2013 at 9:43 AM, Alan Rykhus <ala...@mn...> > wrote: > Hello, > > I've been working with Mark Triggs' AlphaBrowse code and have > the > AlphaBrowse working for call numbers. > > The one issue I'm having problems with is seeding into the > correct spot. > I plan on looking at that next week. But the full call numbers > are > sorting in order. I've added code to bring in any additional > fields you > might want from the records. At this time I'm adding the > titles to the > display in the browse screen. > > Today I'm rebuilding my Solr db on a machine that could use > more memory. > The indexing job will not finish until tomorrow or Sunday. > Monday I'll > have my sites up where you can see this. > > This won't allow you to search on a range, but you can browse > through > the numbers. > > al > > > On Fri, 2013-01-11 at 11:34 +0000, Osullivan L. wrote: > > Hi Tod, > > > > Apologies for the delay in replying - I lost this e-mail in > the > > mountain of e-mails I had after the New Year. > > > > I have managed to get the items to display in the correct > order with > > some custom indexing but I hit a snag with the ultimate goal > of my > > attempts which was to add call number range searching. > > > > getFullNormalizedLCCN.bsh > > > > import org.marc4j.marc.Record; > > import org.solrmarc.tools.CallNumUtils; > > org.solrmarc.index.SolrIndexer indexer = null; > > > > /** > > * Normalize a single LCCN > > * @param lccn > > * @return Normalized LCCN > > */ > > public String getFullNormalizedLCCN(Record record, String > lccn) { > > > > if (lccn != null) { > > > > lccn = indexer.getFirstFieldVal(record, lccn); > > > > String recordID = "1"; // Need to assign real value > from > > record? > > > > if (lccn != null) { > > > > String normal = CallNumUtils.getLCShelfkey(lccn, > recordID); > > > > if (normal != null) { > > // Send back normalized LCCN: > > return normal; > > } > > } > > } > > > > // If we got this far, we couldn't find a valid value: > > return null; > > } > > > > marc_local.properties > > callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > > getFullNormalizedLCCN(852hi) > > > > schema.xml > > <field name="callnumber-search" type="string" indexed="true" > > stored="true"/> > > > > searches.ini > > [Sorting] > > ; Use the "callnumber" line for LC or the "dewey-sort" line > for Dewey > > Decimal. > > ; If you want to enable both systems for sorting, you can > uncomment > > both lines, > > ; but you will need to add some custom text to distinguish > between the > > two. > > callnumber-norm_str = sort_callnumber > > > > [DefaultSortingByType] > > CallNumber = callnumber-norm_str > > > > Cheers, > > > > Luke > > > > On 12/27/2012 02:36 PM, Tod Olson wrote: > > > > > Luke, > > > > > > Did you ever come up with a solution to this problem? > > > > > > We're in a similar way, wanting the call number browse to > reflect call number shelving order. > > > > > > -Tod > > > > > > On May 21, 2012, at 8:22 AM, Osullivan L. > <L.O...@sw...> wrote: > > > > > > > Hi Folks, > > > > > > > > One of our subject librarians has asked us to change the > way results are displayed when a callnumber search is > performed. > > > > > > > > Basically, if someone searches for PQ239, she would like > the results returned to be PQ239, PQ239 > ABC, PQ239 .A22 > 2011, PQ239 .W55 2011, PQ240, PQ2390 etc > > > > > > > > At present, we are getting a lot of PQ2391, PQ2392 etc > at the top of our results... > > > > > > > > The problem I see it two fold - To get what she ideally > wants, we'd need to restrict all callnumber search to exact > matches using the callnumber-a field and then create more > fields to provide sorting for the rest of the callnumber. Has > anyone done something similar? > > > > > > > > Thanks, > > > > > > > > Luke > > > > > ------------------------------------------------------------------------------ > > > > Live Security Virtual Conference > > > > Exclusive live event will cover all the ways today's > security and > > > > threat landscape has changed and how IT managers can > respond. Discussions > > > > will include endpoint security, mobile security and the > latest in malware > > > > threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > _______________________________________________ > > > > VuFind-General mailing list > > > > VuF...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/vufind-general > > > > -- > > Luke O'Sullivan > > Systems Developer > > Web Team > > Swansea University, Singleton Park, Swansea SA2 8PP, UK > > l.o...@sw... > > 01792 602772 > > @l_os_cymru > > > > ------------------------------------------------------------------------------ > > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API > and > > much more. Get web development skills now with LearnDevNow - > > 350+ hours of step-by-step video tutorials by Microsoft MVPs > and experts. > > SALE $99.99 this month only -- learn more at: > > http://p.sf.net/sfu/learnmore_122812 > > > _______________________________________________ > > 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... > "It's hard to lead a cavalry charge if you think you look > funny on a > horse" ~ Adlai Stevenson > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API > and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs > and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > > _______________________________________________ > 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... "Be pleasant until ten o'clock in the morning and the rest of the day will take care of itself." ~ Elbert Hubbard |
From: Tod O. <to...@uc...> - 2013-02-20 01:38:13
|
I think that's attached to VUFIND-726: http://vufind.org/jira/browse/VUFIND-726 It looks like these changes would be of great use to my site, especially the business of returning additional fields in the browse search. I'd be interested in seeing these changes work their way into the trunk. Could probably put some time into in a few weeks. Is that of interest to you? -Tod On Feb 7, 2013, at 2:45 PM, Alan Rykhus <ala...@mn...> wrote: > Hello Anna, > > I was sure I posted a tarball to JIRA, but I can't find it. oh well > > Here is a README of what I changed: > > > What needs to be done to implement the new Alphabetic Browse > functionality? > > 1. Indexing > * biblio/conf/schema.xml > * change topic_browse and author_browse to > stored=true > * marc_local.properties > * callnumber > * uses getFullCallNumber from > callnumber.bsh > * This is for searching and is the default > as delivered in Vufind > * callnumber-norm_str > * uses getFullCallNumberNormalized > * need to add to callnumber.bsh > * uses > org.solrmarc.tools.CallNumUtils > function > * callnumber_display_str > * uses getFullCallNumberDisplay > * need to add to callnumber.bsh > * same as getFullCallNumber, just > do not strip spaces > * name needs to be a '_', Smarty > does not like '-'s > * biblio/conf/solrconfig.xml > * For the lcc configuration use callnumber instead > of callnumber-a > 2. New jar files > * browse-indexing.jar > * put in /srv/vufind/import > * browse-handler.jar > * put in /srv/vufind/solr/lib > 3. New sqlite build scripts > * Build all indexes using StoredFieldLeech > * I don't have auth library, don't know what effect this > will have > * topic_browse > * author_browse > * callnumber instead callnumber-a > * This is a full call number field > * callnumber-norm_str for sort field > * New parameter -Dbuildfield > * This builds an additional field in sqlite to > allow limits to an institution > * Can be omitted if you do not need a limit > 4. config.ini change > * new section [AlphaBrowse_Extras] > * Allows you to retrieve additional fields from > database for display purposes > * I use it to get the callnumber_display_str and > title fields for the call numbers > 5. web/sys/Solr.php > * altered function alphabeticBrowse to handle new > parameters > 6. web/services/AlphaBrowse/Results.php > * Altered code to handle new config and page parameters > 7. web/interface/themes/mnpals/AlphaBrowse/home.tpl > * links are different > * When browsing forward and back, the rowid is in > the link from the initial browse > * Additions to display extra fields > 8. web/interface/themes/mnpals/css/styles.css > * added .alphaBrowseLCCHeading > and .alphaBrowseTitleHeading entries for callnumber > table > > If you have more questions, let me know. > > al > > > On Thu, 2013-02-07 at 14:53 -0500, anna headley wrote: >> Hi Alan, >> >> >> Any additional detail on what you did to accomplish this would be >> greatly appreciated. >> >> >> Is all your work in AlphaBrowse? Did you also create / change >> indexing rules? How are you normalizing the user input? >> >> >> We'd like to do this based on the browse functionality, as well, and >> then enhance that page to show more info about each item. >> >> >> Anna >> >> >> >> >> On Fri, Jan 11, 2013 at 9:43 AM, Alan Rykhus <ala...@mn...> >> wrote: >> Hello, >> >> I've been working with Mark Triggs' AlphaBrowse code and have >> the >> AlphaBrowse working for call numbers. >> >> The one issue I'm having problems with is seeding into the >> correct spot. >> I plan on looking at that next week. But the full call numbers >> are >> sorting in order. I've added code to bring in any additional >> fields you >> might want from the records. At this time I'm adding the >> titles to the >> display in the browse screen. >> >> Today I'm rebuilding my Solr db on a machine that could use >> more memory. >> The indexing job will not finish until tomorrow or Sunday. >> Monday I'll >> have my sites up where you can see this. >> >> This won't allow you to search on a range, but you can browse >> through >> the numbers. >> >> al >> >> >> On Fri, 2013-01-11 at 11:34 +0000, Osullivan L. wrote: >>> Hi Tod, >>> >>> Apologies for the delay in replying - I lost this e-mail in >> the >>> mountain of e-mails I had after the New Year. >>> >>> I have managed to get the items to display in the correct >> order with >>> some custom indexing but I hit a snag with the ultimate goal >> of my >>> attempts which was to add call number range searching. >>> >>> getFullNormalizedLCCN.bsh >>> >>> import org.marc4j.marc.Record; >>> import org.solrmarc.tools.CallNumUtils; >>> org.solrmarc.index.SolrIndexer indexer = null; >>> >>> /** >>> * Normalize a single LCCN >>> * @param lccn >>> * @return Normalized LCCN >>> */ >>> public String getFullNormalizedLCCN(Record record, String >> lccn) { >>> >>> if (lccn != null) { >>> >>> lccn = indexer.getFirstFieldVal(record, lccn); >>> >>> String recordID = "1"; // Need to assign real value >> from >>> record? >>> >>> if (lccn != null) { >>> >>> String normal = CallNumUtils.getLCShelfkey(lccn, >> recordID); >>> >>> if (normal != null) { >>> // Send back normalized LCCN: >>> return normal; >>> } >>> } >>> } >>> >>> // If we got this far, we couldn't find a valid value: >>> return null; >>> } >>> >>> marc_local.properties >>> callnumber-norm_str= script(getFullNormalizedLCCN.bsh), >>> getFullNormalizedLCCN(852hi) >>> >>> schema.xml >>> <field name="callnumber-search" type="string" indexed="true" >>> stored="true"/> >>> >>> searches.ini >>> [Sorting] >>> ; Use the "callnumber" line for LC or the "dewey-sort" line >> for Dewey >>> Decimal. >>> ; If you want to enable both systems for sorting, you can >> uncomment >>> both lines, >>> ; but you will need to add some custom text to distinguish >> between the >>> two. >>> callnumber-norm_str = sort_callnumber >>> >>> [DefaultSortingByType] >>> CallNumber = callnumber-norm_str >>> >>> Cheers, >>> >>> Luke >>> >>> On 12/27/2012 02:36 PM, Tod Olson wrote: >>> >>>> Luke, >>>> >>>> Did you ever come up with a solution to this problem? >>>> >>>> We're in a similar way, wanting the call number browse to >> reflect call number shelving order. >>>> >>>> -Tod >>>> >>>> On May 21, 2012, at 8:22 AM, Osullivan L. >> <L.O...@sw...> wrote: >>>> >>>>> Hi Folks, >>>>> >>>>> One of our subject librarians has asked us to change the >> way results are displayed when a callnumber search is >> performed. >>>>> >>>>> Basically, if someone searches for PQ239, she would like >> the results returned to be PQ239, PQ239 > ABC, PQ239 .A22 >> 2011, PQ239 .W55 2011, PQ240, PQ2390 etc >>>>> >>>>> At present, we are getting a lot of PQ2391, PQ2392 etc >> at the top of our results... >>>>> >>>>> The problem I see it two fold - To get what she ideally >> wants, we'd need to restrict all callnumber search to exact >> matches using the callnumber-a field and then create more >> fields to provide sorting for the rest of the callnumber. Has >> anyone done something similar? >>>>> >>>>> Thanks, >>>>> >>>>> Luke >>>>> >> ------------------------------------------------------------------------------ >>>>> Live Security Virtual Conference >>>>> Exclusive live event will cover all the ways today's >> security and >>>>> threat landscape has changed and how IT managers can >> respond. Discussions >>>>> will include endpoint security, mobile security and the >> latest in malware >>>>> threats. >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>> _______________________________________________ >>>>> VuFind-General mailing list >>>>> VuF...@li... >>>>> >> https://lists.sourceforge.net/lists/listinfo/vufind-general >>> >>> -- >>> Luke O'Sullivan >>> Systems Developer >>> Web Team >>> Swansea University, Singleton Park, Swansea SA2 8PP, UK >>> l.o...@sw... >>> 01792 602772 >>> @l_os_cymru >> >>> >> ------------------------------------------------------------------------------ >>> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API >> and >>> much more. Get web development skills now with LearnDevNow - >>> 350+ hours of step-by-step video tutorials by Microsoft MVPs >> and experts. >>> SALE $99.99 this month only -- learn more at: >>> http://p.sf.net/sfu/learnmore_122812 >> >>> _______________________________________________ >>> 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... >> "It's hard to lead a cavalry charge if you think you look >> funny on a >> horse" ~ Adlai Stevenson >> >> >> ------------------------------------------------------------------------------ >> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API >> and >> much more. Get web development skills now with LearnDevNow - >> 350+ hours of step-by-step video tutorials by Microsoft MVPs >> and experts. >> SALE $99.99 this month only -- learn more at: >> http://p.sf.net/sfu/learnmore_122812 >> >> _______________________________________________ >> 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... > "Be pleasant until ten o'clock in the morning and the rest of the day > will take care of itself." ~ Elbert Hubbard > > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: anna h. <an...@gm...> - 2013-02-20 17:04:49
|
Does anyone else have a situation where records could have multiple items with different call numbers? For example the item is held in multiple libraries in the consortium, and each has given it a different call number, or the item is held in the general collection as well as some other collection with its own special set of call numbers. Are you just arbitrarily choosing one call number to use as the sort value? This would mean the item would only show up in one place in the browse list. I'm thinking of adding another index field that holds a tuple of (sort, display) call number values so that I can match between them when needed. (Well, it couldn't be an actual tuple, but some sort of parseable string.) Is anyone else doing something like this? Something smarter than this? Thanks! Anna On Tue, Feb 19, 2013 at 8:38 PM, Tod Olson <to...@uc...> wrote: > I think that's attached to VUFIND-726: > > http://vufind.org/jira/browse/VUFIND-726 > > It looks like these changes would be of great use to my site, especially > the business of returning additional fields in the browse search. I'd be > interested in seeing these changes work their way into the trunk. Could > probably put some time into in a few weeks. Is that of interest to you? > > -Tod > > > On Feb 7, 2013, at 2:45 PM, Alan Rykhus <ala...@mn...> wrote: > > > Hello Anna, > > > > I was sure I posted a tarball to JIRA, but I can't find it. oh well > > > > Here is a README of what I changed: > > > > > > What needs to be done to implement the new Alphabetic Browse > > functionality? > > > > 1. Indexing > > * biblio/conf/schema.xml > > * change topic_browse and author_browse to > > stored=true > > * marc_local.properties > > * callnumber > > * uses getFullCallNumber from > > callnumber.bsh > > * This is for searching and is the default > > as delivered in Vufind > > * callnumber-norm_str > > * uses getFullCallNumberNormalized > > * need to add to callnumber.bsh > > * uses > > org.solrmarc.tools.CallNumUtils > > function > > * callnumber_display_str > > * uses getFullCallNumberDisplay > > * need to add to callnumber.bsh > > * same as getFullCallNumber, just > > do not strip spaces > > * name needs to be a '_', Smarty > > does not like '-'s > > * biblio/conf/solrconfig.xml > > * For the lcc configuration use callnumber instead > > of callnumber-a > > 2. New jar files > > * browse-indexing.jar > > * put in /srv/vufind/import > > * browse-handler.jar > > * put in /srv/vufind/solr/lib > > 3. New sqlite build scripts > > * Build all indexes using StoredFieldLeech > > * I don't have auth library, don't know what effect this > > will have > > * topic_browse > > * author_browse > > * callnumber instead callnumber-a > > * This is a full call number field > > * callnumber-norm_str for sort field > > * New parameter -Dbuildfield > > * This builds an additional field in sqlite to > > allow limits to an institution > > * Can be omitted if you do not need a limit > > 4. config.ini change > > * new section [AlphaBrowse_Extras] > > * Allows you to retrieve additional fields from > > database for display purposes > > * I use it to get the callnumber_display_str and > > title fields for the call numbers > > 5. web/sys/Solr.php > > * altered function alphabeticBrowse to handle new > > parameters > > 6. web/services/AlphaBrowse/Results.php > > * Altered code to handle new config and page parameters > > 7. web/interface/themes/mnpals/AlphaBrowse/home.tpl > > * links are different > > * When browsing forward and back, the rowid is in > > the link from the initial browse > > * Additions to display extra fields > > 8. web/interface/themes/mnpals/css/styles.css > > * added .alphaBrowseLCCHeading > > and .alphaBrowseTitleHeading entries for callnumber > > table > > > > If you have more questions, let me know. > > > > al > > > > > > On Thu, 2013-02-07 at 14:53 -0500, anna headley wrote: > >> Hi Alan, > >> > >> > >> Any additional detail on what you did to accomplish this would be > >> greatly appreciated. > >> > >> > >> Is all your work in AlphaBrowse? Did you also create / change > >> indexing rules? How are you normalizing the user input? > >> > >> > >> We'd like to do this based on the browse functionality, as well, and > >> then enhance that page to show more info about each item. > >> > >> > >> Anna > >> > >> > >> > >> > >> On Fri, Jan 11, 2013 at 9:43 AM, Alan Rykhus <ala...@mn...> > >> wrote: > >> Hello, > >> > >> I've been working with Mark Triggs' AlphaBrowse code and have > >> the > >> AlphaBrowse working for call numbers. > >> > >> The one issue I'm having problems with is seeding into the > >> correct spot. > >> I plan on looking at that next week. But the full call numbers > >> are > >> sorting in order. I've added code to bring in any additional > >> fields you > >> might want from the records. At this time I'm adding the > >> titles to the > >> display in the browse screen. > >> > >> Today I'm rebuilding my Solr db on a machine that could use > >> more memory. > >> The indexing job will not finish until tomorrow or Sunday. > >> Monday I'll > >> have my sites up where you can see this. > >> > >> This won't allow you to search on a range, but you can browse > >> through > >> the numbers. > >> > >> al > >> > >> > >> On Fri, 2013-01-11 at 11:34 +0000, Osullivan L. wrote: > >>> Hi Tod, > >>> > >>> Apologies for the delay in replying - I lost this e-mail in > >> the > >>> mountain of e-mails I had after the New Year. > >>> > >>> I have managed to get the items to display in the correct > >> order with > >>> some custom indexing but I hit a snag with the ultimate goal > >> of my > >>> attempts which was to add call number range searching. > >>> > >>> getFullNormalizedLCCN.bsh > >>> > >>> import org.marc4j.marc.Record; > >>> import org.solrmarc.tools.CallNumUtils; > >>> org.solrmarc.index.SolrIndexer indexer = null; > >>> > >>> /** > >>> * Normalize a single LCCN > >>> * @param lccn > >>> * @return Normalized LCCN > >>> */ > >>> public String getFullNormalizedLCCN(Record record, String > >> lccn) { > >>> > >>> if (lccn != null) { > >>> > >>> lccn = indexer.getFirstFieldVal(record, lccn); > >>> > >>> String recordID = "1"; // Need to assign real value > >> from > >>> record? > >>> > >>> if (lccn != null) { > >>> > >>> String normal = CallNumUtils.getLCShelfkey(lccn, > >> recordID); > >>> > >>> if (normal != null) { > >>> // Send back normalized LCCN: > >>> return normal; > >>> } > >>> } > >>> } > >>> > >>> // If we got this far, we couldn't find a valid value: > >>> return null; > >>> } > >>> > >>> marc_local.properties > >>> callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > >>> getFullNormalizedLCCN(852hi) > >>> > >>> schema.xml > >>> <field name="callnumber-search" type="string" indexed="true" > >>> stored="true"/> > >>> > >>> searches.ini > >>> [Sorting] > >>> ; Use the "callnumber" line for LC or the "dewey-sort" line > >> for Dewey > >>> Decimal. > >>> ; If you want to enable both systems for sorting, you can > >> uncomment > >>> both lines, > >>> ; but you will need to add some custom text to distinguish > >> between the > >>> two. > >>> callnumber-norm_str = sort_callnumber > >>> > >>> [DefaultSortingByType] > >>> CallNumber = callnumber-norm_str > >>> > >>> Cheers, > >>> > >>> Luke > >>> > >>> On 12/27/2012 02:36 PM, Tod Olson wrote: > >>> > >>>> Luke, > >>>> > >>>> Did you ever come up with a solution to this problem? > >>>> > >>>> We're in a similar way, wanting the call number browse to > >> reflect call number shelving order. > >>>> > >>>> -Tod > >>>> > >>>> On May 21, 2012, at 8:22 AM, Osullivan L. > >> <L.O...@sw...> wrote: > >>>> > >>>>> Hi Folks, > >>>>> > >>>>> One of our subject librarians has asked us to change the > >> way results are displayed when a callnumber search is > >> performed. > >>>>> > >>>>> Basically, if someone searches for PQ239, she would like > >> the results returned to be PQ239, PQ239 > ABC, PQ239 .A22 > >> 2011, PQ239 .W55 2011, PQ240, PQ2390 etc > >>>>> > >>>>> At present, we are getting a lot of PQ2391, PQ2392 etc > >> at the top of our results... > >>>>> > >>>>> The problem I see it two fold - To get what she ideally > >> wants, we'd need to restrict all callnumber search to exact > >> matches using the callnumber-a field and then create more > >> fields to provide sorting for the rest of the callnumber. Has > >> anyone done something similar? > >>>>> > >>>>> Thanks, > >>>>> > >>>>> Luke > >>>>> > >> > ------------------------------------------------------------------------------ > >>>>> Live Security Virtual Conference > >>>>> Exclusive live event will cover all the ways today's > >> security and > >>>>> threat landscape has changed and how IT managers can > >> respond. Discussions > >>>>> will include endpoint security, mobile security and the > >> latest in malware > >>>>> threats. > >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > >>>>> _______________________________________________ > >>>>> VuFind-General mailing list > >>>>> VuF...@li... > >>>>> > >> https://lists.sourceforge.net/lists/listinfo/vufind-general > >>> > >>> -- > >>> Luke O'Sullivan > >>> Systems Developer > >>> Web Team > >>> Swansea University, Singleton Park, Swansea SA2 8PP, UK > >>> l.o...@sw... > >>> 01792 602772 > >>> @l_os_cymru > >> > >>> > >> > ------------------------------------------------------------------------------ > >>> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API > >> and > >>> much more. Get web development skills now with LearnDevNow - > >>> 350+ hours of step-by-step video tutorials by Microsoft MVPs > >> and experts. > >>> SALE $99.99 this month only -- learn more at: > >>> http://p.sf.net/sfu/learnmore_122812 > >> > >>> _______________________________________________ > >>> 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... > >> "It's hard to lead a cavalry charge if you think you look > >> funny on a > >> horse" ~ Adlai Stevenson > >> > >> > >> > ------------------------------------------------------------------------------ > >> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API > >> and > >> much more. Get web development skills now with LearnDevNow - > >> 350+ hours of step-by-step video tutorials by Microsoft MVPs > >> and experts. > >> SALE $99.99 this month only -- learn more at: > >> http://p.sf.net/sfu/learnmore_122812 > >> > >> _______________________________________________ > >> 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... > > "Be pleasant until ten o'clock in the morning and the rest of the day > > will take care of itself." ~ Elbert Hubbard > > > > > > > ------------------------------------------------------------------------------ > > Free Next-Gen Firewall Hardware Offer > > Buy your Sophos next-gen firewall before the end March 2013 > > and get the hardware for free! Learn more. > > http://p.sf.net/sfu/sophos-d2d-feb > > _______________________________________________ > > Vufind-tech mailing list > > Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > |
From: Demian K. <dem...@vi...> - 2013-02-20 17:16:39
|
The default configuration just arbitrarily picks the first call number for sorting purposes – this is necessary since Solr refuses to sort on multi-valued fields. When you refer to the browse list, do you mean the AlphaBrowse module? If so, it looks like the default configuration is currently using the same single sort value for building the browse index. However, AlphaBrowse can handle multi-valued fields, so you might be able to build the browse index using a different field, and then avoid having to do any wacky string-parsing stuff. Does that make sense, or am I missing the point? - Demian From: anna headley [mailto:an...@gm...] Sent: Wednesday, February 20, 2013 12:04 PM To: vuf...@li... Subject: Re: [VuFind-Tech] [VuFind-General] Call Number Searching / Browsing Does anyone else have a situation where records could have multiple items with different call numbers? For example the item is held in multiple libraries in the consortium, and each has given it a different call number, or the item is held in the general collection as well as some other collection with its own special set of call numbers. Are you just arbitrarily choosing one call number to use as the sort value? This would mean the item would only show up in one place in the browse list. I'm thinking of adding another index field that holds a tuple of (sort, display) call number values so that I can match between them when needed. (Well, it couldn't be an actual tuple, but some sort of parseable string.) Is anyone else doing something like this? Something smarter than this? Thanks! Anna On Tue, Feb 19, 2013 at 8:38 PM, Tod Olson <to...@uc...<mailto:to...@uc...>> wrote: I think that's attached to VUFIND-726: http://vufind.org/jira/browse/VUFIND-726 It looks like these changes would be of great use to my site, especially the business of returning additional fields in the browse search. I'd be interested in seeing these changes work their way into the trunk. Could probably put some time into in a few weeks. Is that of interest to you? -Tod On Feb 7, 2013, at 2:45 PM, Alan Rykhus <ala...@mn...<mailto:ala...@mn...>> wrote: > Hello Anna, > > I was sure I posted a tarball to JIRA, but I can't find it. oh well > > Here is a README of what I changed: > > > What needs to be done to implement the new Alphabetic Browse > functionality? > > 1. Indexing > * biblio/conf/schema.xml > * change topic_browse and author_browse to > stored=true > * marc_local.properties > * callnumber > * uses getFullCallNumber from > callnumber.bsh > * This is for searching and is the default > as delivered in Vufind > * callnumber-norm_str > * uses getFullCallNumberNormalized > * need to add to callnumber.bsh > * uses > org.solrmarc.tools.CallNumUtils > function > * callnumber_display_str > * uses getFullCallNumberDisplay > * need to add to callnumber.bsh > * same as getFullCallNumber, just > do not strip spaces > * name needs to be a '_', Smarty > does not like '-'s > * biblio/conf/solrconfig.xml > * For the lcc configuration use callnumber instead > of callnumber-a > 2. New jar files > * browse-indexing.jar > * put in /srv/vufind/import > * browse-handler.jar > * put in /srv/vufind/solr/lib > 3. New sqlite build scripts > * Build all indexes using StoredFieldLeech > * I don't have auth library, don't know what effect this > will have > * topic_browse > * author_browse > * callnumber instead callnumber-a > * This is a full call number field > * callnumber-norm_str for sort field > * New parameter -Dbuildfield > * This builds an additional field in sqlite to > allow limits to an institution > * Can be omitted if you do not need a limit > 4. config.ini change > * new section [AlphaBrowse_Extras] > * Allows you to retrieve additional fields from > database for display purposes > * I use it to get the callnumber_display_str and > title fields for the call numbers > 5. web/sys/Solr.php > * altered function alphabeticBrowse to handle new > parameters > 6. web/services/AlphaBrowse/Results.php > * Altered code to handle new config and page parameters > 7. web/interface/themes/mnpals/AlphaBrowse/home.tpl > * links are different > * When browsing forward and back, the rowid is in > the link from the initial browse > * Additions to display extra fields > 8. web/interface/themes/mnpals/css/styles.css > * added .alphaBrowseLCCHeading > and .alphaBrowseTitleHeading entries for callnumber > table > > If you have more questions, let me know. > > al > > > On Thu, 2013-02-07 at 14:53 -0500, anna headley wrote: >> Hi Alan, >> >> >> Any additional detail on what you did to accomplish this would be >> greatly appreciated. >> >> >> Is all your work in AlphaBrowse? Did you also create / change >> indexing rules? How are you normalizing the user input? >> >> >> We'd like to do this based on the browse functionality, as well, and >> then enhance that page to show more info about each item. >> >> >> Anna >> >> >> >> >> On Fri, Jan 11, 2013 at 9:43 AM, Alan Rykhus <ala...@mn...<mailto:ala...@mn...>> >> wrote: >> Hello, >> >> I've been working with Mark Triggs' AlphaBrowse code and have >> the >> AlphaBrowse working for call numbers. >> >> The one issue I'm having problems with is seeding into the >> correct spot. >> I plan on looking at that next week. But the full call numbers >> are >> sorting in order. I've added code to bring in any additional >> fields you >> might want from the records. At this time I'm adding the >> titles to the >> display in the browse screen. >> >> Today I'm rebuilding my Solr db on a machine that could use >> more memory. >> The indexing job will not finish until tomorrow or Sunday. >> Monday I'll >> have my sites up where you can see this. >> >> This won't allow you to search on a range, but you can browse >> through >> the numbers. >> >> al >> >> >> On Fri, 2013-01-11 at 11:34 +0000, Osullivan L. wrote: >>> Hi Tod, >>> >>> Apologies for the delay in replying - I lost this e-mail in >> the >>> mountain of e-mails I had after the New Year. >>> >>> I have managed to get the items to display in the correct >> order with >>> some custom indexing but I hit a snag with the ultimate goal >> of my >>> attempts which was to add call number range searching. >>> >>> getFullNormalizedLCCN.bsh >>> >>> import org.marc4j.marc.Record; >>> import org.solrmarc.tools.CallNumUtils; >>> org.solrmarc.index.SolrIndexer indexer = null; >>> >>> /** >>> * Normalize a single LCCN >>> * @param lccn >>> * @return Normalized LCCN >>> */ >>> public String getFullNormalizedLCCN(Record record, String >> lccn) { >>> >>> if (lccn != null) { >>> >>> lccn = indexer.getFirstFieldVal(record, lccn); >>> >>> String recordID = "1"; // Need to assign real value >> from >>> record? >>> >>> if (lccn != null) { >>> >>> String normal = CallNumUtils.getLCShelfkey(lccn, >> recordID); >>> >>> if (normal != null) { >>> // Send back normalized LCCN: >>> return normal; >>> } >>> } >>> } >>> >>> // If we got this far, we couldn't find a valid value: >>> return null; >>> } >>> >>> marc_local.properties >>> callnumber-norm_str= script(getFullNormalizedLCCN.bsh), >>> getFullNormalizedLCCN(852hi) >>> >>> schema.xml >>> <field name="callnumber-search" type="string" indexed="true" >>> stored="true"/> >>> >>> searches.ini >>> [Sorting] >>> ; Use the "callnumber" line for LC or the "dewey-sort" line >> for Dewey >>> Decimal. >>> ; If you want to enable both systems for sorting, you can >> uncomment >>> both lines, >>> ; but you will need to add some custom text to distinguish >> between the >>> two. >>> callnumber-norm_str = sort_callnumber >>> >>> [DefaultSortingByType] >>> CallNumber = callnumber-norm_str >>> >>> Cheers, >>> >>> Luke >>> >>> On 12/27/2012 02:36 PM, Tod Olson wrote: >>> >>>> Luke, >>>> >>>> Did you ever come up with a solution to this problem? >>>> >>>> We're in a similar way, wanting the call number browse to >> reflect call number shelving order. >>>> >>>> -Tod >>>> >>>> On May 21, 2012, at 8:22 AM, Osullivan L. >> <L.O...@sw...<mailto:L.O...@sw...>> wrote: >>>> >>>>> Hi Folks, >>>>> >>>>> One of our subject librarians has asked us to change the >> way results are displayed when a callnumber search is >> performed. >>>>> >>>>> Basically, if someone searches for PQ239, she would like >> the results returned to be PQ239, PQ239 > ABC, PQ239 .A22 >> 2011, PQ239 .W55 2011, PQ240, PQ2390 etc >>>>> >>>>> At present, we are getting a lot of PQ2391, PQ2392 etc >> at the top of our results... >>>>> >>>>> The problem I see it two fold - To get what she ideally >> wants, we'd need to restrict all callnumber search to exact >> matches using the callnumber-a field and then create more >> fields to provide sorting for the rest of the callnumber. Has >> anyone done something similar? >>>>> >>>>> Thanks, >>>>> >>>>> Luke >>>>> >> ------------------------------------------------------------------------------ >>>>> Live Security Virtual Conference >>>>> Exclusive live event will cover all the ways today's >> security and >>>>> threat landscape has changed and how IT managers can >> respond. Discussions >>>>> will include endpoint security, mobile security and the >> latest in malware >>>>> threats. >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>>>> _______________________________________________ >>>>> VuFind-General mailing list >>>>> VuF...@li...<mailto:VuF...@li...> >>>>> >> https://lists.sourceforge.net/lists/listinfo/vufind-general >>> >>> -- >>> Luke O'Sullivan >>> Systems Developer >>> Web Team >>> Swansea University, Singleton Park, Swansea SA2 8PP, UK >>> l.o...@sw...<mailto:l.o...@sw...> >>> 01792 602772 >>> @l_os_cymru >> >>> >> ------------------------------------------------------------------------------ >>> Master HTML5, CSS3, ASP.NET<http://ASP.NET>, MVC, AJAX, Knockout.js, Web API >> and >>> much more. Get web development skills now with LearnDevNow - >>> 350+ hours of step-by-step video tutorials by Microsoft MVPs >> and experts. >>> SALE $99.99 this month only -- learn more at: >>> http://p.sf.net/sfu/learnmore_122812 >> >>> _______________________________________________ >>> Vufind-tech mailing list >>> Vuf...@li...<mailto: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<tel:%28507%29389-1975> >> ala...@mn...<mailto:ala...@mn...> >> "It's hard to lead a cavalry charge if you think you look >> funny on a >> horse" ~ Adlai Stevenson >> >> >> ------------------------------------------------------------------------------ >> Master HTML5, CSS3, ASP.NET<http://ASP.NET>, MVC, AJAX, Knockout.js, Web API >> and >> much more. Get web development skills now with LearnDevNow - >> 350+ hours of step-by-step video tutorials by Microsoft MVPs >> and experts. >> SALE $99.99 this month only -- learn more at: >> http://p.sf.net/sfu/learnmore_122812 >> >> _______________________________________________ >> Vufind-tech mailing list >> Vuf...@li...<mailto: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<tel:%28507%29389-1975> > ala...@mn...<mailto:ala...@mn...> > "Be pleasant until ten o'clock in the morning and the rest of the day > will take care of itself." ~ Elbert Hubbard > > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li...<mailto:Vuf...@li...> > https://lists.sourceforge.net/lists/listinfo/vufind-tech ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Vufind-tech mailing list Vuf...@li...<mailto:Vuf...@li...> https://lists.sourceforge.net/lists/listinfo/vufind-tech |
From: Alan R. <ala...@mn...> - 2013-02-20 17:38:32
|
Hello Anna, Yes, we do. But it is easier to make things work with only a single entry. So we take just the first call number we find in our holding strings. I'm not sure if you can crawl a multi-value index in Solr. That's what is done to create the current Alphabetical browse databases. I see Demian posted a response too. The newer version of the Alphabetic browse uses a normailized call number index. If you can crawl the multi-values, it could be done. al On Wed, 2013-02-20 at 12:03 -0500, anna headley wrote: > Does anyone else have a situation where records could have multiple > items with different call numbers? For example the item is held in > multiple libraries in the consortium, and each has given it a > different call number, or the item is held in the general collection > as well as some other collection with its own special set of call > numbers. > > > Are you just arbitrarily choosing one call number to use as the sort > value? This would mean the item would only show up in one place in > the browse list. > > I'm thinking of adding another index field that holds a tuple of > (sort, display) call number values so that I can match between them > when needed. (Well, it couldn't be an actual tuple, but some sort of > parseable string.) > > Is anyone else doing something like this? Something smarter than > this? > > Thanks! > Anna > > > > > > On Tue, Feb 19, 2013 at 8:38 PM, Tod Olson <to...@uc...> wrote: > I think that's attached to VUFIND-726: > > http://vufind.org/jira/browse/VUFIND-726 > > It looks like these changes would be of great use to my site, > especially the business of returning additional fields in the > browse search. I'd be interested in seeing these changes work > their way into the trunk. Could probably put some time into in > a few weeks. Is that of interest to you? > > -Tod > > > On Feb 7, 2013, at 2:45 PM, Alan Rykhus <ala...@mn...> > wrote: > > > Hello Anna, > > > > I was sure I posted a tarball to JIRA, but I can't find it. > oh well > > > > Here is a README of what I changed: > > > > > > What needs to be done to implement the new Alphabetic Browse > > functionality? > > > > 1. Indexing > > * biblio/conf/schema.xml > > * change topic_browse and author_browse > to > > stored=true > > * marc_local.properties > > * callnumber > > * uses getFullCallNumber from > > callnumber.bsh > > * This is for searching and is > the default > > as delivered in Vufind > > * callnumber-norm_str > > * uses > getFullCallNumberNormalized > > * need to add to > callnumber.bsh > > * uses > > > org.solrmarc.tools.CallNumUtils > > function > > * callnumber_display_str > > * uses getFullCallNumberDisplay > > * need to add to > callnumber.bsh > > * same as > getFullCallNumber, just > > do not strip spaces > > * name needs to be a > '_', Smarty > > does not like '-'s > > * biblio/conf/solrconfig.xml > > * For the lcc configuration use > callnumber instead > > of callnumber-a > > 2. New jar files > > * browse-indexing.jar > > * put in /srv/vufind/import > > * browse-handler.jar > > * put in /srv/vufind/solr/lib > > 3. New sqlite build scripts > > * Build all indexes using StoredFieldLeech > > * I don't have auth library, don't know what > effect this > > will have > > * topic_browse > > * author_browse > > * callnumber instead callnumber-a > > * This is a full call number field > > * callnumber-norm_str for sort field > > * New parameter -Dbuildfield > > * This builds an additional field in > sqlite to > > allow limits to an institution > > * Can be omitted if you do not need a > limit > > 4. config.ini change > > * new section [AlphaBrowse_Extras] > > * Allows you to retrieve additional > fields from > > database for display purposes > > * I use it to get the > callnumber_display_str and > > title fields for the call numbers > > 5. web/sys/Solr.php > > * altered function alphabeticBrowse to handle > new > > parameters > > 6. web/services/AlphaBrowse/Results.php > > * Altered code to handle new config and page > parameters > > 7. web/interface/themes/mnpals/AlphaBrowse/home.tpl > > * links are different > > * When browsing forward and back, the > rowid is in > > the link from the initial browse > > * Additions to display extra fields > > 8. web/interface/themes/mnpals/css/styles.css > > * added .alphaBrowseLCCHeading > > and .alphaBrowseTitleHeading entries for > callnumber > > table > > > > If you have more questions, let me know. > > > > al > > > > > > On Thu, 2013-02-07 at 14:53 -0500, anna headley wrote: > >> Hi Alan, > >> > >> > >> Any additional detail on what you did to accomplish this > would be > >> greatly appreciated. > >> > >> > >> Is all your work in AlphaBrowse? Did you also create / > change > >> indexing rules? How are you normalizing the user input? > >> > >> > >> We'd like to do this based on the browse functionality, as > well, and > >> then enhance that page to show more info about each item. > >> > >> > >> Anna > >> > >> > >> > >> > >> On Fri, Jan 11, 2013 at 9:43 AM, Alan Rykhus > <ala...@mn...> > >> wrote: > >> Hello, > >> > >> I've been working with Mark Triggs' AlphaBrowse code > and have > >> the > >> AlphaBrowse working for call numbers. > >> > >> The one issue I'm having problems with is seeding > into the > >> correct spot. > >> I plan on looking at that next week. But the full > call numbers > >> are > >> sorting in order. I've added code to bring in any > additional > >> fields you > >> might want from the records. At this time I'm adding > the > >> titles to the > >> display in the browse screen. > >> > >> Today I'm rebuilding my Solr db on a machine that > could use > >> more memory. > >> The indexing job will not finish until tomorrow or > Sunday. > >> Monday I'll > >> have my sites up where you can see this. > >> > >> This won't allow you to search on a range, but you > can browse > >> through > >> the numbers. > >> > >> al > >> > >> > >> On Fri, 2013-01-11 at 11:34 +0000, Osullivan L. > wrote: > >>> Hi Tod, > >>> > >>> Apologies for the delay in replying - I lost this e-mail > in > >> the > >>> mountain of e-mails I had after the New Year. > >>> > >>> I have managed to get the items to display in the correct > >> order with > >>> some custom indexing but I hit a snag with the ultimate > goal > >> of my > >>> attempts which was to add call number range searching. > >>> > >>> getFullNormalizedLCCN.bsh > >>> > >>> import org.marc4j.marc.Record; > >>> import org.solrmarc.tools.CallNumUtils; > >>> org.solrmarc.index.SolrIndexer indexer = null; > >>> > >>> /** > >>> * Normalize a single LCCN > >>> * @param lccn > >>> * @return Normalized LCCN > >>> */ > >>> public String getFullNormalizedLCCN(Record record, String > >> lccn) { > >>> > >>> if (lccn != null) { > >>> > >>> lccn = indexer.getFirstFieldVal(record, lccn); > >>> > >>> String recordID = "1"; // Need to assign real value > >> from > >>> record? > >>> > >>> if (lccn != null) { > >>> > >>> String normal = CallNumUtils.getLCShelfkey(lccn, > >> recordID); > >>> > >>> if (normal != null) { > >>> // Send back normalized LCCN: > >>> return normal; > >>> } > >>> } > >>> } > >>> > >>> // If we got this far, we couldn't find a valid value: > >>> return null; > >>> } > >>> > >>> marc_local.properties > >>> callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > >>> getFullNormalizedLCCN(852hi) > >>> > >>> schema.xml > >>> <field name="callnumber-search" type="string" > indexed="true" > >>> stored="true"/> > >>> > >>> searches.ini > >>> [Sorting] > >>> ; Use the "callnumber" line for LC or the "dewey-sort" > line > >> for Dewey > >>> Decimal. > >>> ; If you want to enable both systems for sorting, you can > >> uncomment > >>> both lines, > >>> ; but you will need to add some custom text to distinguish > >> between the > >>> two. > >>> callnumber-norm_str = sort_callnumber > >>> > >>> [DefaultSortingByType] > >>> CallNumber = callnumber-norm_str > >>> > >>> Cheers, > >>> > >>> Luke > >>> > >>> On 12/27/2012 02:36 PM, Tod Olson wrote: > >>> > >>>> Luke, > >>>> > >>>> Did you ever come up with a solution to this problem? > >>>> > >>>> We're in a similar way, wanting the call number browse to > >> reflect call number shelving order. > >>>> > >>>> -Tod > >>>> > >>>> On May 21, 2012, at 8:22 AM, Osullivan L. > >> <L.O...@sw...> wrote: > >>>> > >>>>> Hi Folks, > >>>>> > >>>>> One of our subject librarians has asked us to change the > >> way results are displayed when a callnumber search > is > >> performed. > >>>>> > >>>>> Basically, if someone searches for PQ239, she would like > >> the results returned to be PQ239, PQ239 > ABC, > PQ239 .A22 > >> 2011, PQ239 .W55 2011, PQ240, PQ2390 etc > >>>>> > >>>>> At present, we are getting a lot of PQ2391, PQ2392 etc > >> at the top of our results... > >>>>> > >>>>> The problem I see it two fold - To get what she ideally > >> wants, we'd need to restrict all callnumber search > to exact > >> matches using the callnumber-a field and then create > more > >> fields to provide sorting for the rest of the > callnumber. Has > >> anyone done something similar? > >>>>> > >>>>> Thanks, > >>>>> > >>>>> Luke > >>>>> > >> > ------------------------------------------------------------------------------ > >>>>> Live Security Virtual Conference > >>>>> Exclusive live event will cover all the ways today's > >> security and > >>>>> threat landscape has changed and how IT managers can > >> respond. Discussions > >>>>> will include endpoint security, mobile security and the > >> latest in malware > >>>>> threats. > >> > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > >>>>> _______________________________________________ > >>>>> VuFind-General mailing list > >>>>> VuF...@li... > >>>>> > >> > https://lists.sourceforge.net/lists/listinfo/vufind-general > >>> > >>> -- > >>> Luke O'Sullivan > >>> Systems Developer > >>> Web Team > >>> Swansea University, Singleton Park, Swansea SA2 8PP, UK > >>> l.o...@sw... > >>> 01792 602772 > >>> @l_os_cymru > >> > >>> > >> > ------------------------------------------------------------------------------ > >>> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web > API > >> and > >>> much more. Get web development skills now with LearnDevNow > - > >>> 350+ hours of step-by-step video tutorials by Microsoft > MVPs > >> and experts. > >>> SALE $99.99 this month only -- learn more at: > >>> http://p.sf.net/sfu/learnmore_122812 > >> > >>> _______________________________________________ > >>> 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... > >> "It's hard to lead a cavalry charge if you think you > look > >> funny on a > >> horse" ~ Adlai Stevenson > >> > >> > >> > ------------------------------------------------------------------------------ > >> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, > Web API > >> and > >> much more. Get web development skills now with > LearnDevNow - > >> 350+ hours of step-by-step video tutorials by > Microsoft MVPs > >> and experts. > >> SALE $99.99 this month only -- learn more at: > >> http://p.sf.net/sfu/learnmore_122812 > >> > >> _______________________________________________ > >> 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... > > "Be pleasant until ten o'clock in the morning and the rest > of the day > > will take care of itself." ~ Elbert Hubbard > > > > > > > ------------------------------------------------------------------------------ > > Free Next-Gen Firewall Hardware Offer > > Buy your Sophos next-gen firewall before the end March 2013 > > and get the hardware for free! Learn more. > > http://p.sf.net/sfu/sophos-d2d-feb > > _______________________________________________ > > Vufind-tech mailing list > > Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > 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... "Be pleasant until ten o'clock in the morning and the rest of the day will take care of itself." ~ Elbert Hubbard |
From: anna h. <an...@gm...> - 2013-02-20 19:03:25
|
Thanks, Demian and Alan! Yes when I said browse I meant the alphabrowse module. Since solr can't sort on multiple fields, we are considering pointing all of our call number searches to the browse module, and beefing up the browseable list to include more information (titles, at least). The browse list would use the sort-normalized version of the call number (with all the padding zeroes), and a record would have multiple entries if it had multiple different call numbers. At which point I have two options: 1. Translate search queries into sort-normalized format to submit them. Then translate each sort-normalized call number back into something that could be displayed before showing to the user. 2. Store some sort of string-parsey quasi-tuple field, as I mentioned before, in order to be able to match a sort-normalized call number with the correct display value. I think this option is better because it won't cost a huge amount of space and it will save time when presenting the site. Also I wouldn't have to write all the code to translate the different types of call numbers back and forth. Alan's method of just grabbing the first call number if obviously way easier than any of this. Anna On Wed, Feb 20, 2013 at 12:38 PM, Alan Rykhus <ala...@mn...> wrote: > Hello Anna, > > Yes, we do. > > But it is easier to make things work with only a single entry. So we > take just the first call number we find in our holding strings. > > I'm not sure if you can crawl a multi-value index in Solr. That's what > is done to create the current Alphabetical browse databases. > > I see Demian posted a response too. The newer version of the Alphabetic > browse uses a normailized call number index. If you can crawl the > multi-values, it could be done. > > al > > On Wed, 2013-02-20 at 12:03 -0500, anna headley wrote: > > Does anyone else have a situation where records could have multiple > > items with different call numbers? For example the item is held in > > multiple libraries in the consortium, and each has given it a > > different call number, or the item is held in the general collection > > as well as some other collection with its own special set of call > > numbers. > > > > > > Are you just arbitrarily choosing one call number to use as the sort > > value? This would mean the item would only show up in one place in > > the browse list. > > > > I'm thinking of adding another index field that holds a tuple of > > (sort, display) call number values so that I can match between them > > when needed. (Well, it couldn't be an actual tuple, but some sort of > > parseable string.) > > > > Is anyone else doing something like this? Something smarter than > > this? > > > > Thanks! > > Anna > > > > > > > > > > > > On Tue, Feb 19, 2013 at 8:38 PM, Tod Olson <to...@uc...> wrote: > > I think that's attached to VUFIND-726: > > > > http://vufind.org/jira/browse/VUFIND-726 > > > > It looks like these changes would be of great use to my site, > > especially the business of returning additional fields in the > > browse search. I'd be interested in seeing these changes work > > their way into the trunk. Could probably put some time into in > > a few weeks. Is that of interest to you? > > > > -Tod > > > > > > On Feb 7, 2013, at 2:45 PM, Alan Rykhus <ala...@mn...> > > wrote: > > > > > Hello Anna, > > > > > > I was sure I posted a tarball to JIRA, but I can't find it. > > oh well > > > > > > Here is a README of what I changed: > > > > > > > > > What needs to be done to implement the new Alphabetic Browse > > > functionality? > > > > > > 1. Indexing > > > * biblio/conf/schema.xml > > > * change topic_browse and author_browse > > to > > > stored=true > > > * marc_local.properties > > > * callnumber > > > * uses getFullCallNumber from > > > callnumber.bsh > > > * This is for searching and is > > the default > > > as delivered in Vufind > > > * callnumber-norm_str > > > * uses > > getFullCallNumberNormalized > > > * need to add to > > callnumber.bsh > > > * uses > > > > > org.solrmarc.tools.CallNumUtils > > > function > > > * callnumber_display_str > > > * uses getFullCallNumberDisplay > > > * need to add to > > callnumber.bsh > > > * same as > > getFullCallNumber, just > > > do not strip spaces > > > * name needs to be a > > '_', Smarty > > > does not like '-'s > > > * biblio/conf/solrconfig.xml > > > * For the lcc configuration use > > callnumber instead > > > of callnumber-a > > > 2. New jar files > > > * browse-indexing.jar > > > * put in /srv/vufind/import > > > * browse-handler.jar > > > * put in /srv/vufind/solr/lib > > > 3. New sqlite build scripts > > > * Build all indexes using StoredFieldLeech > > > * I don't have auth library, don't know what > > effect this > > > will have > > > * topic_browse > > > * author_browse > > > * callnumber instead callnumber-a > > > * This is a full call number field > > > * callnumber-norm_str for sort field > > > * New parameter -Dbuildfield > > > * This builds an additional field in > > sqlite to > > > allow limits to an institution > > > * Can be omitted if you do not need a > > limit > > > 4. config.ini change > > > * new section [AlphaBrowse_Extras] > > > * Allows you to retrieve additional > > fields from > > > database for display purposes > > > * I use it to get the > > callnumber_display_str and > > > title fields for the call numbers > > > 5. web/sys/Solr.php > > > * altered function alphabeticBrowse to handle > > new > > > parameters > > > 6. web/services/AlphaBrowse/Results.php > > > * Altered code to handle new config and page > > parameters > > > 7. web/interface/themes/mnpals/AlphaBrowse/home.tpl > > > * links are different > > > * When browsing forward and back, the > > rowid is in > > > the link from the initial browse > > > * Additions to display extra fields > > > 8. web/interface/themes/mnpals/css/styles.css > > > * added .alphaBrowseLCCHeading > > > and .alphaBrowseTitleHeading entries for > > callnumber > > > table > > > > > > If you have more questions, let me know. > > > > > > al > > > > > > > > > On Thu, 2013-02-07 at 14:53 -0500, anna headley wrote: > > >> Hi Alan, > > >> > > >> > > >> Any additional detail on what you did to accomplish this > > would be > > >> greatly appreciated. > > >> > > >> > > >> Is all your work in AlphaBrowse? Did you also create / > > change > > >> indexing rules? How are you normalizing the user input? > > >> > > >> > > >> We'd like to do this based on the browse functionality, as > > well, and > > >> then enhance that page to show more info about each item. > > >> > > >> > > >> Anna > > >> > > >> > > >> > > >> > > >> On Fri, Jan 11, 2013 at 9:43 AM, Alan Rykhus > > <ala...@mn...> > > >> wrote: > > >> Hello, > > >> > > >> I've been working with Mark Triggs' AlphaBrowse code > > and have > > >> the > > >> AlphaBrowse working for call numbers. > > >> > > >> The one issue I'm having problems with is seeding > > into the > > >> correct spot. > > >> I plan on looking at that next week. But the full > > call numbers > > >> are > > >> sorting in order. I've added code to bring in any > > additional > > >> fields you > > >> might want from the records. At this time I'm adding > > the > > >> titles to the > > >> display in the browse screen. > > >> > > >> Today I'm rebuilding my Solr db on a machine that > > could use > > >> more memory. > > >> The indexing job will not finish until tomorrow or > > Sunday. > > >> Monday I'll > > >> have my sites up where you can see this. > > >> > > >> This won't allow you to search on a range, but you > > can browse > > >> through > > >> the numbers. > > >> > > >> al > > >> > > >> > > >> On Fri, 2013-01-11 at 11:34 +0000, Osullivan L. > > wrote: > > >>> Hi Tod, > > >>> > > >>> Apologies for the delay in replying - I lost this e-mail > > in > > >> the > > >>> mountain of e-mails I had after the New Year. > > >>> > > >>> I have managed to get the items to display in the correct > > >> order with > > >>> some custom indexing but I hit a snag with the ultimate > > goal > > >> of my > > >>> attempts which was to add call number range searching. > > >>> > > >>> getFullNormalizedLCCN.bsh > > >>> > > >>> import org.marc4j.marc.Record; > > >>> import org.solrmarc.tools.CallNumUtils; > > >>> org.solrmarc.index.SolrIndexer indexer = null; > > >>> > > >>> /** > > >>> * Normalize a single LCCN > > >>> * @param lccn > > >>> * @return Normalized LCCN > > >>> */ > > >>> public String getFullNormalizedLCCN(Record record, String > > >> lccn) { > > >>> > > >>> if (lccn != null) { > > >>> > > >>> lccn = indexer.getFirstFieldVal(record, lccn); > > >>> > > >>> String recordID = "1"; // Need to assign real value > > >> from > > >>> record? > > >>> > > >>> if (lccn != null) { > > >>> > > >>> String normal = CallNumUtils.getLCShelfkey(lccn, > > >> recordID); > > >>> > > >>> if (normal != null) { > > >>> // Send back normalized LCCN: > > >>> return normal; > > >>> } > > >>> } > > >>> } > > >>> > > >>> // If we got this far, we couldn't find a valid value: > > >>> return null; > > >>> } > > >>> > > >>> marc_local.properties > > >>> callnumber-norm_str= script(getFullNormalizedLCCN.bsh), > > >>> getFullNormalizedLCCN(852hi) > > >>> > > >>> schema.xml > > >>> <field name="callnumber-search" type="string" > > indexed="true" > > >>> stored="true"/> > > >>> > > >>> searches.ini > > >>> [Sorting] > > >>> ; Use the "callnumber" line for LC or the "dewey-sort" > > line > > >> for Dewey > > >>> Decimal. > > >>> ; If you want to enable both systems for sorting, you can > > >> uncomment > > >>> both lines, > > >>> ; but you will need to add some custom text to distinguish > > >> between the > > >>> two. > > >>> callnumber-norm_str = sort_callnumber > > >>> > > >>> [DefaultSortingByType] > > >>> CallNumber = callnumber-norm_str > > >>> > > >>> Cheers, > > >>> > > >>> Luke > > >>> > > >>> On 12/27/2012 02:36 PM, Tod Olson wrote: > > >>> > > >>>> Luke, > > >>>> > > >>>> Did you ever come up with a solution to this problem? > > >>>> > > >>>> We're in a similar way, wanting the call number browse to > > >> reflect call number shelving order. > > >>>> > > >>>> -Tod > > >>>> > > >>>> On May 21, 2012, at 8:22 AM, Osullivan L. > > >> <L.O...@sw...> wrote: > > >>>> > > >>>>> Hi Folks, > > >>>>> > > >>>>> One of our subject librarians has asked us to change the > > >> way results are displayed when a callnumber search > > is > > >> performed. > > >>>>> > > >>>>> Basically, if someone searches for PQ239, she would like > > >> the results returned to be PQ239, PQ239 > ABC, > > PQ239 .A22 > > >> 2011, PQ239 .W55 2011, PQ240, PQ2390 etc > > >>>>> > > >>>>> At present, we are getting a lot of PQ2391, PQ2392 etc > > >> at the top of our results... > > >>>>> > > >>>>> The problem I see it two fold - To get what she ideally > > >> wants, we'd need to restrict all callnumber search > > to exact > > >> matches using the callnumber-a field and then create > > more > > >> fields to provide sorting for the rest of the > > callnumber. Has > > >> anyone done something similar? > > >>>>> > > >>>>> Thanks, > > >>>>> > > >>>>> Luke > > >>>>> > > >> > > > ------------------------------------------------------------------------------ > > >>>>> Live Security Virtual Conference > > >>>>> Exclusive live event will cover all the ways today's > > >> security and > > >>>>> threat landscape has changed and how IT managers can > > >> respond. Discussions > > >>>>> will include endpoint security, mobile security and the > > >> latest in malware > > >>>>> threats. > > >> > > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > >>>>> _______________________________________________ > > >>>>> VuFind-General mailing list > > >>>>> VuF...@li... > > >>>>> > > >> > > https://lists.sourceforge.net/lists/listinfo/vufind-general > > >>> > > >>> -- > > >>> Luke O'Sullivan > > >>> Systems Developer > > >>> Web Team > > >>> Swansea University, Singleton Park, Swansea SA2 8PP, UK > > >>> l.o...@sw... > > >>> 01792 602772 > > >>> @l_os_cymru > > >> > > >>> > > >> > > > ------------------------------------------------------------------------------ > > >>> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web > > API > > >> and > > >>> much more. Get web development skills now with LearnDevNow > > - > > >>> 350+ hours of step-by-step video tutorials by Microsoft > > MVPs > > >> and experts. > > >>> SALE $99.99 this month only -- learn more at: > > >>> http://p.sf.net/sfu/learnmore_122812 > > >> > > >>> _______________________________________________ > > >>> 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... > > >> "It's hard to lead a cavalry charge if you think you > > look > > >> funny on a > > >> horse" ~ Adlai Stevenson > > >> > > >> > > >> > > > ------------------------------------------------------------------------------ > > >> Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, > > Web API > > >> and > > >> much more. Get web development skills now with > > LearnDevNow - > > >> 350+ hours of step-by-step video tutorials by > > Microsoft MVPs > > >> and experts. > > >> SALE $99.99 this month only -- learn more at: > > >> http://p.sf.net/sfu/learnmore_122812 > > >> > > >> _______________________________________________ > > >> 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... > > > "Be pleasant until ten o'clock in the morning and the rest > > of the day > > > will take care of itself." ~ Elbert Hubbard > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Free Next-Gen Firewall Hardware Offer > > > Buy your Sophos next-gen firewall before the end March 2013 > > > and get the hardware for free! Learn more. > > > http://p.sf.net/sfu/sophos-d2d-feb > > > _______________________________________________ > > > Vufind-tech mailing list > > > Vuf...@li... > > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_d2d_feb > > _______________________________________________ > > Vufind-tech mailing list > > Vuf...@li... > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_d2d_feb > > _______________________________________________ > > 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... > "Be pleasant until ten o'clock in the morning and the rest of the day > will take care of itself." ~ Elbert Hubbard > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > |
From: Alan R. <ala...@mn...> - 2013-02-20 19:07:29
|
Hello Anna, The new code that is attached to the JIRA ticket does have a normalization function in the services/AlphaBrowse/Results.php PHP code for seeding. It works pretty good for LC Call numbers. al On Wed, 2013-02-20 at 14:02 -0500, anna headley wrote: > Thanks, Demian and Alan! > > > Yes when I said browse I meant the alphabrowse module. Since solr > can't sort on multiple fields, we are considering pointing all of our > call number searches to the browse module, and beefing up the > browseable list to include more information (titles, at least). > > > The browse list would use the sort-normalized version of the call > number (with all the padding zeroes), and a record would have multiple > entries if it had multiple different call numbers. > > > > At which point I have two options: > > 1. Translate search queries into sort-normalized format to submit > them. Then translate each sort-normalized call number back into > something that could be displayed before showing to the user. > > 2. Store some sort of string-parsey quasi-tuple field, as I mentioned > before, in order to be able to match a sort-normalized call number > with the correct display value. I think this option is better because > it won't cost a huge amount of space and it will save time when > presenting the site. Also I wouldn't have to write all the code to > translate the different types of call numbers back and forth. > > > Alan's method of just grabbing the first call number if obviously way > easier than any of this. > > > Anna > > > > > > On Wed, Feb 20, 2013 at 12:38 PM, Alan Rykhus <ala...@mn...> > wrote: > Hello Anna, > > Yes, we do. > > But it is easier to make things work with only a single entry. > So we > take just the first call number we find in our holding > strings. > > I'm not sure if you can crawl a multi-value index in Solr. > That's what > is done to create the current Alphabetical browse databases. > > I see Demian posted a response too. The newer version of the > Alphabetic > browse uses a normailized call number index. If you can crawl > the > multi-values, it could be done. > > al > > On Wed, 2013-02-20 at 12:03 -0500, anna headley wrote: > > Does anyone else have a situation where records could have > multiple > > items with different call numbers? For example the item is > held in > > multiple libraries in the consortium, and each has given it > a > > different call number, or the item is held in the general > collection > > as well as some other collection with its own special set of > call > > numbers. > > > > > > Are you just arbitrarily choosing one call number to use as > the sort > > value? This would mean the item would only show up in one > place in > > the browse list. > > > > I'm thinking of adding another index field that holds a > tuple of > > (sort, display) call number values so that I can match > between them > > when needed. (Well, it couldn't be an actual tuple, but > some sort of > > parseable string.) > > > > Is anyone else doing something like this? Something smarter > than > > this? > > > > Thanks! > > Anna > > > > > > > > > > > > On Tue, Feb 19, 2013 at 8:38 PM, Tod Olson > <to...@uc...> wrote: > > I think that's attached to VUFIND-726: > > > > http://vufind.org/jira/browse/VUFIND-726 > > > > It looks like these changes would be of great use to > my site, > > especially the business of returning additional > fields in the > > browse search. I'd be interested in seeing these > changes work > > their way into the trunk. Could probably put some > time into in > > a few weeks. Is that of interest to you? > > > > -Tod > > > > > > On Feb 7, 2013, at 2:45 PM, Alan Rykhus > <ala...@mn...> > > wrote: > > > > > Hello Anna, > > > > > > I was sure I posted a tarball to JIRA, but I can't > find it. > > oh well > > > > > > Here is a README of what I changed: > > > > > > > > > What needs to be done to implement the new > Alphabetic Browse > > > functionality? > > > > > > 1. Indexing > > > * biblio/conf/schema.xml > > > * change topic_browse and > author_browse > > to > > > stored=true > > > * marc_local.properties > > > * callnumber > > > * uses > getFullCallNumber from > > > callnumber.bsh > > > * This is for > searching and is > > the default > > > as delivered in > Vufind > > > * callnumber-norm_str > > > * uses > > getFullCallNumberNormalized > > > * need to add > to > > callnumber.bsh > > > * uses > > > > > org.solrmarc.tools.CallNumUtils > > > function > > > * callnumber_display_str > > > * uses > getFullCallNumberDisplay > > > * need to add > to > > callnumber.bsh > > > * same as > > getFullCallNumber, just > > > do not > strip spaces > > > * name needs > to be a > > '_', Smarty > > > does not > like '-'s > > > * biblio/conf/solrconfig.xml > > > * For the lcc configuration > use > > callnumber instead > > > of callnumber-a > > > 2. New jar files > > > * browse-indexing.jar > > > * put in /srv/vufind/import > > > * browse-handler.jar > > > * put in /srv/vufind/solr/lib > > > 3. New sqlite build scripts > > > * Build all indexes using > StoredFieldLeech > > > * I don't have auth library, don't > know what > > effect this > > > will have > > > * topic_browse > > > * author_browse > > > * callnumber instead callnumber-a > > > * This is a full call number > field > > > * callnumber-norm_str for sort field > > > * New parameter -Dbuildfield > > > * This builds an additional > field in > > sqlite to > > > allow limits to an > institution > > > * Can be omitted if you do > not need a > > limit > > > 4. config.ini change > > > * new section [AlphaBrowse_Extras] > > > * Allows you to retrieve > additional > > fields from > > > database for display > purposes > > > * I use it to get the > > callnumber_display_str and > > > title fields for the call > numbers > > > 5. web/sys/Solr.php > > > * altered function alphabeticBrowse > to handle > > new > > > parameters > > > 6. web/services/AlphaBrowse/Results.php > > > * Altered code to handle new config > and page > > parameters > > > 7. > web/interface/themes/mnpals/AlphaBrowse/home.tpl > > > * links are different > > > * When browsing forward and > back, the > > rowid is in > > > the link from the initial > browse > > > * Additions to display extra fields > > > 8. web/interface/themes/mnpals/css/styles.css > > > * added .alphaBrowseLCCHeading > > > and .alphaBrowseTitleHeading > entries for > > callnumber > > > table > > > > > > If you have more questions, let me know. > > > > > > al > > > > > > > > > On Thu, 2013-02-07 at 14:53 -0500, anna headley > wrote: > > >> Hi Alan, > > >> > > >> > > >> Any additional detail on what you did to > accomplish this > > would be > > >> greatly appreciated. > > >> > > >> > > >> Is all your work in AlphaBrowse? Did you also > create / > > change > > >> indexing rules? How are you normalizing the user > input? > > >> > > >> > > >> We'd like to do this based on the browse > functionality, as > > well, and > > >> then enhance that page to show more info about > each item. > > >> > > >> > > >> Anna > > >> > > >> > > >> > > >> > > >> On Fri, Jan 11, 2013 at 9:43 AM, Alan Rykhus > > <ala...@mn...> > > >> wrote: > > >> Hello, > > >> > > >> I've been working with Mark Triggs' > AlphaBrowse code > > and have > > >> the > > >> AlphaBrowse working for call numbers. > > >> > > >> The one issue I'm having problems with is > seeding > > into the > > >> correct spot. > > >> I plan on looking at that next week. But > the full > > call numbers > > >> are > > >> sorting in order. I've added code to bring > in any > > additional > > >> fields you > > >> might want from the records. At this time > I'm adding > > the > > >> titles to the > > >> display in the browse screen. > > >> > > >> Today I'm rebuilding my Solr db on a > machine that > > could use > > >> more memory. > > >> The indexing job will not finish until > tomorrow or > > Sunday. > > >> Monday I'll > > >> have my sites up where you can see this. > > >> > > >> This won't allow you to search on a range, > but you > > can browse > > >> through > > >> the numbers. > > >> > > >> al > > >> > > >> > > >> On Fri, 2013-01-11 at 11:34 +0000, > Osullivan L. > > wrote: > > >>> Hi Tod, > > >>> > > >>> Apologies for the delay in replying - I lost > this e-mail > > in > > >> the > > >>> mountain of e-mails I had after the New Year. > > >>> > > >>> I have managed to get the items to display in > the correct > > >> order with > > >>> some custom indexing but I hit a snag with the > ultimate > > goal > > >> of my > > >>> attempts which was to add call number range > searching. > > >>> > > >>> getFullNormalizedLCCN.bsh > > >>> > > >>> import org.marc4j.marc.Record; > > >>> import org.solrmarc.tools.CallNumUtils; > > >>> org.solrmarc.index.SolrIndexer indexer = null; > > >>> > > >>> /** > > >>> * Normalize a single LCCN > > >>> * @param lccn > > >>> * @return Normalized LCCN > > >>> */ > > >>> public String getFullNormalizedLCCN(Record > record, String > > >> lccn) { > > >>> > > >>> if (lccn != null) { > > >>> > > >>> lccn = indexer.getFirstFieldVal(record, > lccn); > > >>> > > >>> String recordID = "1"; // Need to assign > real value > > >> from > > >>> record? > > >>> > > >>> if (lccn != null) { > > >>> > > >>> String normal = > CallNumUtils.getLCShelfkey(lccn, > > >> recordID); > > >>> > > >>> if (normal != null) { > > >>> // Send back normalized LCCN: > > >>> return normal; > > >>> } > > >>> } > > >>> } > > >>> > > >>> // If we got this far, we couldn't find a > valid value: > > >>> return null; > > >>> } > > >>> > > >>> marc_local.properties > > >>> callnumber-norm_str= > script(getFullNormalizedLCCN.bsh), > > >>> getFullNormalizedLCCN(852hi) > > >>> > > >>> schema.xml > > >>> <field name="callnumber-search" type="string" > > indexed="true" > > >>> stored="true"/> > > >>> > > >>> searches.ini > > >>> [Sorting] > > >>> ; Use the "callnumber" line for LC or the > "dewey-sort" > > line > > >> for Dewey > > >>> Decimal. > > >>> ; If you want to enable both systems for > sorting, you can > > >> uncomment > > >>> both lines, > > >>> ; but you will need to add some custom text to > distinguish > > >> between the > > >>> two. > > >>> callnumber-norm_str = sort_callnumber > > >>> > > >>> [DefaultSortingByType] > > >>> CallNumber = callnumber-norm_str > > >>> > > >>> Cheers, > > >>> > > >>> Luke > > >>> > > >>> On 12/27/2012 02:36 PM, Tod Olson wrote: > > >>> > > >>>> Luke, > > >>>> > > >>>> Did you ever come up with a solution to this > problem? > > >>>> > > >>>> We're in a similar way, wanting the call number > browse to > > >> reflect call number shelving order. > > >>>> > > >>>> -Tod > > >>>> > > >>>> On May 21, 2012, at 8:22 AM, Osullivan L. > > >> <L.O...@sw...> wrote: > > >>>> > > >>>>> Hi Folks, > > >>>>> > > >>>>> One of our subject librarians has asked us to > change the > > >> way results are displayed when a > callnumber search > > is > > >> performed. > > >>>>> > > >>>>> Basically, if someone searches for PQ239, she > would like > > >> the results returned to be PQ239, PQ239 > > ABC, > > PQ239 .A22 > > >> 2011, PQ239 .W55 2011, PQ240, PQ2390 etc > > >>>>> > > >>>>> At present, we are getting a lot of PQ2391, > PQ2392 etc > > >> at the top of our results... > > >>>>> > > >>>>> The problem I see it two fold - To get what > she ideally > > >> wants, we'd need to restrict all > callnumber search > > to exact > > >> matches using the callnumber-a field and > then create > > more > > >> fields to provide sorting for the rest of > the > > callnumber. Has > > >> anyone done something similar? > > >>>>> > > >>>>> Thanks, > > >>>>> > > >>>>> Luke > > >>>>> > > >> > > > ------------------------------------------------------------------------------ > > >>>>> Live Security Virtual Conference > > >>>>> Exclusive live event will cover all the ways > today's > > >> security and > > >>>>> threat landscape has changed and how IT > managers can > > >> respond. Discussions > > >>>>> will include endpoint security, mobile > security and the > > >> latest in malware > > >>>>> threats. > > >> > > > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > >>>>> > _______________________________________________ > > >>>>> VuFind-General mailing list > > >>>>> VuF...@li... > > >>>>> > > >> > > > https://lists.sourceforge.net/lists/listinfo/vufind-general > > >>> > > >>> -- > > >>> Luke O'Sullivan > > >>> Systems Developer > > >>> Web Team > > >>> Swansea University, Singleton Park, Swansea SA2 > 8PP, UK > > >>> l.o...@sw... > > >>> 01792 602772 > > >>> @l_os_cymru > > >> > > >>> > > >> > > > ------------------------------------------------------------------------------ > > >>> Master HTML5, CSS3, ASP.NET, MVC, AJAX, > Knockout.js, Web > > API > > >> and > > >>> much more. Get web development skills now with > LearnDevNow > > - > > >>> 350+ hours of step-by-step video tutorials by > Microsoft > > MVPs > > >> and experts. > > >>> SALE $99.99 this month only -- learn more at: > > >>> http://p.sf.net/sfu/learnmore_122812 > > >> > > >>> _______________________________________________ > > >>> 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... > > >> "It's hard to lead a cavalry charge if you > think you > > look > > >> funny on a > > >> horse" ~ Adlai Stevenson > > >> > > >> > > >> > > > ------------------------------------------------------------------------------ > > >> Master HTML5, CSS3, ASP.NET, MVC, AJAX, > Knockout.js, > > Web API > > >> and > > >> much more. Get web development skills now > with > > LearnDevNow - > > >> 350+ hours of step-by-step video tutorials > by > > Microsoft MVPs > > >> and experts. > > >> SALE $99.99 this month only -- learn more > at: > > >> http://p.sf.net/sfu/learnmore_122812 > > >> > > >> > _______________________________________________ > > >> 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... > > > "Be pleasant until ten o'clock in the morning and > the rest > > of the day > > > will take care of itself." ~ Elbert Hubbard > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Free Next-Gen Firewall Hardware Offer > > > Buy your Sophos next-gen firewall before the end > March 2013 > > > and get the hardware for free! Learn more. > > > http://p.sf.net/sfu/sophos-d2d-feb > > > _______________________________________________ > > > Vufind-tech mailing list > > > Vuf...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_d2d_feb > > _______________________________________________ > > Vufind-tech mailing list > > Vuf...@li... > > > https://lists.sourceforge.net/lists/listinfo/vufind-tech > > > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_d2d_feb > > _______________________________________________ > > 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... > "Be pleasant until ten o'clock in the morning and the rest of > the day > will take care of itself." ~ Elbert Hubbard > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > 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... "Be pleasant until ten o'clock in the morning and the rest of the day will take care of itself." ~ Elbert Hubbard |