eikek
[Feature Request] Pagination in list view
Hi! Thank you very much for docspell, it saved me a lot of time!
I was thinking that it would be very convenience to hava pagination in item list view when there are lots of documents to look through. For example, I have 20k+ pdf documents to look through, i can't easily continue what I was doing yesterday. And the major disadvantage of the "Load more" solution is that it's not possible to load all the 20k+ items in one page. So, may be a pagination solution is more suitable for the item list view?
Hi @ohagene - thank you for your thoughts! I'm a bit reluctant to add a complete pagination I have to admit. It is always a bit of a hassle to implement (but it should be possible with the current api). When I have to do something like this (going through many documents), I usually use a query and then "mark" all visited documents with a tag or custom field. Then when you go back to the list, it will update and already visited items are gone (if the query is accordingly). Would this work for you as well? Or otherwise can you elaborate maybe more?
For loading more items in one page: you could increase the hard limit in the configuration file if you want (and then also in the ui) But loading 20k documents may slow the site down quite a bit. To me using a tag or custom field for already visited documents seems the better approach right now (I might not understand your exact use case, though, of course), because looking at 20k documents would feel a bit overwhelming for me.
Hi @eikek. Thanks for the swift reply. The solution you provided seems the better approach right now. But I thought just jump to a page directly might be more graceful than tagging all visited documents.
Anyway, thank you so much for the great project! I have some other ideas that have nothing to do with pagination, may be a new issue is more suitable for that.
You're welcome! Thanks for your kind words! Sure, create issues for things you like to address, no problem! Also, I'm not against adding pagination at all - I see that it can be useful. It is not a high prio for me right now. I leave this issue open and at some point it may arrive :). It is only client side and could actually be made optional (like a setting in ui settings). There's nothing to loose :-)