Comments on: The Problem with Data that is Meta http://tleaves.com/2004/07/21/the-problem-with-data-that-is-meta/ Creativity x Technology Sat, 17 Mar 2012 05:09:58 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jymmm http://tleaves.com/2004/07/21/the-problem-with-data-that-is-meta/comment-page-1/#comment-483 Jymmm Sat, 09 Oct 2004 06:00:55 +0000 http://tleaves.com/?p=148#comment-483 Hey Psu, Even after finding the update, I'm personally still pissed. Adobe is force-feeding their standard down everyone's throat. "The nice thing about standards is there are so many" NOT!!!!!!!!! There are a million+ digital cameras and printers that support EXIF meta-data and then Adobe introduces a new format that doesn't work along side of what is existing to give folks a choice or even an opportunity to transition to, but just kicks it to the curb like yesterday's garbage. Sure, all the big boys are adopting XMP, but they completely left out the lil folks that create/use utilities to work as they want to. I have a Nikon D70 DSLR and even the latest version of Nikon's software doesn't display all the EXIF data. I have to rely upon third party utilities to grab all of it. Not even Photoshop CS can see/view all the available data (even with the new RAW plugin). I'm in the process of writing a script to read/write IPTC, EXIF and XMP data, all at the same time. A very slow process btw (writing the script that is). Just too darn difficult to bulk edit (crop and watermark in/on) 250+ photos at a time with Adobe products. And I agree that the image browser in PS completely sucks. Paint Shop Pro has that feature down flat (I use both just to be productive). [end rant] To email: name + at symbol + email address Hey Psu,

Even after finding the update, I’m personally still pissed. Adobe is force-feeding their standard down everyone’s throat.

“The nice thing about standards is there are so many” NOT!!!!!!!!!

There are a million+ digital cameras and printers that support EXIF meta-data and then Adobe introduces a new format that doesn’t work along side of what is existing to give folks a choice or even an opportunity to transition to, but just kicks it to the curb like yesterday’s garbage.

Sure, all the big boys are adopting XMP, but they completely left out the lil folks that create/use utilities to work as they want to.

I have a Nikon D70 DSLR and even the latest version of Nikon’s software doesn’t display all the EXIF data. I have to rely upon third party utilities to grab all of it.

Not even Photoshop CS can see/view all the available data (even with the new RAW plugin).

I’m in the process of writing a script to read/write IPTC, EXIF and XMP data, all at the same time. A very slow process btw (writing the script that is).

Just too darn difficult to bulk edit (crop and watermark in/on) 250+ photos at a time with Adobe products. And I agree that the image browser in PS completely sucks. Paint Shop Pro has that feature down flat (I use both just to be productive).

[end rant]

To email: name + at symbol + email address

]]>
By: Josh http://tleaves.com/2004/07/21/the-problem-with-data-that-is-meta/comment-page-1/#comment-482 Josh Mon, 02 Aug 2004 02:44:55 +0000 http://tleaves.com/?p=148#comment-482 I couldn't have said it better myself! As someone who spends all day cooped up with Information Science grad students*, I can tell you that, yes, metadata does give lots of idealists wet dreams. As someone with a background in IM protocols**, metadata strikes me the same way as it does you. I foresee a future full of weirdo kludges to bridge between one person's idea of a document and someone else's, with plenty of third-party "extraction" tools. That is, it'll be a lot like today. The thing that is positive about metadata is that at least now people are thinking about it. I used to do accounting system migrations (read: the world's dullest and least sexy reverse engineering gig), where I had to spend days of my life writing perl to handle all the nuances of text files containing COBOL-generated, bizarro-formatted accounting reports. Yeah, we would just replace their serial printer with a serial port on a linux box, and suck up all the data as it got printed. It was easier than divining the nuances of a dozen or more binary files. At least with "metadata," people are thinking that encapsulation is needed, instead of just spewing data onto screens or drives. Rigidly structured data is a lot easier to work with than "amorphous" data. The problems of missing/incongruous information are still there, though. As someone who's made parts of a career out of this sort of thing, I like the idea. It means that my jobs get easier, but I'll probably still be able to bill the same =) * I work at a little place called ibiblio, nee MetaLab, nee SunSite... we have a few RAs that do a lot of the site development. I'm just an admin there: it's a nice quiet student job while I finally knuckle down and get a degree. ** I worked on reverse engineering AOL's OSCAR protocol, better known as AIM. I couldn’t have said it better myself!

As someone who spends all day cooped up with Information Science grad students*, I can tell you that, yes, metadata does give lots of idealists wet dreams. As someone with a background in IM protocols**, metadata strikes me the same way as it does you. I foresee a future full of weirdo kludges to bridge between one person’s idea of a document and someone else’s, with plenty of third-party “extraction” tools. That is, it’ll be a lot like today.

The thing that is positive about metadata is that at least now people are thinking about it. I used to do accounting system migrations (read: the world’s dullest and least sexy reverse engineering gig), where I had to spend days of my life writing perl to handle all the nuances of text files containing COBOL-generated, bizarro-formatted accounting reports. Yeah, we would just replace their serial printer with a serial port on a linux box, and suck up all the data as it got printed. It was easier than divining the nuances of a dozen or more binary files. At least with “metadata,” people are thinking that encapsulation is needed, instead of just spewing data onto screens or drives. Rigidly structured data is a lot easier to work with than “amorphous” data. The problems of missing/incongruous information are still there, though.

As someone who’s made parts of a career out of this sort of thing, I like the idea. It means that my jobs get easier, but I’ll probably still be able to bill the same =)

* I work at a little place called ibiblio, nee MetaLab, nee SunSite… we have a few RAs that do a lot of the site development. I’m just an admin there: it’s a nice quiet student job while I finally knuckle down and get a degree.

** I worked on reverse engineering AOL’s OSCAR protocol, better known as AIM.

]]>
By: psu http://tleaves.com/2004/07/21/the-problem-with-data-that-is-meta/comment-page-1/#comment-481 psu Thu, 22 Jul 2004 01:31:20 +0000 http://tleaves.com/?p=148#comment-481 8 hours after writing this in a fit of anger, I found that Adobe released a patch to their Camera RAW plugin that fixes this problem. So my workflow is in tact and I get to keep my beloved iView and use all the new Photoshop toys too. Thank goodness for good apps. 8 hours after writing this in a fit of anger, I found that Adobe released a patch to their Camera RAW plugin that fixes this problem. So my workflow is in tact and I get to keep my beloved iView and use all the new Photoshop toys too.

Thank goodness for good apps.

]]>
By: megan dietz http://tleaves.com/2004/07/21/the-problem-with-data-that-is-meta/comment-page-1/#comment-480 megan dietz Wed, 21 Jul 2004 16:53:23 +0000 http://tleaves.com/?p=148#comment-480 hey pete remember me? found you thru rich engel's blog. hey pete remember me?
found you thru rich engel’s blog.

]]>