All, I know I have missed most calls lately but this topic is of high I treat to me as well. Please count me in. Robin Robin Ruggaber Library CTO University of Virginia On Aug 28, 2013, at 11:34 AM, Gail Truman <[log in to unmask]> wrote: > Hoping you already got my "count me in" - but here it is again, just to > be sure. I am keenly interested in this topic. > > Gail > > > > Gail Truman > Truman Technologies, LLC > > Protecting the world's digital heritage for future generations > www.trumantechnologies.com > facebook/TrumanTechnologies > > 510 502 6497 > > > > > -------- Original Message -------- > Subject: Re: [NDSA-INFRASTRUCTURE] interest > From: Mark Evans <[log in to unmask]> > Date: Wed, August 28, 2013 7:59 am > To: [log in to unmask] > > Please count me in also. > > Andrea raises some good points about 'check what' and 'how check'. These > > are particularly important when you are dealing with complex objects > such > as AV content and also when checking at scale. > Its certainly not a one size fits all problem. > > M > > > > Mark Evans > Digital Archiving Practice Manager > Tessella > 51 Monroe Street, Suite 702, Rockville, MD 20850, USA > T: (1) 240 403-7502 C: (1) 240 401 6256 F: (1) 240 403-7507 > E: [log in to unmask] > W: www.digital-preservation.com > > This message is commercial in confidence and may be privileged. It is > intended for the addressee(s) only. Access to this message by anyone > else > is unauthorized and strictly prohibited. If you have received this > message > in error, please inform the sender immediately. Please note that > messages > sent or received by the Tessella e-mail system may be monitored and > stored > in an information retrieval system. > Please consider the environment and do not print this e-mail unless you > really need to. > > > > > From: "Goethals, Andrea" <[log in to unmask]> > To: [log in to unmask], > Date: 08/28/2013 10:38 AM > Subject: Re: [NDSA-INFRASTRUCTURE] interest > Sent by: The NDSA infrastructure working group list > <[log in to unmask]> > > > > Sorry to have missed the call. I'm interested in this project as well if > > could be considered in scope to develop a spectrum of options for > checking > integrity. I think the 'how often check' is one aspect but I'm more > interested in the 'check what' and 'how check'. I could imagine a > spectrum > of practices based on the context and content, e.g. cheap check > practices > where it's a redundant practice, more expensive check practices where it > > matters. > > Andrea > >> -----Original Message----- >> From: The NDSA infrastructure working group list [mailto:NDSA- >> [log in to unmask]] On Behalf Of Dr. Micah >> Altman >> Sent: Wednesday, August 28, 2013 10:04 AM >> To: [log in to unmask] >> Subject: Re: [NDSA-INFRASTRUCTURE] interest >> >> Ditto. Assuming we treat "fixity" broadly to include bit-level curation >> parameters. Also interested in integrating this into the "levels" work >> and >> seeing what we can do in terms of validation of our recommendations. >> >> That said -- will probably need to put analyzing the 2nd round of the >> preservation storage survey at the top of my queue... >> >> best, >> >> Micah >> >> >> >> ----------------------------------------------------------------------- >> ------------------------------------------------------- >> Micah Altman, Ph.D. <http://micahaltman.com> Twitter: >> @drmaltman >> >> Director of Research -- MIT Libraries; Head/Scientist, Program on >> Information Science >> Non-Resident Senior Fellow, Brookings Institution >> "Entia non sunt multiplicanda sine necessitate" - Doctor Invincibilis >> (Corollary, "Ad indicia spectate.") >> >> >> On Tue, Aug 27, 2013 at 2:31 PM, Gallinger, Michelle <[log in to unmask]> >> wrote: >> >>> I'm interested in participating on the file fixity working group to >>> develop guidance on how frequently to check fixity. >>> >>> Best, >>> >>> Michelle Gallinger >>> Digital Programs Coordinator >>> Library of Congress >>> 101 Independence Ave. SE >>> Washington, DC 20007 >>> 202-707-1619 >>> [log in to unmask] >>> >>> >>> ############################ >>> >>> To unsubscribe from the NDSA-INFRASTRUCTURE list: >>> write to: mailto: >>> [log in to unmask] >>> or click the following link: >>> >>> http://list.digitalpreservation.gov/scripts/wa- >> DIGITAL.exe?SUBED1=NDSA-INFRASTRUCTURE&A=1 >>> >> >> ############################ >> >> To unsubscribe from the NDSA-INFRASTRUCTURE list: >> write to: mailto:NDSA-INFRASTRUCTURE-SIGNOFF- >> [log in to unmask] >> or click the following link: >> http://list.digitalpreservation.gov/scripts/wa-DIGITAL.exe?SUBED1=NDSA- >> INFRASTRUCTURE&A=1 > > ############################ > > To unsubscribe from the NDSA-INFRASTRUCTURE list: > write to: > mailto:[log in to unmask] > or click the following link: > http://list.digitalpreservation.gov/scripts/wa-DIGITAL.exe?SUBED1=NDSA-INFRASTRUCTURE&A=1 > > > > ############################ > > To unsubscribe from the NDSA-INFRASTRUCTURE list: > write to: > mailto:[log in to unmask] > or click the following link: > http://list.digitalpreservation.gov/scripts/wa-DIGITAL.exe?SUBED1=NDSA-INFRASTRUCTURE&A=1 > > ############################ > > To unsubscribe from the NDSA-INFRASTRUCTURE list: > write to: mailto:[log in to unmask] > or click the following link: > http://list.digitalpreservation.gov/scripts/wa-DIGITAL.exe?SUBED1=NDSA-INFRASTRUCTURE&A=1 ############################ To unsubscribe from the NDSA-INFRASTRUCTURE list: write to: mailto:[log in to unmask] or click the following link: http://list.digitalpreservation.gov/scripts/wa-DIGITAL.exe?SUBED1=NDSA-INFRASTRUCTURE&A=1