Hi Tony!
Picasa has useful support for a number of different types of jpg
"retro-tags", but you're right, some sorts of tag are flakier than
others, and some image-editing or image-processing applications (and
their software plugins) are also flakier than others.
I once bought a commercial bulk image-processing and bulk image-tagging
program, which, if you ran an image-optimisation script, destroyed
earlier bulk-tagging info created by the same program! The program
correctly read existing standard tags from the front of RIFF files,
incorrectly resaved them to the ends of the files, and then when it bulk
edited the image data it carefully preserved the file headers but
overwrote the image block and everything after it, destroying its own
saved metadata blocks at the same time. Sigh.
I think that sometimes, people who write image processing routines get
understandably enraptured with all the cool pretty visual stuff, and
forget about the more "boring" data-archival issues. But for museums,
data integrity (for things like where images came from, what they show,
when they were taken, and who owns the copyright) is kinda important.
But maybe that's something for a different discussion.
Eric
On 16/08/2011 22:24, Tony Crockford wrote:
> On 16 Aug 2011, at 22:05, Eric Baird wrote:
>> Some thoughts:
>>
> <snipped interesting stuff>
>> (15) Auto-embedding of tag and field data associated with images, directly into the image files themselves. I'm still mildly shocked at the number of picture vendors that don't bother embedding subject tags, titles or their copyright info into their images using the tag system.
>>
>> (16) Support for new and emergent tagging formats such as geolocator tags.
>>
>> ... and probably some other stuff.
>>
>
>
> Most of the first part of your spec was how we built our bespoke exhibition software, and it's working fine, powering several exhibitions for several years. (and the site it was originally piloted on (torbytes.com) is still plodding along.)
>
> Your point 15 is interesting and I have some insight into that to share - it seems that some image manipulation tools strip out all the embedded image data without warning, notably the file upload and resizing scripts in WordPress for example.
>
> I imagine the fragility of the embedded data, and the different standards (EXIF, IPTC, XMP etc) are the main obstacle here.
>
> ****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
> ****************************************************************
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|