Angular staff catalog facets are effectively hard-coded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
High
|
Unassigned |
Bug Description
Evergreen version: 3.6+
OpenSRF version: all
PG version: all
The public catalog templates allow an administrator to define the set and order of facets that could be displayed for any search result. The Angular staff catalog follows the same logic but does not have a way for an admin to specify the facet display configuration except by adjusting code and recompiling the Angular client.
Bill Erickson has put together a WIP branch to help address the more general problem of Angular catalog config and customization here:
His branch addresses the specific concern of this bug but demonstrates a general framework for attacking (some of) this class of problems. Feedback (on the problem, and his branch) sought!
Changed in evergreen: | |
status: | New → Confirmed |
tags: |
added: needswork removed: pullrequest |
tags: | added: staffcatalogblocker |
And as a first bit of feedback, I think it would be useful to have this file live in the opac template area near config.tt2 so that it can make use of the existing (public catalog) template override functionality.