TPAC: Provide shortcut for changing search scope

Bug #1487527 reported by Dan Pearl on 2015-08-21
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned

Bug Description

From the MassLNC suggestion: "Patrons and librarians frequently need to change the search scope, and the vast majority of the time they are switching between their default scope and the top-level (all libraries) scope. A button that provided an easy means to do this would be very helpful."

Attached is a mini-spec describing implementation ideas.

This is a wishlist-type item.

Dan Pearl (dpearl) wrote :
Mike Rylander (mrylander) wrote :

Interestingly, we had just such a thing for many years, in the jspac, in the form of the depth selector. I still lament its (ui-level) death, but it's still supported throughout and can be spelled "depth(X)" in searches.

Dan Pearl (dpearl) wrote :

I understand Tom Berezansky may have a different implementation.

This is mine:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dpearl/scope_switch_1487527

tags: added: pullrequest
Kathy Lussier (klussier) on 2015-10-26
Changed in evergreen:
status: New → Triaged
importance: Undecided → Wishlist
Kathy Lussier (klussier) wrote :

I have loaded this code on a MassLNC VM. I'll look at it more closely later, but it's available at http://mlnc1.mvlcstaff.org/eg/opac/home if anyone else wants to take a look at it.

Tested and it worked fine for me on Kathy's site but I haven't installed it
myself yet.

On Mon, Oct 26, 2015 at 12:55 PM, Kathy Lussier <email address hidden>
wrote:

> I have loaded this code on a MassLNC VM. I'll look at it more closely
> later, but it's available at http://mlnc1.mvlcstaff.org/eg/opac/home if
> anyone else wants to take a look at it.
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: evergreenbugs
> https://bugs.launchpad.net/bugs/1487527
>
> Title:
> TPAC: Provide shortcut for changing search scope
>
> Status in Evergreen:
> Triaged
>
> Bug description:
> From the MassLNC suggestion: "Patrons and librarians frequently need
> to change the search scope, and the vast majority of the time they are
> switching between their default scope and the top-level (all
> libraries) scope. A button that provided an easy means to do this
> would be very helpful."
>
> Attached is a mini-spec describing implementation ideas.
>
> This is a wishlist-type item.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1487527/+subscriptions
>

Thomas Berezansky (tsbere) wrote :

For reference, this is my implementation:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/tsbere/depth_zero

It is installed on MVLC's catalog:

http://catalog.mvlc.org

Note that it only shows up when your original search was not scoped to the entire consortia outright.

Thomas Berezansky (tsbere) wrote :

As an additional note, I was considering adding config.tt2 entries for my version for whether to show it or not and what depth to have it change to (current is "when the org unit isn't 1 and depth 0", the latter being what I named the branch after). If that is desirable I can go ahead and make those additions.

Rogan Hamby (rogan-hamby) wrote :

I tried tsbere's too and I like it a little more. I like that it doesn't
show up if the original search is scoped to the entire consortium. Also
the checkbox having a dynamic behavior is a bit more consistent with the
other UI elements IMO.

Again, I tried it on the mvlc box, didn't install it myself yet.

On Tue, Oct 27, 2015 at 1:16 PM, Thomas Berezansky <
<email address hidden>> wrote:

> For reference, this is my implementation:
>
> http://git.evergreen-
>
> ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/tsbere/depth_zero
>
> It is installed on MVLC's catalog:
>
> http://catalog.mvlc.org
>
> Note that it only shows up when your original search was not scoped to
> the entire consortia outright.
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: evergreenbugs
> https://bugs.launchpad.net/bugs/1487527
>
> Title:
> TPAC: Provide shortcut for changing search scope
>
> Status in Evergreen:
> Triaged
>
> Bug description:
> From the MassLNC suggestion: "Patrons and librarians frequently need
> to change the search scope, and the vast majority of the time they are
> switching between their default scope and the top-level (all
> libraries) scope. A button that provided an easy means to do this
> would be very helpful."
>
> Attached is a mini-spec describing implementation ideas.
>
> This is a wishlist-type item.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1487527/+subscriptions
>

Dan Pearl (dpearl) wrote :

I like tsbere's take a little less, actually. I'm thinking of the patron experience.

The "checkbox as a submit" UI: I can't think of anywhere in EG that this is used, and it might be confusing to patrons.
I can see that thefunctionality was a way to reduce clicks, and I appreciate that.

I think my functionality is a bit more intuitive, and mirrors similar UI in Yahoo, Google, Amazon, etc. They have done the education for us!

Dan

Dan Pearl (dpearl) wrote :

I thought about hiding the global search button if the pull-down was already set to the top level. I thought that there was no harm done to keep the global search button there, and it would simplify the code not to have to maintain the visibility or active/inactive status of the button. In fact, I kinda like it that you can always rely on clicking the blue button for a global search.

Thomas Berezansky (tsbere) wrote :

For the "checkbox as a submit" bit: The "Limit to available items" and "Group Formats and Editions" check boxes do that already, so I was duplicating the functionality those already provide. As mine is literally placed right next to them I saw it as reasonable to duplicate that.

For a couple of other comparative points:

My version does not rely on JavaScript to function. Without JavaScript you have to submit the search yourself, but it still works.
Dan's version seems to act as though you hit the regular search button without JavaScript available/enabled, making me think it should at least be hidden by default and "shown" by JavaScript instead of being there from the start.

My version leaves the search scope at the selected org unit but changes the "depth" of the search. This has effects on some things, such as rendering of Located URIs and copy count displays.
Dan's changes the search scope to the top of the org tree, which will remove the selected library scoping on those features.
Which is better would vary on the goals of the end-user, I suspect, as both methods have pros and cons.

Thomas Berezansky (tsbere) wrote :

I have pushed an additional commit to the depth_zero branch to add config.tt2 options, an optional button for basic search, and an optional "Results Page Hint" to show up when the option is selected.

It also removes the "hide the checkbox if you scoped to the top of the tree anyway" check for a more consistent interface.

Kathy Lussier (klussier) on 2015-11-05
Changed in evergreen:
assignee: nobody → Kathy Lussier (klussier)
Kathy Lussier (klussier) wrote :

Looks good to me. I signed off on tsbere's latest branch and added a commit to uncomment the config.tt2 settings so that it will
be turned on by default. Some sites may miss the new feature in release notes when upgrading. Turning it on by default will allow them to use it immediately and will provide a cue to look further at the release notes if they don't like a particular aspect of it.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/kmlussier/lp1487527-depth_zero

Changed in evergreen:
assignee: Kathy Lussier (klussier) → nobody
tags: added: signedoff
Kathy Lussier (klussier) on 2015-11-05
Changed in evergreen:
milestone: none → 2.next
Ben Shum (bshum) wrote :

Neat feature, pushed to master for next version goodness.

Changed in evergreen:
status: Triaged → Fix Committed
Changed in evergreen:
milestone: 2.next → 2.10-beta
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers