Re: [CODE4LIB] seeking linked data-based user interface examples in libraries

[Sheila M. Morrissey]

Do you know if the relationship-viewer source code open source and available?
Thanks,
sheila

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Kevin 
Hawkins
Sent: Tuesday, February 10, 2015 11:27 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] seeking linked data-based user interface examples in 
libraries

Here's one that I heard about at a presentation at ALA Midwinter:

http://civilwaronthewesternborder.org/content/relationship-viewer

People also like to cite this one, though it's not, strictly speaking, based in 
a library:

https://linkedjazz.org/

--Kevin

On 2/10/15 12:39 PM, Adam L. Chandler wrote:
> Hi,
>
>
> I am working on a presentation about linked data and I need some help. My 
> talk is about examples of linked data-based user interfaces in libraries, 
> wireframes, demos, or working systems. I am having difficulty finding them. 
> Please send me your examples.
>
>
> Thanks,
>
> Adam Chandler
>

[CODE4LIB] Version 2.1.0 of JHOVE2 format characerization tool is released

[Sheila M. Morrissey]

*** Cross posted ***




The JHOVE2 development community is pleased to announce the release of Version 
2.1.0 of the open-source JHOVE2 format characterization tool.

Version 2.1.0 of JHOVE2 includes 3 new format modules, 1 new identifier module, 
1 new displayer module, and several bug fixes and enhancements from the Issues 
page on the JHOVE2 wiki.

The new format modules included in this release are for the ARC, WARC, and GZIP 
formats.

The new Identifier module uses the UNIX "file" utility, giving JHOVE2 users the 
choice of employing either DROID or file for identification of file formats.

The new XSLDisplayer module (which extends XMLDisplayer) can do XSLT 
transformations on the XML output before displaying it.

This release also reflects a new milestone in the JHOVE2 development community. 
 The new format and identifier modules are the contribution of developers from 
institutions (Bibliothéque Nationale de France and NETARKIVET.DK) beyond the 
original project participants (California Digital Library, Portico, and 
Stanford University Libraries).

Please see the release notes at  https://bitbucket.org/jhove2/main/downloads 
for detailed information about the release and for information about 
configuring JHOVE2 to use the new identifier module.  For information about 
issues resolved in this release, known bugs, open issues, and enhancement 
requests, please refer to

[cid:image001.png@01CE23F7.787F0E50]   JHOVE2 Issues page

https://bitbucket.org/jhove2/main/issues?sort=version

For detailed installation and configuration instructions please refer to:

[cid:image001.png@01CE23F7.787F0E50]   JHOVE2 User's Guide
http://bitbucket.org/jhove2/main/wiki/documents/JHOVE2-Users-Guide_20110222.pdf.


For detailed guidance on developing additional format modules please refer to:

[cid:image001.png@01CE23F7.787F0E50]   JHOVE2 Architectural Overview
http://bitbucket.org/jhove2/main/wiki/documents/JHOVE2-Architecture-v2-0-0.pdf
[cid:image001.png@01CE23F7.787F0E50]   JHOVE2 Programmer's Guide
http://bitbucket.org/jhove2/main/wiki/documents/JHOVE2Programmer2-0-0.pdf

Questions concerning the use of JHOVE2 and module development should be 
addressed to
jhove2-techtal...@listserv.ucop.edu<mailto:jhove2-techtal...@listserv.ucop.edu>.

Specific errors or suggestions may be reported to the JHOVE2 issue tracker at 
https://bitbucket.org/jhove2/main/issues?sort=id.

The JHOVE2 development community welcomes all interested members of the 
preservation community to contribute to improving and extending the JHOVE2 tool.

Sincerely,
Sheila M. Morrissey

On behalf of the JHOVE2 development community:
http://www.jhove2.org<http://www.jhove2.org/>

BIBLIOTHÈQUE NATIONALE DE FRANCE
Laurent Bihanic

CALIFORNIA DIGITAL LIBRARY
Stephen Abrams,
Patricia Cruse
John Kunze
Marisa Strong
Perry Willett

NETARKIVET.DK
Nicholas Clarke

PORTICO
John Meyer
Sheila Morrissey

STANFORD UNIVERSITY
Richard Anderson
Tom Cramer
Hannah Frost




Sheila M. Morrissey
Senior Research Developer
ITHAKA
100 Campus Drive
Suite 100
Princeton NJ 08540
609-986-2221
sheila.morris...@ithaka.org<mailto:sheila.morris...@ithaka.org>

