5.2 search bug? (NOT A BUG)

Johnny Doomo · October 21st, 2005, 05:06 PM

I don't know if this is a search bug or what, but IMO it seems like some type of bug.

I submitted 3 files:

clean_1920x1200
logo_1920x1200
guns_1920x1200

I gave them no title, description or keywords so that it used the file name as the title and as the keywords.

When I do a search for 1920x1200 it doesn't pull up any results. Shouldn't it at least pull up these 3 files? I also tried *1920x1200* as I thought the wildcards might make a difference (though really the search feature should find anything with 1920x1200 in it if not specified) but there was still no difference.

Chuck S · October 21st, 2005, 06:38 PM

Nope this is not a boolean search feature 1920x1200 must have a space between to be considered

Johnny Doomo · October 21st, 2005, 07:00 PM

What do you mean a space? The file name doesn't have a space so shouldn't it find it? How does a "boolean" search work versus whatever Photopost has?

Michael P · October 21st, 2005, 10:14 PM

Quote:

$keyphrase .= "((title LIKE \"% $key%\" OR description LIKE \"% $key%\" OR keywords LIKE \"% $key%\" OR bigimage LIKE \"% $key%\"
OR extra1 LIKE \"% $key%\" OR extra2 LIKE \"% $key%\" OR extra3 LIKE \"% $key%\" OR extra4 LIKE \"% $key%\" OR extra5 LIKE \"% $key%\" OR extra6 LIKE \"% $key%\")";
$keyphrase .= " OR (title LIKE \"$key%\" OR description LIKE \"$key%\" OR keywords LIKE \"$key%\" OR bigimage LIKE \"$key%\"
OR extra1 LIKE \"%$key%\" OR extra2 LIKE \"%$key%\" OR extra3 LIKE \"%$key%\" OR extra4 LIKE \"%$key%\" OR extra5 LIKE \"%$key%\" OR extra6 LIKE \"%$key%\"))";

As you can read from the code snippet above, we look for:

- Words that start with the keyword in all fields
- Words that end in a keyword (title, description, keywords, bigimage)
- Patterns that appear with extra fields (can be contained within the string)

If there are better ways, I am open to suggestions.

Johnny Doomo · October 25th, 2005, 12:40 PM

How about searching the actual keywords? What's the point of the system adding keywords if it doesn't even search them? I mean if the image title is one of the following

clean_1920x1200
logo_1920x1200
guns_1920x1200

and it adds those same words to the keywords for each image, wouldn't you just assume that a search for "1920x1200" would pull up those images? Is it just me or does it seem kind of stupid for it to not pull up those images as the results if 1920x1200 is what's searched for?

Michael P · October 25th, 2005, 01:44 PM

Go back and re-read what I wrote and what I outlined for you. It'll help you if you actually read my responses.

What you are talking about is searching for letters within a word. Just because you search for "ord" doesn't mean anything with "word" is a reasonable match; or search for "is" and returning "this" and "crisis" and "sister" is reasonable. Most people are searching for the word "is", right?

By all means, feel free to modify the search query to suit your need.

Johnny Doomo · October 25th, 2005, 02:51 PM

Sorry, everything in the box from your first reply just looks like jumbled characters to me. Would it be hard to make it so that IF the user wanted to search for ord and pull up all results that they have the option of using wild cards like *ord* ?

I don't know. Maybe the problem comes from Photopost adding underscores to filenames with spaces in them. So if you have "guns 1920x1200.jpg" the system changes it so the keyword is "guns_1920x1200" instead of "guns" AND "1920x1200". It just seems not very friendly that for a file you upload with the actual name that has 1900x1200 in it and the system auto creating the keyword from the title that doing a search for 1920x1200 won't pull up that file name.

I guess in my mind I would just assume that it would.

Michael P · October 25th, 2005, 02:57 PM

Because you can't bring up a URL with a space in the name; i.e. "guns 1920x1200.jpg".

Wildcards aren't an option at this time, but it's something we could consider.

Johnny Doomo · October 26th, 2005, 11:58 AM

It doesn't have a space in it, it has an underscore as Photopost converts it to that. (Is that what you meant?)

Chuck S · October 26th, 2005, 12:12 PM

Basically the search does not use wildcards as Michael states.

If a title is this it will be found searching for guns or 1920x1200

guns 1920x1200

But not

guns1920x1200.jpg

Johnny Doomo · October 26th, 2005, 12:54 PM

nope, 1920x1200 won't pull up results. Remember that hack that we added that would add an underscore to the keyword so that the keyword would match up with the title of the image?

Since Photopost replaces spaces in the title for underscores if the title is not entered, then the system also adds an underscore to the keywords as well, so that that keyword works with that image. The reason we wanted that was because if you didn't, then you click the keyword for that image, and the results don't even bring up the image that you clicked the keyword from. So it puts an underscore in the keyword. So then the keyword and title are "gun_1920x1200". Doing a search for 1920x1200 won't pull up the image in the results.

I don't know how to fix it, but maybe it would be easier if it could just allow spaces in the image title. Because then you wouldn't have to mess with the keywords putting underscores and then 1920x1200 probably would pull up that image in the results.

Do you have any ideas for a work around or something that might work better?