MetaMaze Mac OS

broken image


Mess of Metadata


  • A crypto wallet & gateway to blockchain apps. Install MetaMask for your browser.
  • Once the Mac OS does kick-off the extraction of metadata from a file, it does so through a Spotlight Importer. Spotlight Importers are plug-ins for the Mac OS that a developer provides specifically for helping files created by their applications to be searchable within Spotlight.

Metamaze Mac Os Download

© May 2019 Anthony Lawrence

The metadata of a file is a corpus of data originating from the tagging operations of the OS that ensue when you save files to local folder on your Mac. It includes the background information about the file which provide sorting functions with cues to trace out the file's location.

There was a long series of comments at the article about mdfind that got very confused talking about OS X metadata. I thought I'd try to straighten some of that out in a separate post - though honestly I'm still easily confused myself!

First, what metadata are we talking about? For an old Unix hand, the metadata is information stored in the inode: file size, permissions, pointers to datablocks, link counts.. that's traditional metadata.

However, there's more metadata today - not just in Unix systems, but especially in Mac OS X. There are extended permissions, acl's, xattributes, Spotlight related metadata.. it's very hard to ferret all this out of Google because similar terms are used for dissimilar features.

Macs had 'resource forks' early on. OS X still has resource forks. but apparently Apple would like to move away from those. That's probably why things get so darn confusing: search for information on metadata and OS X and you'll find lots of pointers to things that talk about resource forks, but usually that's deprecated and doesn't usually apply to OS X.

Let's take Spotlight metadata first. These are specific keys that Spotlight indexes. For example, you can do things like this:

How does Spotlight get the info to index? It asks an Spotlight Importer. This BASICS OF SPOTLIGHT page explains:

Once the Mac OS does kick-off the extraction of metadata from a file, it does so through a Spotlight Importer. Spotlight Importers are plug-ins for the Mac OS that a developer provides specifically for helping files created by their applications to be searchable within Spotlight. Spotlight crawls through its list of changed files, handing each one to the appropriate importer. The importers then read the files, compile a list of metadata, and then hand the metadata back to Spotlight. At this point, the changed file is available for searching within Spotlight.

OK, great, but where does the metadata that the importer supplies come from? Apparently, that's up to the developer. Apple's Extracting Metadata from Documents says:

Avoid the use of external files to store metadata content. All critical metadata should be in the same file as the data. The system store of metadata should be considered volatile.

I want to quibble a little: if it's stored in the data file, it's really not metadata, is it? But never mind. Some apps do it that way. For example, ID3 tags. But other apps do not. For example. In my ~/Library/Caches/Metadata I found some interesting stuff. *Some* apps store Spotlight metadata there. I found:

Metamaze Mac Os Catalina

If I look in Billings, I find this:

But obviously not all apps store their Spotlight related metadata there. Entourage does, as seen in this HOW DOES ENTOURAGE WORK WITH SPOTLIGHT? bit:

When you enable Spotlight indexing within Entourage, a 'cache' file is created for each item within your Entourage database. If you have 100,000 e-mail messages in your Entourage database, 100,000 cache files will be created. If you want to see the cache files, you can find them within your Library/Caches/Metadata/Microsoft folder.
Each cache file contains all the metadata that will be needed for indexing by Spotlight. All changes within Entourage are reflected to the cache files. Create a new item and a new cache file will be created. Updated an item and its cache file will update. Delete an item and its cache file will be deleted. With all these changes, Spotlight receives file change notifications and eventually will ask the modified cache files to go through the import process using the Entourage Spotlight Importer.

But there's no iTunes folder there..

There are also defaults. If I create a text file with 'date > file', an 'mdls' will show Spotlight keys:

Obviously the 'date' command didn't create those. Spotlight won't even index that file (no extension), but it has some default keys just the same! See Spotlight, mdfind (Mac OS X Tiger searching) for more on that.

You can add metadata yourself and can modify one item of Spotlight's domain.

The only Spotlight related data you can modify is kMDItemFinderComment. You do that with GetInfo and after adding it, xattr shows this:

Note that this gives us the clue as to where the data was stored, but I don't find a file with that 'com.apple.metadata' name. I do find:

But those aren't related.

So what do we know? Well, we know it's up to the application responsible for a file to provide importer code. It's up to the same app to decide where to store metadata. Obviously, that implies that for some data that would be the across all files of this type, there's no need to store it anywhere - the importer could generate the response when Spotlight asks.

That's as far as I've gone.. maybe someone else can add more.


Got something to add? Send me email.

MetaMaze Mac OS

(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version
-> -> Mess of Metadata


Inexpensive and informative Apple related e-books:
Take Control of Numbers
Digital Sharing Crash Course
Take Control of IOS 11
Take control of Apple TV, Second Edition
Sierra: A Take Control Crash Course
v0.39.1 / Operations Guide / Running the Metabase Mac App

The Mac Application is the easiest way to setup Metabase locally on macOS for personal use.Note that currently the Mac Application is not setup for shared use, so some Metabase features which involve the rest of your team won't be possible.

Installing the Mac Application

Start off by downloading the Metabase Mac Application if you haven't done so already.Once the download is complete go ahead and double click the file to open it up. You should see something like this:

Next simply click and drag the Metabase.app icon over to the Applications folder icon on the left. That will install Metabase into your main Applications folder.

Launching Metabase

To launch Metabase open the Mac Finder application and click on Applications on the left. Then scroll down your applications list until you see Metabase.app and double click it.

The Metabase application should now have opened and you should see the loading screen in the application window with a spinner going.

Give the application a moment to finish initializing and then you should see the screen change to the Metabase Welcome page. That's it! Installation Complete.

Now that you've installed Metabase, it's time to set it up and connect it to your database.

The application database

The application database lives on your filesystem, at~/Library/Application Support/Metabase/metabase.db.h2.db

If you want to delete it, back it up, or replace it with an old backup, shut down the application and then delete, copy or replace the file.

Note: depending on when you first started using Metabase the file may be called~/Library/Application Support/Metabase/metabase.db.mv.db





broken image