ITHAKA (www.ithaka.org<http://www.ithaka.org/>) is a not-for-profit 
organization that helps the academic community use digital technologies to 
preserve the scholarly record and to advance research and teaching in 
sustainable ways.  We provide innovative services that benefit higher 
education, including Ithaka S+R, JSTOR, and Portico.

<>

Re: [CODE4LIB] Version 2.1.0 of JHOVE2 format characerization tool is released

[Sheila M. Morrissey]

Gary -- thanks so much -- as the old saying has it -- praise from Sir Hugo is 
praise indeed!
Sheila

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Gary 
McGath
Sent: Monday, March 18, 2013 4:48 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Version 2.1.0 of JHOVE2 format characerization tool is 
released

Congratulations to the JHOVE2 development team!

On 3/18/13 4:41 PM, Sheila M. Morrissey wrote:
> *** Cross posted ***
> 
> 
> 
> 
> The JHOVE2 development community is pleased to announce the release of 
> Version 2.1.0 of the open-source JHOVE2 format characterization tool.
> 
> Version 2.1.0 of JHOVE2 includes 3 new format modules, 1 new identifier 
> module, 1 new displayer module, and several bug fixes and enhancements from 
> the Issues page on the JHOVE2 wiki.
> 
> The new format modules included in this release are for the ARC, WARC, and 
> GZIP formats.
> 
> The new Identifier module uses the UNIX "file" utility, giving JHOVE2 users 
> the choice of employing either DROID or file for identification of file 
> formats.
> 
> The new XSLDisplayer module (which extends XMLDisplayer) can do XSLT 
> transformations on the XML output before displaying it.
> 
> This release also reflects a new milestone in the JHOVE2 development 
> community.  The new format and identifier modules are the contribution of 
> developers from institutions (Bibliothéque Nationale de France and 
> NETARKIVET.DK) beyond the original project participants (California Digital 
> Library, Portico, and Stanford University Libraries).
> 
> Please see the release notes at  
> https://bitbucket.org/jhove2/main/downloads for detailed information 
> about the release and for information about configuring JHOVE2 to use 
> the new identifier module.  For information about issues resolved in 
> this release, known bugs, open issues, and enhancement requests, 
> please refer to
> 
> [cid:image001.png@01CE23F7.787F0E50]   JHOVE2 Issues page
> 
> https://bitbucket.org/jhove2/main/issues?sort=version
> 
> For detailed installation and configuration instructions please refer to:
> 
> [cid:image001.png@01CE23F7.787F0E50]   JHOVE2 User's Guide
> http://bitbucket.org/jhove2/main/wiki/documents/JHOVE2-Users-Guide_20110222.pdf.
> 
> 
> For detailed guidance on developing additional format modules please refer to:
> 
> [cid:image001.png@01CE23F7.787F0E50]   JHOVE2 Architectural Overview
> http://bitbucket.org/jhove2/main/wiki/documents/JHOVE2-Architecture-v2-0-0.pdf
> [cid:image001.png@01CE23F7.787F0E50]   JHOVE2 Programmer's Guide
> http://bitbucket.org/jhove2/main/wiki/documents/JHOVE2Programmer2-0-0.
> pdf
> 
> Questions concerning the use of JHOVE2 and module development should 
> be addressed to 
> jhove2-techtal...@listserv.ucop.edu<mailto:jhove2-techtal...@listserv.ucop.edu>.
> 
> Specific errors or suggestions may be reported to the JHOVE2 issue tracker at 
> https://bitbucket.org/jhove2/main/issues?sort=id.
> 
> The JHOVE2 development community welcomes all interested members of the 
> preservation community to contribute to improving and extending the JHOVE2 
> tool.
> 



--
Gary McGath, Professional Software Developer http://www.garymcgath.com

Re: [CODE4LIB] rdf serialization

[Sheila M. Morrissey]

Ed -- thanks for the link -- you and Dorothy have written a tremendously clear 
and useful piece
Sheila

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Ed 
Summers
Sent: Tuesday, November 05, 2013 9:45 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] rdf serialization

On Sun, Nov 3, 2013 at 3:45 PM, Eric Lease Morgan  wrote:
> This is hard. The Semantic Web (and RDF) attempt at codifying knowledge using 
> a strict syntax, specifically a strict syntax of triples. It is very 
> difficult for humans to articulate knowledge, let alone codifying it. How 
> realistic is the idea of the Semantic Web? I wonder this not because I don't 
> think the technology can handle the problem. I say this because I think 
> people can't (or have great difficulty) succinctly articulating knowledge. Or 
> maybe knowledge does not fit into triples?

