Bug 21482 - Create a "landing page" for ILL
Summary: Create a "landing page" for ILL
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: ILL (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on: 20600
Blocks: 36164
  Show dependency treegraph
 
Reported: 2018-10-03 11:28 UTC by Magnus Enger
Modified: 2024-04-16 10:53 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Enger 2018-10-03 11:28:30 UTC
Currently, when you go to the ILL module, the first iew is of all ILL requests. This can be a lot of data, and take several seconds to load, and I doubt a lot of people will want the full list. 

So maybe we could have some sort of intermediate page with links to selections of request, based on their status, type etc. 

At it's simplest this could just be a page that displays the contents of a syspref, and that syspref could then be filled with HTML and links to filtered views of ILL requests. If the syspref is empty, the intermediate page could redirect to the full view, as it is today. 

A more advanced version would have a GUI to configure the links, order them, give them names etc. 

Thougts?
Comment 1 Andrew Isherwood 2018-11-07 13:50:29 UTC
I guess what we do here should be consistent with what other areas of Koha do. For example, going to "Suggestions" in Acquisitions loads all suggestions in a way very similar to what ILL does. Whereas "Invoices" doesn't load anything, it just gives you a form by which to specify search criteria.

I think a landing page, or dashboard, with perhaps some pertinent statistics, for example "Total of 2437 requests, 2312 completed, 3 new" etc. then links to pre-filtered displays of requests makes sense.
Comment 2 Katrin Fischer 2023-01-13 10:24:07 UTC
I think Magnus had a good thought here as we recently also changed the suggestions page. 

A general idea might be to use a tabbed table or an a pre-filter on some status that you actually need to do something about.

At the moment the table is not sorted by status, which is a bit of a usability problem, it's not really useful, you actually always need to do a search first to look for the one you want to edit/process.
Comment 3 Daphne Hoolahan 2024-04-11 13:09:04 UTC
I would be in favour too and would like to add in an option to show the ILLs for the logged in library (like we do with Suggestions).  The current list is very cumbersome for multi branch systems.  You can filter the list by Library but you have to repeat the search after every request you manage.
Comment 4 Pedro Amorim 2024-04-16 09:14:50 UTC
One question here is do we want to invest time in creating a landing page for ILL or would we prefer investing more time in creating a landing page "engine" that any module can make use of in the future?

This could be a system that considers multiple 'widgets', with each module having a default list of widgets but any staff member could pick whatever 'widgets' they want shown in their own personalized dashboard, for each module. i.e. a 'widget' showing counts, a widget allowing for a quick search, one showing quick links to different module specific deep pages, one showing all objects given a set of query params, etc.
I would personally prefer this approach, it'd take longer but would potentially benefit all of Koha, and developers would have less code to maintain.
If done on a per module basis, we'd have to improve every module dashboard, every time.

Sorry if I'm adding confusion to the discussion, that's not my goal! Curious to see what others think.
Comment 5 Magnus Enger 2024-04-16 09:31:20 UTC
(In reply to Pedro Amorim from comment #4)
> One question here is do we want to invest time in creating a landing page
> for ILL or would we prefer investing more time in creating a landing page
> "engine" that any module can make use of in the future?

That sounds like an awesome idea!