[Dspace-tech] How does wildcard behave in Discovery search filters?

[Alan Orth]

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:

<value>dc.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

[Bram Luyten]

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=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>

Post by Alan Orth
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
<value>dc.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
https://lists.sourceforge.net/lists/listinfo/dspace-tech
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Alan Orth]

Ah, indeed! I saw that dc.subject.* in the default discovery.xml but didn't
think to test it. Thanks, Bram. :)

Alan

Post by Bram Luyten
Hi,
the wild card filter is already present in the default configuration for
https://github.com/DSpace/DSpace/blob/master/dspace/config/spring/api/discovery.xml#L389
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=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>

Post by Alan Orth
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
<value>dc.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
https://lists.sourceforge.net/lists/listinfo/dspace-tech
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette