[Dspace-tech] How does wildcard behave in Discovery search filters?
Hi, I was looking at our Discovery sidebar facet configuration and I noticed we have items using both dc.type as well as dc.type.output fields. Now I'm wondering how the following search filter configuration would behave: valuedc.type.*/value Would that capture both dc.type as well as dc.type.output, or only metadata values under the dc.type.* namespace? I'm from a computer science background rather than library science, so the answer is not obvious to me in this context! In any case, it is my long-term plan to move away from dc.type.output, as it seems we added it in error, and dc.type is standard Dublin Core so that should have preference. Thanks, Alan -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] How does wildcard behave in Discovery search filters?
Hi, the wild card filter is already present in the default configuration for dc.subject.*: https://github.com/DSpace/DSpace/blob/master/dspace/config/spring/api/discovery.xml#L389 Just did a quick test on demo.dspace.org to see how it behaves: http://demo.dspace.org/xmlui/handle/10673/279 most terms are in dc.subject (without qualifier) and I added MyWeirdSubject in dc.subject.other They all show up in the sidebar facet. rgds Bram -- [image: logo] *Bram Luyten* *250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586* *Esperantolaan 4, Heverlee 3001, Belgium* www.atmire.com http://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml On 20 August 2015 at 08:44, Alan Orth alan.o...@gmail.com wrote: Hi, I was looking at our Discovery sidebar facet configuration and I noticed we have items using both dc.type as well as dc.type.output fields. Now I'm wondering how the following search filter configuration would behave: valuedc.type.*/value Would that capture both dc.type as well as dc.type.output, or only metadata values under the dc.type.* namespace? I'm from a computer science background rather than library science, so the answer is not obvious to me in this context! In any case, it is my long-term plan to move away from dc.type.output, as it seems we added it in error, and dc.type is standard Dublin Core so that should have preference. Thanks, Alan -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] How does wildcard behave in Discovery search filters?
Ah, indeed! I saw that dc.subject.* in the default discovery.xml but didn't think to test it. Thanks, Bram. :) Alan On Thu, Aug 20, 2015 at 3:01 PM Bram Luyten b...@atmire.com wrote: Hi, the wild card filter is already present in the default configuration for dc.subject.*: https://github.com/DSpace/DSpace/blob/master/dspace/config/spring/api/discovery.xml#L389 Just did a quick test on demo.dspace.org to see how it behaves: http://demo.dspace.org/xmlui/handle/10673/279 most terms are in dc.subject (without qualifier) and I added MyWeirdSubject in dc.subject.other They all show up in the sidebar facet. rgds Bram -- [image: logo] *Bram Luyten* *250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586* *Esperantolaan 4, Heverlee 3001, Belgium* www.atmire.com http://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml On 20 August 2015 at 08:44, Alan Orth alan.o...@gmail.com wrote: Hi, I was looking at our Discovery sidebar facet configuration and I noticed we have items using both dc.type as well as dc.type.output fields. Now I'm wondering how the following search filter configuration would behave: valuedc.type.*/value Would that capture both dc.type as well as dc.type.output, or only metadata values under the dc.type.* namespace? I'm from a computer science background rather than library science, so the answer is not obvious to me in this context! In any case, it is my long-term plan to move away from dc.type.output, as it seems we added it in error, and dc.type is standard Dublin Core so that should have preference. Thanks, Alan -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
