Dear Bill, Unfortunately, I am unaware of the DSpace solr stuff, so I cannot help you with this. Maybe, someone else from the list can help on this issue. That's why I'm CCing this email to the list.
Regards, Kostas -----Original Message----- From: Bill Tantzen [mailto:[email protected]] Sent: Friday, February 28, 2014 11:01 PM To: Kostas Stamatis Subject: Re: [Dspace-tech] configuring browse indexes Thanks Kostas! My question is even more specific than that. Let me get very particular.j Here is how my browse indexes are currently configured: webui.browse.index.1 = dateissued:item:dateissued webui.browse.index.2 = author:metadata:dc.contributor.*,dc.creator:text webui.browse.index.3 = title:metadata:dc.title:title:full webui.browse.index.4 = subject:metadata:dc.subject.*:text After indexing, I see fields corresponding to each of the metadata indexes in my Solr database, for instance: <arr name="bi_2_dis_filter"> <str>speaks, kelsey lynn ||| Speaks, Kelsey Lynn</str> </arr> <arr name="bi_2_dis_partial"> <str>Speaks, Kelsey Lynn</str> </arr> <arr name="bi_2_dis_value_filter"> <str>Speaks, Kelsey Lynn</str> </arr> similar for bi_2 and bi_3 and bi_4. This is an approximation of how it works with postgresql with it's bi_* series of tables. For the dateissued field, an "item", I'm not sure where the data is stored. In Solr, there is a "dateIssued" field, but case sensitivity prevents me from searching on "dateissued" successfully. There's also a dc.date.issued field... What I'm wondering is what is the solr source of the "item" data? It is not clear, because the field names do not seem to match. Or am I looking at the wrong field altogether? Am I making myself a little more clear now? Thanks for helping me look under the hood!! Bill On Thu, Feb 27, 2014 at 11:54 PM, Kostas Stamatis <[email protected]> wrote: > Hi Bill, > > > > Discovery/Solr work the same as DAO, the "metadata" and "item" options > apply as well, the only difference is the way the indices are stored > in the back-end. Take a look at DSpace demo site: http://demo.dspace.org/jspui/ . > Notice, that there are "item" and "metadata" browse indices as well. > > > > Maybe the problem is in the way you re-index after configuration changes. > Take a look here: > https://wiki.duraspace.org/display/DSDOC4x/Discovery#Discovery-Discove > rySolrIndexMaintenance for more information on how to re-index on > Discovery/Solr. > > > > > > Regards, > > > > Kostas > > > > > > From: Bill Tantzen [mailto:[email protected]] > Sent: Thursday, February 27, 2014 3:56 PM > To: Kostas Stamatis > Cc: dspace-tech > Subject: Re: [Dspace-tech] configuring browse indexes > > > > Kostas, > > Thank you for the detailed reply! > > > > In my case, I am indeed using Discovery/Solr. I'm clear now on how > these configuration options work with postgresql indexes, but still > not clear on the difference between "item" and "metadata" with > Discovery... In a nutshell, when designating a browse index as > "item", no results (as in the documentation's examples) no results are found (even after reindexing). > > > > Does this option not apply to Discovery? > > > > Thanks, > > Bill > > > > On Thu, Feb 27, 2014 at 12:48 AM, Kostas Stamatis <[email protected]> wrote: > > Dear Bill, > > > > First of all, if you consider changing these options from the > configuration file, you need to re-index the browse index afterwards. > That's why the first config may not work for you directly, you need to re-index. > > > > So, the difference between metadata and item is the following: When a > browse index is declared as metadata, when clicked, you are presented > with the distinct values of this metadata field and when a value is > pressed you are presented the items which have this value. When a > browse index is declared as "item", when clicked you are directly presented with the list of items. > > In case of the "deprecated" browse DAO indexing, the browse indices > declared as metadata where stored in database in tables whose names > starts with bi_(i)_dis or bi_(i)_dmap, where i is the number declared > in the cdg file for each index. When the brose index is declared as > item, then it stored in the table named "bi_item" and more > specifically, each "item" browse index is bound to a sort column in this table. > > DSpace 4, workd by default with solr and discovery, so, the > aforementioned may not take place at all. > > > > Hope this helps, > > > > Kostas > > > > > > > > From: Bill Tantzen [mailto:[email protected]] > Sent: Wednesday, February 26, 2014 11:46 PM > To: dspace-tech > Subject: [Dspace-tech] configuring browse indexes > > > > In dspace 4.0 (or any version in general), I have the choice for :metadata: > for any given webui.browse.index.n of either "metadata" or "item". > > Can anyone explain the difference between these two options? For > instance, in the docs I see an example like so for title: > > webui.browse.index.3 = title:metadata:dc.title:title:full > > In the default dspace.cfg, the example is > > webui.browse.index.3 = title:item:title > > > > I am guessing that with "metadata" I'm pulling the data from dc.title > field...What about "item"? Where does that data come from? > > > > Naturally, I'm asking because the latter example works, and the former > does not, but I'm having a hard time understanding why. > > > > Thanks in advance for any pointers! > > Regards, > > Bill > > ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
