Feedback from a fellow paperless-ngx user #104
Replies: 2 comments 2 replies
-
Hi Jonas, first of all thanks for your kind words, I really do appreciate it! It's always nice to get some valuable feedback from users, and active contributors of Paperless (you especially) that know the capabilities of paperless-ng(x) and have it integrated into their lives. I currently do not yet have the need to archive and index that many documents, therefore I would consider myself a very basic/naive user who doesn't use most of Paperless's capabilities (as of now, I'm sure that will change in the near future, thanks to good old German bureaucracy).
These are very good ideas and I will consider them in the next release cycles. The search is fairly new and I basically just implemented the M3 design spec.
That's good to know! I am not really familiar with the workflows of using and assigning ASNs, I've followed some discussions here and there and there seems to be multiple ways of doing so. I agree that the way it is currently implemented is highly opinionated and doesn't allow for much flexibility, which probably had to do with a lack of understanding. I think it might be a good idea to also display the next available ASN on the scanner page before any pages have been scanned. What do you think about that? Would that be a benefit or do you essentially only look at the last physical ASN on the latest document in your binder? Just out of curiosity, if this is the intended workflow, wouldn't it be beneficial to also be able to specify the ASN on document upload (just like correspondent, created date, tags, and document type)? Or are there technical limitations to this approach?
You're right, it is currently sorted by date, I will adjust this.
This should also be very easy to implement and fairly obvious to the user once implemented. I've had requests that scrolling down would open the preview, but I think just tapping is easier, maybe not as fancy but functional.
I've seen this and part of it is already implemented. However, from what I've seen the response is html format, I'll have to see how that complements with the rest of the app as I've not really played around with the HTML renderer. But, specifically with the "new" detailed view, this might be a useful addition to make it actually detailed :D
Hm, I've never used it with a running VPN, but greyed out buttons mean that your device doesn't have a connection to the internet. Could have to do with the VPN, but I'm not sure. Best regards, |
Beta Was this translation helpful? Give feedback.
-
Ah, regarding this:
I'm not entirely sure what's the best option here. Maybe only show a badge if there exist suggestions for an unset field, i.e. if only correspondent is not set and there are suggestions for correspondents, show a "1" and so on... At least from my intention, inbox tags should be handled in the dedicated inbox. |
Beta Was this translation helpful? Give feedback.
-
Hello!
This is a great application, and its easy to notice you've put a lot of effort and thought into it! It's great so see things like this happen :)
I do have a couple recommendations through on what to improve, in no particular order, and looking at the app as a naive user. Maybe you find some of them useful! Most of them are just minor nitpicks though.
When searching for document, debounce input in the search bar. This means that a server request to load autocomplete recommendations is only made when the user stopped typing (for about a second, maybe). I've had cases where I was typing "amazo", and the first recommendation is "amazing", since loading recommendations for "amaz" took longer than loading recommendations for "amazo".
Autocompleting multiple words would be nice. Google has a very elegant solutions on their search boxes, touching a recommendation searches for it, touching the arrow next to it copies it (with a trailing space) to the search bar to continue typing in the query.
ASN: I'd prefer an option to manually enter (and edit) the ASN of any document. I don't really know how users use this, but the way I initially intented this to work was in the following way:
Maybe you can enlighten me how you use it, and I can adjust my workflow.
I think search results and similar documents are sorted by date? I'd consider sorting them by relevance. This way, documents that better match the search query (or are the most similar to a document) appear first. Just pass ordering=score to the api.
Also related to the search results, the API also sends fragments of the document content with the search terms highlighted, formatted in HTML. Its visible in the web app on search results when you select the large cards. Combine that with sorting by relevance for even better search :)
On the document details page, tapping the partial preview image on the top above the tabs could open the preview.
Sometimes, the document edit button has a badge "1" attached to it. I figured this appears when there is an edit recommendation? I like the idea, however, this also appears on documents where I verified that the date / correspondent / etc is correct. Sometimes, the date parsing logic finds multiple dates in a document, and those are getting recommended, resulting in the badge, and implying that I still need to edit the document. As a workaround, maybe only display the badge when there's an inbox tag on the document? Not sure.
In the document list, when selecting the most compact "list" view type, there's lots of border around the small preview images. I think it wouldn't hurt to make the borders smaller, resulting in larger previews.
And lastly, some weird observation I made, where I'm not sure if its a bug or not.
Best regards,
Jonas
Beta Was this translation helpful? Give feedback.
All reactions