LISTSERV mailing list manager LISTSERV 16.0

Help for METS Archives


METS Archives

METS Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

METS Home

METS Home

METS  March 2002

METS March 2002

Subject:

Re: Checksum

From:

Carl Fleischhauer <[log in to unmask]>

Reply-To:

Metadata Encoding and Transmission Standard <[log in to unmask]>

Date:

Fri, 15 Mar 2002 08:38:16 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (63 lines)

Thanks for the dialog, MacKenzie.  In our theorizing here at LC, we have
wished for a file integrity monitoring tool, and pictured a system that
checks and rechecks a file/object over time.  We seek reassurance about
the integrity of our objects over the long haul.

Now: how does that relate to METS?  Ummm.  If METS was the metadata for an
OAIS AIP, then there might be an argument that the "original" checksum (or
equivalent) is parked there, with the object.  The job of the monitoring
system would be to run comparisons and alert the owner when a change is
noticed.  In addition, you would probably want the system to keep a log of
when the comparisons were made.  Now, in such a system, is it useful or
needful to know the date when the original checksum (or equivalent) was
created?  I'd be curious to hear your thoughts.

Carl Fleischhauer
Library of Congress

On Thu, 14 Mar 2002, MacKenzie Smith wrote:

> In the better late than never category, I've tried to think of any problems
> with this
> proposal and can't, except the general caveat that it *is* possible to take
> generalization to an absurd extreme, however in this case it makes sense to me
> to go for a general solution over a specific one since I agree that there
> will be
> other checksum algorithms and we shouldn't make invalid presumptions.
>
> Could we, pehaps, have an optional attribute of checksumtype, and if that
> attribute is missing, but there is a checksum, assume it's an MD5?
>
> And what on earth would the benefit of a checksum create date be?
>
> MacKenzie/
>
> At 09:57 AM 3/5/2002 -0500, Robin Wendler wrote:
> >One of the general questions that came out of the recent
> >(and soon to be documented, I swear) meeting on technical metadata for
> >audio was about the METS <checksum> attribute of the <file> element.
> >Right now, this is defined explicitly as MD5, but there are now and
> >undoubtedly will continue to be other checksum algorithms in use. We were
> >wondering whether it would be better/possible to generalize this in METS,
> >providing for the checksum type, value, and create date. It seems better
> >to raise this now, rather before we hit the big Version 1.0.
> >
> >What do others think about this?
> >
> >-- Robin
> >
> >Robin Wendler  ........................     work  (617) 495-3724
> >Office for Information Systems  .......     fax   (617) 495-0491
> >Harvard University Library  ...........     [log in to unmask]
> >Cambridge, MA, USA 02138  .............
>
> MacKenzie Smith
> Associate Director for Technology
> MIT Libraries
> Building 14S-208
> 77 Massachusetts Avenue
> Cambridge, MA  02139
> (617)253-8184
> [log in to unmask]
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

May 2023
April 2023
March 2023
January 2023
November 2022
December 2021
November 2021
November 2020
October 2020
September 2020
July 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
May 2019
April 2019
March 2019
November 2018
October 2018
September 2018
July 2018
June 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
January 2017
October 2016
August 2016
July 2016
June 2016
May 2016
April 2016
January 2016
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
January 2014
December 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
February 2013
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
March 2012
February 2012
January 2012
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager