Ah, the plot thickens. Nothing calls that metadataParser method. I can
delete the whole package and no compile errors appear. There's no
mention of metadata parsing in the package.html either, so there is no
documentation on setting it up. Which makes me think it is very unlikely
anyone is using it.
I also see the native lib is coming from the Native/ directory in the
project, which is only x86 macosx evidently.
The mimetype you mention is coming out of ERMimeTypeManager in utils.
It seems like it will be safe to delete this metadata parser package
after all.
So it's just down to rackspace cloud files now.
On 1/27/26 8:11 PM, Ramsey Gurley wrote:
Okay, digging a bit deeper, I see that in
ERMetadataParser.metadataParser(), it first tries the
ImageIOMetadataParser. This evidently relies on a native lib which
comes out of drewnoakes. So it would depend on if that lib exists on
your platform. I suspect that comes out of metadata-extractors only
dependency, xmpcore, which is a proprietary adobe lib which is not
updated since 2020. One week after the first ARM mac was announced, so
it seems doubtful that anyone is using the native lib today, at least
in development.
Second stop is the ImageMagick command line metadata parser. That
would depend on if you've installed image magick stuff and it's
configured correctly to be found by the app.
Then it falls back to the JAI parser which says is "java2d" in the
code, but it also seems to lean on drewnoakes again to do its thing.
So you're probably using it in some fashion and if metadata is
important to anyone, I guess we need to find a replacement for it.
That being the case, since we already have the interface, we could
just make a service locator and let people load metadata extractors
the same way slf4j lets you use the logger of your choice. That's
probably what I'll do with it.
On 1/27/26 6:12 AM, Paul Hoadley wrote:
Hi Ramsey,
On 26 Jan 2026, at 6:01 pm, Ramsey Gurley <[email protected]>
wrote:
Well, actually, let me ask that too. Is anyone actually using the
drewnoakes metadata parser? It appears there are several metadata
parser implementations, and this is just one of them.
We might be: we use ERS3Attachment, and database rows certainly end
up with a sensible value in the mimetype column. So we're relying on
whatever ERAttachment.framework is doing automatically under the
hood—is that drewnoakes?
--
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/