search

PTFS-Europe / rebus-list-2

rebus:list 2+ issue tracker repository
0 stars 0 forks source link

Reset Sort - Hierarchy Management #186

Open mrenvoize opened 8 years ago

mrenvoize commented 8 years ago

Add a 'reset sort order' in the hierarchy to allow direct children of a taxon to be automatically sorted by taxon name alphabetically.

mrenvoize commented 8 years ago

I built a one time script to do this for BUCKS so I have the backend code for it now.

@AndrewIsh We need to come up with a suitable API call for it.

mrenvoize commented 8 years ago

We should perhaps allow for an automated regular run of this across the whole hierarchy too for those that want it.

AndrewIsh commented 8 years ago

+1

AndrewIsh commented 8 years ago

Requested by Sunderland https://github.com/PTFS-Europe/rebus-list-2/issues/141#issuecomment-248583593

mrenvoize commented 8 years ago

Questions to answer before starting implementation:

  1. Should sorting be UI driven, or a background task driven. (i.e. should it be a set and forget configuration option, or a user accessible function) ?
  2. Should we sort on 'Name' OR 'Course ID' OR ... ?
  3. Should we ignore 'Articles' ('the' etc
  4. Should we be alpha sorting, numeric sorting, or alpha numeric sorting
  5. If 'UI Driven':
    • Should we allow this as a full hierarchy sort, or sort per level (i.e have a 'Sort Children' button)?
    • Should this be an 'immediate' action, large sorts could take a few seconds to complete and thus lock the hierarchy for a few seconds before being editable again.
VicWatt commented 7 years ago

Here are my thoughts from our perspective: 1 - either would be an improvement on the current situation but a set and forget config option would be better 2 - I think this would have to be primarily course ID but a secondary sort on Name 3 - From our perspective ignoring Article should be ok 4 - Alpha numeric as our course IDs contain both and some lists only have alphabetical information (for cross-school generic lists) Sort per level is maybe more work intensive if UI driven but safer in terms of locking the hierarchy Could the action be triggered by the addition of a new course ID/name - basically the feedback I've had from our librarians is, can we have it the same as legacy rebus (RL1)?

janetc commented 7 years ago

Response to Martins queries on Nov 10th from Elizabeth at Bucks:

1) Should sorting be UI driven or a background task driven? (i.e. should it be a set and forget configuration option, or a user accessible function)

Can it be both - worry with it being part of the configuration is if it is not obvious people will not find it.... 2) Should we sort on 'Name' OR 'Course ID' OR ...? Name in the first instance for us but know others will want course id?! 3) Should we ignore 'Articles' ('the' etc Yes 4) Should we be alpha sorting, numeric sorting, or alphanumeric sorting If name Alphanumeric as names can have numbers in the list names. Obviously, if course then I suspect numeric is better. 5) Should we allow this as a full hierarchy sort, or sort per level (i.e have a 'Sort Children' button)? Sort children would work for us as we have only one box. You may want to ask a couple of users with hierarchies on this one rather than us. Immediate would be nice or scheduled may be - similar to the reports scheduling?

mrenvoize commented 7 years ago

So to summarise, customers would like:

1) To be able to configure which field(s) to sort on by default (None, Title, Course ID, ?) 2) To sort naturally (alphanumeric sort with 10 coming after 9 as opposed to 1) 3) Optionally ignore articles (the, a) when sorting 4) Sort at 'list addition time' 5) Resort on any related preference change 6) Allow for 'Enforced/Default/Manual' sort modes where 'Enforced' means lists will 'Always' be sorted by the system, 'Default' means lists will be sorted at addition time, but can be manually overridden and finally 'Manual' means lists will always be appended and then the user is expected to manually reposition them to the correct location.