using headers for search syntax ?
using headers for search syntax ?
Hello again, in the header section such as (date taken, camera maker, camera model) how can I use a search syntax in the search field? for example typing : *.jpg camera-model:sm-g930w8 ?
Re: using headers for search syntax ?
Right click a column header and click Search for <property-name>.
This will paste the related search function into the search box.
For the search function syntax, please see: Search Functions
Search Modifiers can be used with Search Functions which will mix up the syntax.
For example: regex:camera-maker:^mycam
date-taken:
camera-maker:
camera-model:
This will paste the related search function into the search box.
For the search function syntax, please see: Search Functions
Search Modifiers can be used with Search Functions which will mix up the syntax.
For example: regex:camera-maker:^mycam
date-taken:
camera-maker:
camera-model:
Re: using headers for search syntax ?
Oooo I see thank you!!!!!
Re: using headers for search syntax ?
I've tried regex:date-taken:!=dc: but the results which have date taken matching date-created are still showing....
Re: using headers for search syntax ?
Why "regex:" ?
regex: could be there, but in any case you would not want it as "part of the" date-taken:
So you could have something like,, but then, why regex: ?
I can do, date-taken:=dm: or date-taken:!=dm:, with both returning expected results.
Or anything along these lines...
(The first regex: example in the block above serves no purpose.)
regex: could be there, but in any case you would not want it as "part of the" date-taken:
So you could have something like,
regex: date-taken:
I can do, date-taken:=dm: or date-taken:!=dm:, with both returning expected results.
Or anything along these lines...
Code: Select all
regex: date-taken:!=dm:
"C:\My Documents\_Pics\_gif" date-taken:!=dm:
date-taken:!=dm: ext:gif
regex:blue.*cats date-taken:!=dm:
Re: using headers for search syntax ?
There should be two results from my iphone which date taken does not equal date created but somehow it gives all results including date created = date-taken. I've used
date-taken:!=dc:
dc:!=date-taken:
none of them work for me. Under menu item Search --> enabled ignore puncuation, enabled ignore whitespace. Still the same results. What am I doing wrong...
date-taken:!=dc:
dc:!=date-taken:
none of them work for me. Under menu item Search --> enabled ignore puncuation, enabled ignore whitespace. Still the same results. What am I doing wrong...
Re: using headers for search syntax ?
Is it only these two particular files that are not turning up correct?
What kind of time frame (difference) are we talking?
Not sure if "millisecond" is taken into consideration here or not, but very well may be?
(I know that on video length comparison, "ms" is taken into consideration, (or maybe that was with the Find Duplicates function ?) & that can throw things off. [Probably on the Find Dups, I'm thinking?])
What kind of time frame (difference) are we talking?
Not sure if "millisecond" is taken into consideration here or not, but very well may be?
(I know that on video length comparison, "ms" is taken into consideration, (or maybe that was with the Find Duplicates function ?) & that can throw things off. [Probably on the Find Dups, I'm thinking?])
Re: using headers for search syntax ?
It seems to me like, something keeps glitching either within everything or with my iphone se. I had to restart my computer twice but sometimes it works sometimes it doesn't
Re: using headers for search syntax ?
date-taken:!=dc:
Will find files where the date-taken and date-created differs by 100 nano seconds.
Which will most likely be every single file on your computer.
To find files where the date-taken and date-created differs by 1 second or more, please try the following search:
eval:$date-taken:/10000000!=$dc:/10000000
Will find files where the date-taken and date-created differs by 100 nano seconds.
Which will most likely be every single file on your computer.
To find files where the date-taken and date-created differs by 1 second or more, please try the following search:
eval:$date-taken:/10000000!=$dc:/10000000
Last edited by void on Sat Apr 30, 2022 12:00 am, edited 1 time in total.
Reason: fixed search
Reason: fixed search
Re: using headers for search syntax ?
well im not looking for an exact second or any specified time duration but I'm looking for entries where the date taken and date created is different no matter how long the duration ie. any time difference
Even for files where the date taken is exactly equal to the date created, no files appear by using this syntax:
dc:=date-taken: or dc:==-date-taken:
no files appear in the search results
Even for files where the date taken is exactly equal to the date created, no files appear by using this syntax:
dc:=date-taken: or dc:==-date-taken:
no files appear in the search results
Re: using headers for search syntax ?
Sorry, there was a few mistakes in my previous search.
Please try the following search:
eval:$date-taken:/10000000!=$dc:/10000000
This will find files that differ by 1 second or more.
Typically, $date-taken: will differ from $dc: by a few nanoseconds.
They will most likely never be equal.
Please try the following search:
eval:$date-taken:/10000000!=$dc:/10000000
This will find files that differ by 1 second or more.
Typically, $date-taken: will differ from $dc: by a few nanoseconds.
They will most likely never be equal.
Re: using headers for search syntax ?
but why doesnt the initial date-taken:!=dc not work ? because the syntax is so simple...
Re: using headers for search syntax ?
Because date taken and date create are FILETIMEs.
FILETIMEs have a 100-nanosecond resolution.
Everything only shows year/month/day hour:min
But the timestamp resolution is higher.
So your file might have the following date taken timestamp:
2022-04-30 13:26:00.0000000
and your file has the following date created timestamp:
2022-04-30 13:26:00.0000001
date-taken:!=dc will compare the full 100-nanosecond timestamp, not the year/month/day hour:min which you might expect.
You can change your time format to show 100-nanoseconds, which might make this more obvious:
To restore the default time format:
FILETIMEs have a 100-nanosecond resolution.
Everything only shows year/month/day hour:min
But the timestamp resolution is higher.
So your file might have the following date taken timestamp:
2022-04-30 13:26:00.0000000
and your file has the following date created timestamp:
2022-04-30 13:26:00.0000001
date-taken:!=dc will compare the full 100-nanosecond timestamp, not the year/month/day hour:min which you might expect.
You can change your time format to show 100-nanoseconds, which might make this more obvious:
- In Everything, type in the following search and press ENTER:
/time_format=HH:mm:ss.SSSSSSS
To restore the default time format:
- In Everything, type in the following search and press ENTER:
/time_format=
Re: using headers for search syntax ?
Ohhhh now that makes sense....but that doesn't that kind of defeat the purpose ? If you want to compare two files which have different date and time, it only compares the nanosecond....
Re: using headers for search syntax ?
Everything also compares the nanoseconds, which makes date-taken:!=dc impractical.
I will consider only comparing with minute resolution when using date-taken:!=dc.
Thank you for the suggestion.
Adding a date-taken-day: property might also be a possibility for date-taken-day:!=dc-day
I will consider only comparing with minute resolution when using date-taken:!=dc.
Thank you for the suggestion.
Adding a date-taken-day: property might also be a possibility for date-taken-day:!=dc-day
Re: using headers for search syntax ?
hmm maybe compare all 3 like....date (in number), month and year...for comparing two dates in addition to timing??
Re: using headers for search syntax ?
Yes, date-taken-day: would compare in days.
I'll look into handling time as well.
eval: will give you more control:
Compare with second resolution:
eval:$date-taken:/10000000!=$dc:/10000000
Compare with minute resolution:
eval:$date-taken:/600000000!=$dc:/600000000
Compare with hour resolution:
eval:$date-taken:/36000000000!=$dc:/36000000000
Compare with day resolution:
eval:$date-taken:/864000000000!=$dc:/864000000000
I'll look into handling time as well.
eval: will give you more control:
Compare with second resolution:
eval:$date-taken:/10000000!=$dc:/10000000
Compare with minute resolution:
eval:$date-taken:/600000000!=$dc:/600000000
Compare with hour resolution:
eval:$date-taken:/36000000000!=$dc:/36000000000
Compare with day resolution:
eval:$date-taken:/864000000000!=$dc:/864000000000
Re: using headers for search syntax ?
yes something like that..for more accurate control...than just nanoseconds