.cwk how to find all documents that are created by Claris Works and Apple Works

I started a Raw Query search for the shorter string "BOBO". No results after 45 minutes or so. Restricted the search to the folder where my documents are saved, Still no results after 30 minutes (timed). Aborted.

Tried again, using the full search string "kMDItemFSCreatorCode=BOBO"

Results were almost instant. Several types, including about 1700 Documents.

Must learn to trust the advice given. 😉

Regards,

Barry

Binaries in Snow Leopard reveal kMDItemFSCreatorCode in only two pieces of active code:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata .framework/Versions/A/Metadata

/System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightI ndex

But kMDItemFSCreatorCode itself appears to have been deprecated as a metadata attribute. (Or perhaps it was never fully implemented. I don't find it listed in Apple's metadata reference guides going back to Tiger.) Scanning through the various .lproj files in /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Resources/ does not reveal any mappings in the schema.strings files where I would expect to find kMDItemFSCreatorCode listed for a metadata attribute that Apple continues to support. Nonetheless, vestiges of the code that makes the Raw Query/kMDItemFSCreatorCode search work still live in Snow Leopard binaries.

Presumably Apple engineers believe that kMDItemCreator will serve adequately into the future. Perhaps, but first there's a lot of clean-up work to do on the past before making the transition.

@fruhulda--I switched to Swedish on a clone drive and the Raw Query worked for me (no translation needed). Perhaps the difference is that I originally installed the OS in English and therefore can access kMDItemFSCreatorCode in a Raw Query in any language. But honestly, I don't really know.

@ChangeAgent--Glad to hear it's working.

Message was edited by: mns579-- The forum message system introduced a few blank spaces into the paths above. I think you can see where they are. I don't know how to remove the spaces.

Hi!

I tried it again and now it worked i "swedish". I must have done something more and faulty which I can't remember. Anyway thanks for this great tips!!!!

I don't think you can narrow down the search anymore but you can after you have found your files use Yvans script "which_kind_of_AWdoc.zip". You'll find it here https://public.me.com/koenigyvan in the folder scripts for appleWorks.

You could Raw Query search on the type code used for files created by the AW/CW Drawing subprogram:

kMDItemFSTypeCode=CWGR

Metadata queries can also be chained for greater precision. Thus you could combine the two Raw Query search strings to specify files with creator code BOBO and type CWGR:

kMDItemFSCreatorCode=BOBO && kMDItemFSTypeCode=CWGR

But other than slowing down the search, there's nothing to gain from the additional precision.

Question for Lion users: do these metadata attributes continue to exist for files migrated from older operating systems? In other words, when performing a command-line mdls on, say, an AW/CW Drawing file, is there still an entry for kMDItemFSTypeCode or kMDItemFSCreatorCode--or have the old type and creator codes disappeared with the advent of Lion?

Did you miss my post above? It does tell you how.

My point about refining the creator code BOBO results by further restricting to type CWGR is that all CWGR files are BOBO files--that is, the CWGR files are a nested set inside the BOBO set. Spotlight will move more slowly with two search terms than it does with one, and, for your purposes, only one is needed. (Offering more information than you probably need. . . .)

You can use these Raw Query searches for each of the AW/CW subtypes:

(Drawings) kMDItemFSTypeCode=CWGR

(Paintings) kMDItemFSTypeCode=CWPT

(Spreadsheets) kMDItemFSTypeCode=CWSS

(Presentations) kMDItemFSTypeCode=CWPR

(Databases) kMDItemFSTypeCode=CWDB

(Wordprocessing) kMDItemFSTypeCode=CWWP

Why did you try that script??