I think you're right Eric. I don't think knowledge can be encoded completely in 
triples, any more than it can be encoded completely in finding aids or books.

One thing that I (naively) wasn't fully aware of when I started dabbling the 
Semantic Web and Linked Data is how much the technology is entangled with 
debates about the philosophy of language. These debates play out in a variety 
of ways, but most notably in disagreements about the nature of a resource 
(httpRange-14) in Web Architecture. Shameless plug: Dorothea Salo and I tried 
to write about how some of this impacts the domain of the library/archive [1].

One of the strengths of RDF is its notion of a data model that is behind the 
various serializations (xml, ntriples, json, n3, turtle, etc). I'm with Ross 
though: I find it much to read rdf as turtle or json-ld than it is rdf/xml.

//Ed

[1] http://arxiv.org/abs/1302.4591

Re: [CODE4LIB] Welcome to Roy4Lib

[Sheila M. Morrissey]

Sent from my iPhone

On Feb 25, 2014, at 5:47, "Caplan, Priscilla"  wrote:

> You would have to ask the pig about that.
> 
> p
> 
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Riley 
> Childs
> Sent: Tuesday, February 25, 2014 6:38 AM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Welcome to Roy4Lib
> 
> But bacons not meat,I consider it a soul food :D
> 
> Riley Childs
> Student
> Asst. Head of IT Services
> Charlotte United Christian Academy
> (704) 497-2086
> RileyChilds.net
> Sent from my Windows Phone, please excuse mistakes 
> 
> From: Barnes, Hugh
> Sent: ‎2/‎24/‎2014 10:51 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Welcome to Roy4Lib
> 
> And vegetarians, and Mormons, and folks who never met Roy :)
> 
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Riley 
> Childs
> Sent: Tuesday, 25 February 2014 4:28 p.m.
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Welcome to Roy4Lib
> 
> Just a reminder there are minors on this listserv ;P
> 
> Riley Childs
> Student
> Asst. Head of IT Services
> Charlotte United Christian Academy
> (704) 497-2086
> RileyChilds.net
> Sent from my Windows Phone, please excuse mistakes 
> 
> From: Wilhelmina Randtke
> Sent: ‎2/‎24/‎2014 10:24 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Welcome to Roy4Lib
> 
> My neighbor made this bacon vodka, and it was amazing 
> http://www.instructables.com/id/Bacon-Infused-Vodka/
> 
> -Wilhelmina Randtke
> 
> On Mon, Feb 24, 2014 at 10:36 AM, Michael J. Giarlo 
>  wrote:
>> Bacon being cooked in a liquor store?  Wow, California is awesome.
>> 
>> 
>> On Mon, Feb 24, 2014 at 8:31 AM, Roy Tennant  wrote:
>> 
>>> That would make sense, but I think in this particular instance I was 
>>> watching bacon being cooked.
>>> Roy
>>> 
>>> 
>>> On Mon, Feb 24, 2014 at 8:26 AM, Michael J. Giarlo < 
>>> leftw...@alumni.rutgers.edu> wrote:
>>> 
 Clearly taken in the liquor store.
 
 
 On Mon, Feb 24, 2014 at 7:08 AM, Cindi Trainor Blyberg
 wrote:
 
> Well, I do like the photo that Roy uses everywhere, but I have to 
> say I like this one better:
> 
> http://www.flickr.com/photos/23341397@N00/3769032245
> 
> 
> On Mon, Feb 24, 2014 at 9:05 AM, Roy  wrote:
> 
>> Hmm. Call it roys4lib.org and put pictures of all the list's 
>> Roys on there...
>> Mr. Tennant's picture would have to be first, of course, and be 
>> the biggest.
>> 
>> 
>> 
>> On 2/21/2014 6:51 PM, Rosalyn Metz wrote:
>> 
>>> so tempted to buy roy4lib.org and put up a glass of scotch there.
>>> 
>>> 
>>> On Fri, Feb 21, 2014 at 3:46 PM, Edward M Corrado <
 ecorr...@ecorrado.us
 wrote:
>>> 
>>> Roy4lib has consumed to much Scotch - after all, it is Friday.
 
 --
 Edward M. Corrado
 
 On Feb 21, 2014, at 18:13, Roy Tennant 
>>> wrote:
 
 roy4lib.org is ALWAYS down. I mean, it just makes too much 
 sense
 for
> it
> 
 to
 
