Messages - qforce [ switch to compact view ]

Pages: prev1 [2] 3 4next
6
BTW, AutoFocus is also base partially on Lucene so that should make it quite familiar to you...
All the best.
It looked fairly interesting until I read the hardware requirements section...

7
That's exactly what I'm getting at. I don't know of any other tool that can search through, e.g., ACDSee's database. However, any photo album app will allow you to save tags into EXIF or IPTC metadata in the images themselves. And since this is a standard, any desktop search app worth its salt can access it.

Having done that, now I can use my search app to find, say, "Mexico 2008" and get all my related photos, emails exchanged with the travel agent, and the AVI of the time-lapse sunset I made. Sure, all of these things are handled through different apps. But the ability to search like this allows me to have all of the materials related to a given project in front of me at once. (Which is why I also think that the Windows way of organizing files under "My Documents" in app-centric folders is idiotic)
Some people are just too lazy to add half a dozen tags to each and every image they store on their computer. Do you really do that? :o
On a related note I'd like to mention delicious.com, a social bookmarking site. This site allows you to assign multiple tags to a bookmark. which sounds awesome in theory (multiple categorization, yay!), but after a while I stopped bothering with all this tagging. Not sure why, but it felt like "too much work"... It seems there's a subtle, but significant difference between tagging and the capability to put a file in more than one folder.

Open source people sometimes amaze me. You refuse to use any such program (even though, as I noted, there's a standard way for them to store their data in most cases), despite how much good it might do you.
Maybe I should also mention the second reason why I don't use albums and the likes: I don't have too many pictures on my computer (a few hundred or so, rarely updated), and I stopped collecting music a long time ago (last.fm anyone?), so there's not much to organize here. This is not too amazing an explanation, is it?

8
Greetings.

What would be the required syntax if one tries to find documents that contain certain strings?
As much as I knew
"word1 word2"
was suppose to that job whereas
word1 word2
is the equivalent of AND, do please correct me if I am wrong.
Just give me a second to check the Lucene documentation... ah, here it is: http://lucene.apache.org/java/2_4_0/queryparsersyntax.html
DocFetcher is based on Apache Lucene, and therefore supports all operators described on that page. As for the AND operator, yes, there is one. Example: "some string" AND "some other string"

As for the problems with the hierarchical file system, have you guys considered "albums" and similar features which are provided by decent picture managers and media players these days? This is basically a way to put files into multiple categories. I never used that sort of thing, though, because of the potential risk of vendor lock-in (meaning that all that categorization data is lost when I move to another program).

9
I agree with you when e-mails are involved but their respective attachments are completely different thing, in this case you do need a DtS software.
Now I understand :)

Creating and maintaining hierachies takes time, that'a a fact and probably the most important reason for using DtS. Because I don't want to spend time for that  the rest my answers follow:

a.Images - can be found in many places therefore I use DtS to find them all and then I view them as thumbnails...and thus the decision is easiest
b. Music - here you can, generally search by filename...or metadata/tags. Or, can be leftovers(.ac3 files) from video conversions(DVD->.avi) that, in time, can stack up heavily...
c. Videos - when you use several sources for getting them on your computer they can also get lost in various places, especially when you have more than 1 HDD. For now I have more than 60 movies on my computer...mpeg/avi/iso/vob, you name it.

I also do not think that the typical savvy DtS user is searching mainly for the above but rather for documents with a certain content, at least this is my case. My search ratio is 95%/5% for content/a,v,p.
You seem to be the kind of user who doesn't clean up his folders very often and who then uses full hard drive desktop search to keep that mess under control. Don't get me wrong though, I don't think there's anything wrong with doing it this way. (I'm the kind of user who's folders are highly organized and who only uses desktop search to access stuff where the hierarchical system doesn't help much, i.e. documents.)

I gave it a try for a folder with less than 500 indexable documents and I got 2 messages:
Needed 19 bytes to create the next chunk header, but only found 4 bytes, ignoring rest of data
### Skipped: Not enough memory left in the Java Virtual Machine.
The Java Virtual Machine in which DocFetcher is running has a memory cap, and your file was too big for that. The manual explains how to raise that cap. However, I admit that this error message should've been more helpful.

Also I didn't get what I was expecting from a Boolean search:

search:"word1 word2"
returned a diffent set(number) of documents compared to
search:word1 word2
but in preview in both cases I saw enlightened both search terms(???).
The first case is AND, the second one is OR. Well, the preview highlighting wasn't fully implemented... :-[ Thanks for pointing this out.

So, for now I wish you all the best but I stick to Autofocus

To each his own.  :Thmbsup:

10
Considering that you can assign tags (apart from other info) to several media formats and save them within the file, I don't think it does really make more sense. What's more, several apps used to view or manipulate media can parse that data and save it in a local database (only accessible by that app, though). Whether you bother to use those methods is another story.

Both methods are not mutually exclusive, and I use them without problems. Depending of the moment, it makes more sense to use one or another, but I don't think there's an optimal solution.
Considering that you can assign tags (apart from other info) to several media formats and save them within the file, I don't think it does really make more sense. What's more, several apps used to view or manipulate media can parse that data and save it in a local database (only accessible by that app, though). Whether you bother to use those methods is another story.

Both methods are not mutually exclusive, and I use them without problems. Depending of the moment, it makes more sense to use one or another, but I don't think there's an optimal solution.
Okay, good point. Thanks for your answer.

Pages: prev1 [2] 3 4next
Go to full version