Hello, Jon --
Should have added -- thanks for the pointer to JHOVE/JHOVE2 --
There are still some modules in JHOVE for which there is not yet one in JHOVE2 (though coming to a Bitbucker repository near you soon!!) and vice versa-- but for TIFF -- folks might prefer using the later code.
Best,
Sehila
________________________________________
From: Jon Stroop [[log in to unmask]]
Sent: Monday, July 18, 2011 9:41 AM
To: Sheila M. Morrissey
Subject: Re: [CODE4LIB] TIFF Metadata to XML?
Oops! I wasn't trying to specify a version of JHOVE, I meant to add a
footnote with a link and forgot. For what it's worth, I was going to
link to JHOVE2 :-) .
Hope all is well with you,
Jon
On 07/18/2011 09:36 AM, Sheila M. Morrissey wrote:
> JHOVE2 (www.jhove2.org) will work as well.
> Sheila
>
> ________________________________________
> From: Code for Libraries [[log in to unmask]] On Behalf Of Jon Stroop [[log in to unmask]]
> Sent: Monday, July 18, 2011 9:23 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] TIFF Metadata to XML?
>
> Edward,
> JHOVE (1) should be able to do this, and I believe you can pass the
> included shell script a directory and have it extract data for
> everything it finds and can parse inside.
> -Jon
>
> On 07/18/2011 09:18 AM, Edward M. Corrado wrote:
>> Hello All,
>>
>> Before I re-invent the wheel or try many different programs, does
>> anyone have a suggestion on a good way to extract embedded Metadata
>> added by cameras and (more importantly) photo-editing programs such as
>> Photoshop from TIFF files and save it as as XML? I have> 60k photos
>> that have metadata including keywords, descriptions, creator, and
>> other fields embedded in them and I need to extract the metadata so I
>> can load them into our digital archive.
>>
>> Right now, after looking at a few tools and having done a number of
>> Google searches and haven't found anything that seems to do what I
>> want. As of now I am leaning towards extracting the metadata using
>> exiv2 and creating a script (shell, perl, whatever) to put the fields
>> I need into a pseudo-Dublin Core XML format. I say pseudo because I
>> have a few fields that are not Dublin Core. I am assuming there is a
>> better way. (Although part of me thinks it might be easier to do that
>> then exporting to XML and using XSLT to transform the file since I
>> might need to do a lot of cleanup of the data regardless.)
>>
>> Anyway, before I go any further, does anyone have any
>> thoughts/ideas/suggestions?
>>
>> Edward
________________________________________
From: Sheila M. Morrissey
Sent: Monday, July 18, 2011 9:36 AM
To: Code for Libraries
Subject: RE: [CODE4LIB] TIFF Metadata to XML?
JHOVE2 (www.jhove2.org) will work as well.
Sheila
________________________________________
From: Code for Libraries [[log in to unmask]] On Behalf Of Jon Stroop [[log in to unmask]]
Sent: Monday, July 18, 2011 9:23 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] TIFF Metadata to XML?
Edward,
JHOVE (1) should be able to do this, and I believe you can pass the
included shell script a directory and have it extract data for
everything it finds and can parse inside.
-Jon
On 07/18/2011 09:18 AM, Edward M. Corrado wrote:
> Hello All,
>
> Before I re-invent the wheel or try many different programs, does
> anyone have a suggestion on a good way to extract embedded Metadata
> added by cameras and (more importantly) photo-editing programs such as
> Photoshop from TIFF files and save it as as XML? I have> 60k photos
> that have metadata including keywords, descriptions, creator, and
> other fields embedded in them and I need to extract the metadata so I
> can load them into our digital archive.
>
> Right now, after looking at a few tools and having done a number of
> Google searches and haven't found anything that seems to do what I
> want. As of now I am leaning towards extracting the metadata using
> exiv2 and creating a script (shell, perl, whatever) to put the fields
> I need into a pseudo-Dublin Core XML format. I say pseudo because I
> have a few fields that are not Dublin Core. I am assuming there is a
> better way. (Although part of me thinks it might be easier to do that
> then exporting to XML and using XSLT to transform the file since I
> might need to do a lot of cleanup of the data regardless.)
>
> Anyway, before I go any further, does anyone have any
> thoughts/ideas/suggestions?
>
> Edward
|