> be in any other state.
> Roy
> 
> 
> On Fri, Feb 21, 2014 at 2:31 PM, Rosalyn Metz <
 rosalynm...@gmail.com>
> 
 wrote:
 
> it appears that roy4lib.org is also down
>> 
>> 
>> On Fri, Feb 21, 2014 at 1:59 PM, Frumkin, Jeremy < 
>> frumk...@u.library.arizona.edu> wrote:
>> 
>> Welcome to the Roy4Lib discussion list. This list is 
>> intended to
>>> facilitate discussion on Roy Tennant's new world library 
>>> order,
 the
>>> 
>> role
 
> of bacon (including kosher and vegetarian based varieties) 
> in this
>>> context, and the long, long, long, long, long drawn out 
>>> death of
> MARC.
>>> 
>>> If you believe you have subscribed to this list in error, 
>>> please
> email
>>> 
>> the
>> 
>>> admin at r...@roy4lib.org.
>>> 
>>> 
>>> --
>>> --
>>> 
>>> Jeremy Frumkin
>>> Assistant Dean / Chief Technology Strategist University of 
>>> Arizona Libraries
>>> 
>>> +1 520.626.7296
>>> frumk...@u.library.arizona.edu
>>> --
>>> -- "Any intelligent fool can make things bigger and more 
>>> complex...
 It
>>> 
>> takes
 
> a touch of genius - and a lot of courage to move in the 
> opposite
>

Re: [CODE4LIB] "Citation Analysis" - like projects for print resources

[Sheila M. Morrissey]

Matt --
Do you mean something like this?
http://chronicle.com/article/Maps-of-Citations-Uncover-New/128938/?sid=at&utm_source=at&utm_medium=en

Sheila

Sheila M. Morrissey
Senior Research Developer
ITHAKA
100 Campus Drive
Suite 100
Princeton NJ 08540
609-986-2221   
sheila.morris...@ithaka.org
 
ITHAKA (www.ithaka.org) is a not-for-profit organization that helps the 
academic community use digital technologies to preserve the scholarly record 
and to advance research and teaching in sustainable ways.  We provide 
innovative services that benefit higher education, including Ithaka S+R, JSTOR, 
and Portico.



-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Matt 
Amory
Sent: Thursday, November 17, 2011 9:41 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] "Citation Analysis" - like projects for print resources

Is anyone involved with, or does anyone know of any project to extract and
aggregate bibliography data from individual works to produce some kind of
"most-cited" authors list across a collection?  Local/Network/Digital/OCLC
or historic?

Sorry to be vague, but I'm trying to get my head around whether this is a
tired old idea or worth pursuing...


-- 
Matt Amory
(917) 771-4157
matt.am...@gmail.com
<http://www.linkedin.com/pub/matt-amory/8/515/239>

Re: [CODE4LIB] MarcXML and char encodings

[Sheila M. Morrissey]

Re: But do others agree that there is in fact no legal way to have Marc8 in 
MarcXML?

No -- it is perfectly legal - -but you MUST declare the encoding to BE Marc8 in 
the XML prolog, and you will want to be aware that XML processors are only 
REQUIRED to process UTF-8 and UTF-16 -- in practice many (including JAVA-based 
one) can handle other encodings -- but you will have to make sure whatever XML 
processor you use, in whatever language it is written, has a handy-dandy MARC8 
coder/decoder ring

Sheila

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of 
Jonathan Rochkind
Sent: Tuesday, April 17, 2012 2:46 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] MarcXML and char encodings

Thanks, this is helpful feedback at least.

I think it's completely irrelevant, when determining what is legal under 
standards, to talk about what certain Java tools happen to do though, I 
don't care too much what some tool you happen to use does.

In this case, I'm _writing_ the tools. I want to make them do 'the right 
thing', with some mix of what's actually official legally correct and 
what's practically useful.  What your Java tools do is more or less 
irrelevant to me. I certainly _could_ make my tool respect the Marc 
leader encoded in MarcXML over the XML decleration if I wanted to. I 
could even make it assume the data is Marc8 in XML, even though there's 
no XML charset type for it, if the leader says it's Marc8.

But do others agree that there is in fact no legal way to have Marc8 in 
MarcXML?

Do others agree that you can use non-UTF8 encodings in MarcXML, so long 
as they are legal XML?

I won't even ask someone to cite standards documents, because it's 
pretty clear that LC forgot to consider this when establishing MarcXML.  
(And I have no faith that one could get LC to make a call on this and 
publish it any time this century).

