View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005024 | MMW v4 | Properties/Auto-Tools | public | 2008-12-11 10:47 | 2015-02-05 15:13 |
Reporter | Ludek | Assigned To | |||
Priority | high | Severity | minor | Reproducibility | always |
Status | feedback | Resolution | open | ||
Product Version | 3.1 | ||||
Target Version | 4.0.7 | ||||
Summary | 0005024: Advanced queries based on dates relative to the present | ||||
Description | This was originally raised in 0004609 by Bex. 4) I miss a PresentYear (if introduced perhaps rename Present to PresentDate). LastYear would also be nice but even better if you could add "modifiers" after PresentYear/PresentDate. I.e -X Year,Month,Week,Day Example: (Date='2008-12-10') PresentYear -2 Year = 2006 PresentDate -2 Month = 2006-10-10 That would also take care of point 2 above (Years ago condition). 5) It would also be nice to be able to search specific dates in the other date fields that exists: (It has been requested.) - Added - Last Played - Timestamp (shouldn't this be renamed to File Modified? Both here and in the main window.) I also miss Track Modified in the search as well as in the main window. | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
related to | 0004609 | closed | Ludek | MMW v4 | Allow date queries based on time relative to the present |
related to | 0004794 | closed | MMW Wishlist | Users want a "date added" criteria | |
related to | 0005215 | closed | Ludek | MMW 5 | Implement sort by DATEAdded (not DateTimeAdded) |
related to | 0006022 | closed | Ludek | MMW v4 | Advanced queries: Several Date fields can't search by specific date |
related to | 0007375 | closed | Ludek | MMW v4 | Advanced search / autoplaylists: ability to sort on timestamp |
|
Reminder sent to: jiri, rusty Re 4) I would rather resolve this by adding new following checkbox: [x] Relative to present By checking this checkbox and selecting ['Date','>','2007'] will mean that after year the condition will be automatically changed to ['Date','>','2008'] Similarly ['Date','between','1.1.2007;1.7.2007'] will mean that after week the condition will be automatically changed to ['Date','between','8.1.2007;8.7.2007'] This way we will give users the maximal flexibility and UI complexity will retain at the almost same level. Re 5) I agree on both that we should join the conditions for 'Date', 'Added', 'Last Played' and 'Timestamp' in order to give users more flexibility. And that we should rename 'Timestamp' to 'File Modified' Rusty, Jiri, what do you think? |
|
Re. 4) I believe that 'Relative to present' would be quite unintuitive, and even more confusing when it came time to editing a query. That said, the original proposal would probably result in a fairly messy UI. 5) Has been moved to 0006022 and 0005215 |
|
If you think that 'Relative to present' would be unintuitive then I would suggest to add the conditions '> (days ago)' '< (years ago)' ... , it could be more intuitive, but would add amout of new conditions. Nevertheless it would be better than the original proposal, as you said "The original proposal would probably result in a fairly messy UI." |
|
Queries based on dates relative to the present has already been implemented for Added, Last Played, Timestamp fileds (in the manner suggested by Ludek in the previous comment). It hasn't been implemented for Date, though (probably only the 'years' ago options are relevant, though). p.s. It would be fine to change 'timestamp' to 'Date Modified'. |