| Summary: | Advanced search "standard number" options are confusing | ||
|---|---|---|---|
| Product: | Koha | Reporter: | paxed <pasi.kallinen> |
| Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | ||
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
I've changed the title of this bug to reflect the fact that it is not specific to Bootstrap. It looks to me like the change introduced in Bug 9395 was intended to remove the "sn" option altogether in cases where the system is configured to use "sn,phr" by default. Can anyone confirm? |
From bootstrap/en/modules/opac-advsearch.tt: [% IF ( numbersphr) %] <option value="sn,phr">Standard number</option> [% ELSE %] <option value="sn">Standard number</option> [% END %] <option value="sn">Standard number</option> The patron cannot be expected to know what the difference is between the two "Standard number" entries. And if numbersphr is not on, there isn't any difference.