From: Jay R. <ja...@gm...> - 2013-04-25 16:28:54
|
This is what is populated in Solr: <str name="title">Captive embraces</str> <str name="title_auth">Captive embraces</str> <str name="title_full">Captive embraces [large print] / Fern Michaels.</str> <str name="title_fullStr">Captive embraces [large print] / Fern Michaels. </str> <str name="title_full_unstemmed">Captive embraces [large print] / Fern Michaels.</str> <str name="title_short">Captive embraces</str> <str name="title_sort">captive embraces</str> <arr name="topic"> On Thu, Apr 25, 2013 at 10:48 AM, Demian Katz <dem...@vi...>wrote: > Not sure what’s going on with dewey_browse, but for title_browse, the > first thing to check is whether title and title_sort are populated > correctly in Solr.**** > > ** ** > > - Demian**** > > ** ** > > *From:* Jay Roos [mailto:ja...@gm...] > *Sent:* Thursday, April 25, 2013 11:47 AM > *To:* Demian Katz > *Cc:* vuf...@li... > *Subject:* Re: [VuFind-Tech] Skipped entries for docid....**** > > ** ** > > Yes, this is during a index-alphabetic-browse run. It is happening on > title_browse and dewey_browse.**** > > ** ** > > On Thu, Apr 25, 2013 at 10:38 AM, Demian Katz <dem...@vi...> > wrote:**** > > This happened during alphabrowse generation, correct? Which index was > being built at the time? Mark can probably give more details, but I think > the issue is that AlphaBrowse sometimes uses separate fields for display > and sorting purposes; it expects these fields to have parallel sets of > values and gets confused if they do not. Might be worth looking at 369009 > to see what’s going on there – but knowing which index was being built will > help you determine which fields to look at.**** > > **** > > - Demian**** > > **** > > *From:* Jay Roos [mailto:ja...@gm...] > *Sent:* Thursday, April 25, 2013 11:06 AM > *To:* vuf...@li... > *Subject:* [VuFind-Tech] Skipped entries for docid....**** > > **** > > What does the message **** > > **** > > "Skipped entries for docid 369009 because the number of sort keys didn't > match the number of stored values." > **** > > **** > > mean?**** > > **** > > Is it something I can/should look to fix?**** > > **** > > **** > > -- > Jay Roos > Information Technology Coordinator > Great River Regional Library**** > > > > **** > > ** ** > > -- > Jay Roos > Information Technology Coordinator > Great River Regional Library**** > -- Jay Roos Information Technology Coordinator Great River Regional Library |