Has anyone seen any Marc8-encoded MarcXML in the wild? Is it common? How 
is it represented with regard to the XML leader and the Marc header?

Has anyone seen any MarcXML with char encodings that are neither Marc8 
nor UTF8 in the wild? Are they common? How are they represented with 
regard to XML leader and Marc header?

On 4/17/2012 2:32 PM, LeVan,Ralph wrote:
>> If I want to have a MarcXML document encoded in Marc8 -- what should
> it
>> look like?  What should be in the XML decleration? What should be in
> the
>> MARC header embedded in the XML?  Or is it not in fact legal at all?
> I'm going out on a limb here, but I don't think it is legal.  There is
> no formal encoding that corresponds to MARC-8, so there's no way to tell
> XML tools how to interpret the bytes.
>
>
>> If I want to have a MarcXML document encoded in UTF8, what should it
>> look like? What should be in the XML decleration? What should be in
> the
>> MARC header embedded in the XML?
> 
>
> I suppose you'll want to set the leader to UTF-8 as well, but it doesn't
> really matter to any XML tools.
>
>
>> If I want to have a MarcXML document with a char encoding that is
>> _neither_ Marc8 nor UTF8, but something else generally legal for XML

Re: [CODE4LIB] MarcXML and char encodings

[Sheila M. Morrissey]

In XML standard:

It is RECOMMENDED that character encodings registered (as charsets) 
with the Internet Assigned Numbers Authority [IANA-CHARSETS], other than those 
just listed, be referred to usingtheir registered names; other encodings 
SHOULD use names starting with an "x-" prefix. XML processors SHOULD match 
character encoding names in a case-insensitive way and SHOULDeither 
interpret an IANA-registered name as the encoding registered at IANA for that 
name or treat it as unknown (processors are, of course, not required to support 
all IANA-  registered encodings).


As I suggested -- since MARC8 isn't (so far as I know) registered -- you won't 
get far with most standard tools, in whatever language -- you'll have to extend 
them to first recognize the encoding name, and second, decode the content.

smm

-Original Message-
From: Jonathan Rochkind [mailto:rochk...@jhu.edu] 
Sent: Tuesday, April 17, 2012 4:19 PM
To: Code for Libraries
Cc: Sheila M. Morrissey
Subject: Re: [CODE4LIB] MarcXML and char encodings



On 4/17/2012 3:01 PM, Sheila M. Morrissey wrote:
> No -- it is perfectly legal - -but you MUST declare the encoding to BE Marc8 
> in the XML prolog,

Wait, how canyou declare a Marc8 encoding in an XML 
decleration/prolog/whatever it's called?

The things that appear there need to be from a specific list, and I 
didn't think Marc8 was on that list?

Can you give me an example?  And, if you happen to have it, link to XML 
standard that says this is legal?

Re: [CODE4LIB] MarcXML and char encodings

[Sheila M. Morrissey]

I think this is a case of being in violent agreement -- see some earlier 
replies in this thread -- 
Pragmatically, if you are going to hew to marc-8 encoding transported in XML -- 
you are losing the usefulness of standard tools for xml --
smm

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of 
LeVan,Ralph
Sent: Tuesday, April 17, 2012 4:21 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] MarcXML and char encodings

>> No -- it is perfectly legal - -but you MUST declare the encoding to
BE Marc8 in the XML prolog,

> Wait, how canyou declare a Marc8 encoding in an XML 
> decleration/prolog/whatever it's called?

Nope, you can't do that.  There is no approved name for the MARC-8
encoding.  As Andy said, the closest you could get would be to make up
an experimental name, like x-marc-8, but no tool in the world would
recognize that.

Ralph

Re: [CODE4LIB] TIFF Metadata to XML?

[Sheila M. Morrissey]

JHOVE2 (www.jhove2.org) will work as well.
Sheila


From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Jon Stroop 
[jstr...@princeton.edu]
Sent: Monday, July 18, 2011 9:23 AM
To: CODE4LIB@LISTSERV.ND.EDU
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

Re: [CODE4LIB] TIFF Metadata to XML?

[Sheila M. Morrissey]

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 [jstr...@princeton.edu]
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 [CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Jon Stroop 
> [jstr...@princeton.edu]
> Sent: Monday, July 18, 2011 9:23 AM
> To: CODE4LIB@LISTSERV.ND.EDU
> 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 [CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Jon Stroop 
[jstr...@princeton.edu]
Sent: Monday, July 18, 2011 9:23 AM
To: CODE4LIB@LISTSERV.ND.EDU
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