I thought non-ISO-formatted dates would be neat, too, and did a bit of looking for a date parser that supported internationalization, but (like most of npm), were either English-only, had no tests, had been abandoned, or all of the above.
Just as more feedback… I do want to deal with date ranges a lot, but personally never seem to use the “natural language” type date formats (last week, etc.). Maybe it’s the programmer in me that finds them too ambiguous (or I’m just too old :-)).
Anyhow, I certainly don’t mind if they are there for folks that like them, I can see the use, but just to toss in my 2 cents…
I’m also a programmer and yyyy-MM-dd is the only thing that I prefer most of the time, but as your product’s supposed main audience is non-IT, I assume date:"last summer" is more preferable to type than after:2020-06-01 AND before:2020-09-01
fs:=a/b/c matches /photos/a/b/c/file.jpg assuming that /photos is a single root of your photo library. But I think you support having multiple roots so it will also match /other/a/b/c/file.jpg and that makes := to mean what it actually isn’t.
Moreover, with that logic how can you find fs:=photos/a/b/c when you want to filter only the photos root folder? How to make the syntax not ambiguous so it won’t mistakenly include /other/photos/a/b/c/file.jpg?
The solution is to provide an “absolute path” to the tag your want to match.
tag:=foo/bar means match all assets directly associated to tags that end with foo/bar. I think it will be helpful for who:=michael to only match first names.
tag:=/foo/bar means match all assets directly associated to tags whose path exactly matches /foo/bar. You have to include the entire path.
So to avoid files in /other/a/b/c/, you’d use fs:=/a/b/c.
Note that the fs: search terms currently hit the tag fts index. I’ll be adding an asset fts index as well, which will include title, description, and metadata terms at some point in the future.
Also it’s a bit unclear about fs, description says we query asset’s pathname, but don’t you think we should also be able to query filename? Maybe you should rename fs to path and also add an ability to query filename? Or maybe even fullname that will include both path and filename?
Also I think it’s essential to add a Lightroom’s killer feature where you can search any text and it will find all the assets that include that text in any tag. So you type something like text:michael and it will find everything including /photo/michael/123.jpg, /photo/a/michael.jpg, who:michael and even city:michael
YES! This is absolutely how I want “filterless” queries to work.
Instead of text:michael, though, it’s just micheal, just because that’s going to be simpler to type. I don’t expect many people will get into filtered queries and operators: I expect them to want to type “beach sunset” and get something reasonable.
