Sorting on collection dashboard
EvaMLang opened this issue · 18 comments
Sorting possibilities are missing for
- docID
- Statistics
Works perfectly fine for fields
- image (does this make sense? why should you sort by image?)
- document title
- description
- author
- pages
- language
Refers to library view rather than dashboard ie https://transkribus.eu/readTest/library/2305
appears to be done already
Sorry for my ignorance on wording here, yes - library should be the correct title.
Test OK for sorting by docID.
Test failed for sorting by Statistics - would expect (at least) string comparison
One more thing - why would sorting by "image" be a considerable option? Does this make sense after all?
If used this also introduces wrong images to the respective documents...
Hi Eva,
Thanks for your feedback and screen shots :)
You are correct, sorting by image is a bit of a nonsense.
On the statistics I notice that the sorting is not functional. I think this may be because they are loaded with ajax separately whereas the rest of data is loaded when the table is initialised. This means he datatables library is not able to use the statistics for sorting. @hackmanschorsch and I have implemented it this way because the loading time would be too great if the statistics were calculated and delivered for all the results. The solution is to just fetch those that are needed for the page.
The outcome is that we'll need to remove the sorting option from the statistics column, sorry!
Rory
Hi Rory,
could we possibly revisit this functionality at a later stage? There would be a clear use case from collection management perspective for the sorting-by-statistics feature - especially with regards to tracking the status of crowd sourcing progress...
Eva
Maybe a REST function would be helpful here to retrieve a sorted list of a collection for the given sorting parameter (set)? I could envision things to be much faster on REST level than on webserver level - but this is only a feeling...
I agree with the above and would suggest that the statistics can be better presented too (rather than the string in a table cell we currently have).
The datatables are capable of using the REST services more. This was something that we made use of originally, but was switched back to loading all the data when the sorting and search were added. We'd need to ensure a comparable sort and search functionality via the REST services to ensure there would be no loss of functionality when switching back.
More use of REST would have the advantage of speeding up the table load time too. One to coordinate when @hackmanschorsch is back in action, as it was he who added the search and sort and made the switch away from REST.
Once that is done we could revisit the way that stats are loaded (and displayed).
For now though I suggest we either make some new issues (or find existing ones) to deal with
- data tables using ajax/REST with search and sort (Transkribus/TWI-library#9)
- statistics display (Transkribus/TWI-library#9)
And test this solution on the basis that is a workaround to the non-functional sorting that @EvaMLang identified originally.
Thanks,
Rory
Test questions:
- What should sorting by "Documents" do? What will be listed there? A full list of documents in that collection?
- Sorting by ID, Collection Name, Description, My Role now works - however, the column widths vary depending on the length of the content in the column (see screenshots for sorting by Role)
Documents should contain the number of documents for each collection. Seems there is a problem in showing these numbers at the moment.
Regarding the presentation: Agree to present the statistics in a much nicer way so that sorting is possible also for those numbers.
Not sure if we should sort and search via rest services. Thought about this a while ago and came to the conclusion that sorting would work quiet well but searching in the way datatables do would need one request for each typed character. And I assume that this cannot keep up with the solution if the data is already loaded at the client side. Other opinions on that?
@maxbry @jnphilipp @kansallisarkisto - any further ideas on the sorting issue / presenting statistics / datatables vs. ajax/REST?
Sorting handles confuse me - intial setup now would allow for
- sorting by images (sorry, makes no sense for me)
- sorting by view (sorry, makes no sense either)
- sorting by stats (yay, this is what I would like to have)
Would also expect
- sorting by "Document title and description" (behavior: sort by document name)
When I toggle one of the buttons, the sorting handles for sorting by view are gone, only sorting options 1/3 above remain
Again: would expect sorting by name and stats, nothing else...
Thanks
Please see my previous comment - still needs fixing
Removed sorting from columns where it doesn't make sense.
Currently sorting on all columns where
a) It make some sense and...
b) It is technically possible at present
@hackmanschorsch has a solution. We can pre-load the title and allow sorting by this and then the secondary ajax call will replace title with the title/description string!
Sorting now works smoothly for columns "Collection Title and description", "No. of Docs" and "My role" when on collection table (https://transkribus.eu/readTest/library) and on columns "Document title and description and "pp." for document level.
What I still miss, is sorting via the "Stats" column. @cziaarm: Is this considered technically impossible at present?
I would attribute "partially fixed" to this issue - should I move the sorting by stats into a new issue?
Hi @EvaMLang ,
Yes, please make a new issue for ordering by stats (If you are happy that the other elements are working as expected).
Happy to close this issue. Discussion on stats is carried over to Transkribus/TWI-library#20