Bug 33165 - Add search history with its own button to staff interface start page
Summary: Add search history with its own button to staff interface start page
Status: RESOLVED MOVED
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-08 03:56 UTC by Adam Styles
Modified: 2023-03-10 13:39 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
screen shot of Koha staff interface landing page with added 'my search history' icon (55.45 KB, image/png)
2023-03-08 03:56 UTC, Adam Styles
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Styles 2023-03-08 03:56:25 UTC
Created attachment 147889 [details]
screen shot of Koha staff interface landing page with added 'my search history' icon

Hi All,

I believe the 'search history' feature to be quite useful in daily repeated search work flows, further to this it is a feature fairly hidden behind a drop down UI. Therefor to promote the use of this valuable tool and also to improve it's discoverability, I propose the follow new enhancement I happy to contribute as patch.

The Creation of 'My search history' button via added LI element in intranet landing intranet-main.tt, linked to '/cgi-bin/koha/catalogue/search-history.pl'

See attached screen shot that makes use of existing LI element design system and related FA icons (4.7.0). I am of course happy to vote on icon choice (lol).

Source could be applied intranet-main.tt li component add after line 103

Static there for all.
...
<li>
    <a class="icon_general icon_lists" href="/cgi-bin/koha/catalogue/search-history.pl"><i class="fa fa-fw fa-history"></i>My search history</a>
</li>
...


OR 

Enable/disable via system preference e.g 'showMySearchHistoryIconStaff'

...

[% IF Koha.Preference('ILLModule') %]
<li>
    <a class="icon_general icon_lists" href="/cgi-bin/koha/catalogue/search-history.pl"><i class="fa fa-fw fa-history"></i>My search history</a>
</li>
[% END %]

...

I welcome feedback, and I can get started on this soon if community keen.

This is my first suggested UI change that I would like to code contribute.

Thanks.
Comment 1 Adam Styles 2023-03-08 04:00:30 UTC
opps...

[% IF Koha.Preference('showMySearchHistoryIconStaff') %]
<li>
    <a class="icon_general icon_lists" href="/cgi-bin/koha/catalogue/search-history.pl"><i class="fa fa-fw fa-history"></i>My search history</a>
</li>
[% END %]

That's better 8-)
Comment 2 Katrin Fischer 2023-03-09 21:44:41 UTC
I am not sure about this one tbh. The page is already quite full, and with ILL and ERM active the balance is already off by 2 for icons on the left vs right side.

We try to only put modules on the start page and search history isn't really a module I'd say, but a catalog feature. It will also only be helpful if you have already done some searches.

Functionally, I think you'd also need to check on the existing preference  EnableSearchHistory, so it only displays when the feature is activated.
Comment 3 Adam Styles 2023-03-09 23:00:52 UTC
Hi Katrin,

You make some excellent points, I have been thinking on my idea submission over the last few days and agree that perhaps my perspective on a 'search history' action from the landing page is quite meaningful, as I use this daily, however for those who do not do so, and also for those who share Koha logins, perhaps this could be more noise then benefit.

Building on your point about this suggestions being more feature of an existing module, as opposed to an actual module, perhaps I might pivot this original feature concept into an added button/link element that could sit in the footer of the advanced search module. This would offer an added quick action for those like myself who use the search history daily, but would create no friction for other users.

As I a new to this community, would I now create a new feature ticket? or simply re-purpose this one.

New concept:
* I want a 'search history' button or link added to advanced search page, to allow quick previous search history action.

I appreciate your thoughts on this BTW.

Thanks.
Comment 4 Adam Styles 2023-03-10 05:47:39 UTC
Hi All,

I have created a new bug based on the new user story and feature offer.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33190

Can someone please advise the correct way to close this ticket?

Thanks.
Comment 5 Katrin Fischer 2023-03-10 13:38:45 UTC
Hi Adam, 

there are (as with Perl) always multiple ways to do things and not really a wrong way. We could mark this RESOLVED (WONTFIX or INVALID or MOVED). After a while we will move it to CLOSED - this happens always a few weeks after a release when we do some clean-up.
I've chosen MOVED as it's the least harsh - I like the idea that the idea progressed ;)