[Koha-bugs] [Bug 30271] Allow distinct ILLHiddenRequestStatuses config for view from patron record

[bugzilla-daemon at bugs.koha-community.org]

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

--- Comment #5 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---

> This is already implementing the "search for a status without having to pick
> a backend", among other things related to status_alias.

Our backend doesn't use status_alias and I never understood how and why to use
them.

> > Right now we load everything and there is no good sorting,
> It sorts on most recently created first, but you can also click on the
> column headers including status, backend, library. There's plenty of sorting
> options.

Yes, you can click. But ideally we'd want to save the user clicks. The most
recent might already have been processed. The question was if the default
filtering makes sense and if it should be removed. We found it made a lost of
sense for the completed requests. - is there a technical reason you'd like to
remove it?

> I think ILLHiddenRequestStatuses is feature bloat from the past and does not
> bring value. Or a different way of saying it, the problem it tries to
> resolve would better be resolved in a different way. Just my opinion!

I am open to a different way, my arguments were about workflows. As I said, we
started out with it empty, but quickly were asked to filter by default. It
helped with performance, but there are also other reasons to break down the
table to more manageable chunks. If there is another better way to achieve
this, I am ok with it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.