From e9771beffe8ffcdb0d7f02eb2bfce6962a4e1ac5 Mon Sep 17 00:00:00 2001 From: Bill Erickson <berick@esilibrary.com> Date: Thu, 31 May 2012 09:27:40 -0400 Subject: [PATCH] Search filter groups release notes Signed-off-by: Bill Erickson <berick@esilibrary.com> Signed-off-by: Kathy Lussier <klussier@masslnc.org> Signed-off-by: Dan Scott <dscott@laurentian.ca> --- docs/RELEASE_NOTES_NEXT/search-filter-groups.txt | 38 ++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 docs/RELEASE_NOTES_NEXT/search-filter-groups.txt diff --git a/docs/RELEASE_NOTES_NEXT/search-filter-groups.txt b/docs/RELEASE_NOTES_NEXT/search-filter-groups.txt new file mode 100644 index 0000000000..3473166f92 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/search-filter-groups.txt @@ -0,0 +1,38 @@ +Search Filter Groups +-------------------- + +Search filter groups support the collection of free-form search queries into +named groups of named filters which can be applied to searches. The purpose +is to allow systems to fine tune filters in the catalog. + +Editing the groups and their entries is done in the staff client at +Admin -> Local Administration -> Search Filter Groups. + +Example +~~~~~~~ + +Consider a new filter called "reading_level". It uses a combination of +MARC audience and shelving location to differentiate items. It might have +entries that look like this: + +Children's Materials => audience(a,b,c) locations(1,2,3,4,5,6,7) + +Young Adult => audience(j,d) locations(5,6,7,8,9,10) + +Adult => audience(e,f,g, ) -locations(1,2,3,4,5,6,7,8,9) + +Using the filter in a template +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +[source, html] +--------------------------------------------------- +<span>[% ctx.filter_groups.reading_level.label %]<span> +<span> +[% + INCLUDE 'opac/parts/filter_group_selector.tt2' + filter_group=reading_level + none_ok=1 + none_label=l('All') +%] +<span> +--------------------------------------------------- -- 2.11.0