Model, Outfit, Location

[koolestani]

So I encountered this situation where I wanted to look up all the various outfits that a model has been photographed in.
I have two txt files placed in folders of every shoot, one txt named after the model and another txt that is named "outfit-(description.of.outfit).txt", which, as the name suggests describes the outfit worn by the model.
d
├── 2014.09.15
│ ├── model.a.txt
│ └── outfit-desc.a.txt
├── 2014.10.16
│ ├── model.b.txt
│ └── outfit-desc.z.txt
├── 2014.09.19
│ ├── model.a.txt
│ └── outfit-desc.b.txt
├── 2014.09.23
│ ├── model.a.txt
│ └── outfit-desc.c.txt

So if I search

outfit txt

, I will be shown all the outfits worn by all the models, I obviously want to narrow it down to all outfits worn by one specific model. Maybe some syntax already caters to what I want to do here, but I cannot figure out what that might be.

I could search

child:model.a child:outfit

but that would display the folder that contains both these files, but I want to see the "outfit-(description.of.outfit).txt" file in the results.
On the other hand, if I search

model.a outfit

OR

<model.a> <outfit>

, this expects both the terms to be present in same filename.
I want to see the description of all the outfits worn by one particular model.

I would also like to know if the solution of this situation can be expanded to three pieces of information, for example if I had three txt files, one named after the model, other named "outfit-(description.of.outfit).txt" and third named "location-(description.of.location).txt".
Now I'd provide lock down any two variables, like model name and location and would like to see all the situations where these two variables (that are now basically constants as they have been defined) intersect with the third variable.

So that means all the locations where a specific model was wearing a specific outfit.
Or all the outfits worn by a specific model at a specific location.

[void]

Please try the sibling: search with Everything 1.5:

outfit txt sibling:model.a

sibling:

[koolestani]

As always, it blows my mind how Everything has taken, well... Everything into consideration. I doubt I will ever stumble into a situation that you haven't already thought of and designed for.

Thanks

[koolestani]

If the question was slightly tweaked and now the

model.a

file was one directory up than the

location-<desc>.txt

and

outfit-<desc>.txt

files. Would a similar search still be possible?

To be precise, the directory structure looks like this:
d
├── 2014.09.15
│ ├─ model.a.txt
│ ├─── tags
│ ├───── location-desc.a.txt
│ ├───── outfit-desc.z.txt

[NotNull]

You mean the following structure?

Code: Select all

d
└───2014.09.15
    │   model.a.txt
    │
    └───tags
            location-desc.a.txt
            outfit-desc.z.txt       
            

Try the following:

Code: Select all

outfit*.txt   exists:$parent-path:\\model.a.txt

This should show all outfits model.a has been wearing.

[koolestani]

This doesn't seem to be working for me. I even removed the extra spaces between

outfit*.txt exists

but that didn't change anything. I'm on version 1.5.0.1337a in case the functions used in the query are very new or something.

[NotNull]

This doesn't seem to be working for me.

You need to be more specific than that ....



In the meantime I tested the searchquery: here it gives the expected results.
HOWEVER: Not when there is a space in "model.a.txt"

In that case, the filename needs to be in quotes (as usual):

Code: Select all

outfit*.txt  exists:"$parent-path:\\model a.txt"

[koolestani]

Well, a folder structure where this exact scenario is applicable doesn't show the txt files in the results. The results are blank actually. I'm not sure but it looks like the

exists:

function is not working at all on my end.

[void]

1.5.0.1337a doesn't support substitution.

Please try the latest Everything 1.5 version.

Please specify your model.a.txt filename exactly.



I will look into support for a parent-sibling: function and an ancestor-sibling: function.
I will look into support for wildcards (for the name part) when using exist: