Feature #5286

Include editable Facet filter title in Admin > Settings

Added by Dan Gillean almost 9 years ago. Updated over 8 years ago.

Status:VerifiedStart date:06/27/2013
Priority:MediumDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:UsabilityEstimated time:8.00 hours
Target version:Release 2.0.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

Ticket based on user feedback: https://groups.google.com/d/msg/ica-atom-users/PS13ud6hTvE/C9RvQG2DZL8J

Initial feedback expresses concern over end-user understanding of the intent of the filters; the ability to personally configure the terms used (ex: to be able to say "filter results by place" instead of just "Places") to suit local preferences and use cases would greatly add to the customizability of AtoM.

As such, ideally an Admin user could navigate to Admin > Menus, and be able to change the labels associated with the search/browse facets, as well as a a title or header for the filters themselves (e.g. "Narrow your results by;" "Search Filters," etc.) if desired.

AtoM_facetHeader.png - Adding a title to the search facets (212 KB) Dan Gillean, 08/16/2013 10:20 AM

History

#1 Updated by Jesús García Crespo almost 9 years ago

  • Estimated time set to 8.00

#2 Updated by Jesús García Crespo almost 9 years ago

  • Assignee changed from Jesús García Crespo to Dan Gillean

Would you like to add some more comments or a mockup, please?
I can't really see what you are suggesting.

I don't understand why would you offer the option to change UI labes form the menu editor. That may not be the best place?
Also, this level of customization may be too complex, maybe something we want to push to 2.1 or later? Or we could change the default labels.

#3 Updated by Dan Gillean almost 9 years ago

Ok, as a compromise that might address some of the issues raised without adding too much complexity, I propose we add a simple title above the search facets, to clarify their use. This avoids needing to have users mess with the labels on the facets themselves, and will avoid repetition anyways (Narrow results by place, Narrow results by subject, etc). Hopefully this simplifies the issue ticket while also addressing some of the concerns raised.

See attached screenshot.

For now, I've gone with the default "Narrow your results by".

IDEALLY, we could set up this string to be one of the customizable labels through the GUI - i.e., in the same way that you can change "information object" to "archival description" or "resource" or whatever you want, a user could change this header to "Filter results by:" or "Search filters" or whatever else they want. This ideal functionality could be bumped to a later release if it adds too much complexity, and if it's important to users, maybe we can find some development support. But the simple step of adding a clarifying title addresses at least some of the usability concerns raised, and should not be too difficult to implement.

#4 Updated by Dan Gillean almost 9 years ago

  • Assignee changed from Dan Gillean to Jesús García Crespo

#5 Updated by Jesús García Crespo almost 9 years ago

Awesome, thanks.

#6 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from New to In progress
  • Assignee changed from Jesús García Crespo to José Raddaoui Marín

#7 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from In progress to QA/Review
  • % Done changed from 0 to 100

Applied in changeset atom|commit:9d650ce5b939926a865ce9e3b259233f35563fc3.

#8 Updated by Dan Gillean over 8 years ago

Awesome! Administrators can now edit the title above the search/browse facets via the GUI by Navigating to Admin > Settings > User interface label and changing the "facetstitle" string.

#9 Updated by Dan Gillean over 8 years ago

  • Status changed from QA/Review to Verified

#10 Updated by Dan Gillean over 8 years ago

  • Subject changed from Include search/browse facet headings in Admin > Menus to allow users to customize labels to Include editable Facet filter title in Admin > Settings

Since the scope of this issue changed throughout the ticket, I am changing the title now to reflect the final implementation, for other users who might be searching - this way it doesn't appear that the original proposal was verified.

Also available in: Atom PDF