Quote:
Originally Posted by chaley
Are talking about arbitrary searches as search restrictions? If so, then the code is now in trunk.
|
Yes I was talking about that feature, thanks for adding. I will wait for your feedback and thoughts on that latest beta before I make use of it though.
Quote:
|
I have never tried to sort by the marked field, but it should work at the db level. However, there is no provision at the GUI level to do it. It would be easy to add, if there is a use case for it.
|
Yes I did say "in theory"
. What I had in mind was that if there is a view like "Show all duplicates", that perhaps the default sort applied should be by the "marked" column. So when they first see the results, all of the groups would be kept together on screen - the user wouldn't be able to see where one group starts and the next ends of course, but if this is being used in conjunction with highlighting then the highlighting would sequentially move down the screen as they move to the next group. Plus in the case of "not duplicates" forcing a group to be partitioned, the group numbers would sequentially be one after another, so at least in this view without the user even trying to sort by title they would "usually" see the next group for the related book next to it.
I say "usually" because it depends on how many other groups that book is in as to whether it will sort next to it. In a happy case, the marked column would be like this:
Say you have Group 5 of (11,12) and Group 6 of (11,13), caused by a duplicate exclusion in place between (12,13).
book 11 is marked 'duplicate_group_0005,duplicates'
book 12 is marked 'duplicate_group_0005,duplicate_group_0006,not_dup licate,duplicates'
book 13 is marked 'duplicate_group_0006,not_duplicate,duplicates'
So sorting by marked text will in this case put them together on screen.
If however book 13 also happens to be part of a group 1, then book 13 is marked: 'duplicate_group_0001,duplicate_group_0006,not_dup licate,duplicates'
So initially it will sort at the top in group 1, not next to the members of its second related group of group 6. However if the user processes their duplicates sequentially and resolves group 1 first, then the marked text for book 13 would be updated to remove that duplicate_group_0001 and it would appear as per my initial example above in the right place. So basically a book that was in multiple groups (assuming it is the "winner" of any earlier merges) will progressively move down the screen to be displayed with its next associated merge group.
It's just a theoretical approach to displaying all duplicate groups at once
. And as marked is not a visible column, the user could "break" the sorting at any point by clicking on a column heading, though I would keep re-applying it every time they move next/previous.
Quote:
|
Will try the new version soon...
|
Excellent, as always look forward to your feedback.