Hi all,

I'm very sorry that I missed this call. I suspect that my comments below 
were already mentioned during the call by others, but in case they weren't 
here goes.

What a great start to a useful document. I like that it will explain why 
there can't be a set overall standard for scheduling fixity checks other 
than it should be run when a file is moved -- timing depends so much on 
storage medium and infrastructure.

top of p.2: Constraints. Add more info on fixity checks of files on tape. 
Oracle/Sun/StorageTek drives (choose your name) can run checks while the 
tapes are in situ in the drives, so the files needn't be copied to servers 
and checked there. LTO drives can't do that (yet) so the files must be 
copied up to servers for checking, adding lots of work and strain on the 
infrastructure. However, I say "yet" because I corresponded with someone in 
IBM's LTO R&D department. They're working on a driver to check files in situ 
on LTO LTFS drives. She thought it'd be released Q2 2014.

p. 2: more on the trend to run frame-level checksums on very large video 
files (uncompressed, DPX) as a preservation act. If there are frame-level 
checksums, then the error can be immediately identified rather than knowing 
vaguely that the file is corrupt somewhere.

Add: metadata that should be captured, following PREMIS: algorithm type, 
value, creation software, date created, who created it, when checked, 
result.

Best,
Linda


----- Original Message ----- 
From: "Owens, Trevor" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, October 29, 2013 5:39 AM
Subject: [NDSA-INFRASTRUCTURE] Infrastructure Call Today: 2PM EST on Fixity 
check project


Reminder, today we have our working group call. This time focused on 
discussing ways forward on the fixity check project. (See Karen's message 
below.)

As a way to try and kick off the conversation, I started sketching out what 
could be the basis of a short document on fixity checking. It's really just 
a straw man for us to use for the purposes of figuring out what we actually 
would like to produce.

I had a hard time making all of this fit into a neat grid but I think we 
could make something that just spells out different goals, approaches and 
constraints.

Time: 2:00 PM EST, Oct 29th

The call in number will always be:
Call-in number:  866-469-3239
Participant access code:  21408589

-----Original Message-----
From: The NDSA infrastructure working group list 
[mailto:[log in to unmask]] On Behalf Of Karen 
Cariani
Sent: Thursday, September 19, 2013 4:37 PM
To: [log in to unmask]
Subject: [NDSA-INFRASTRUCTURE] Fixity check project

Hi everyone,

I'm sorry for my delay in getting this going.  Since there were a number of 
you interested, I figured I'd just use the list serv for the project work. 
We can use regular phone calls too if there is nothing else going on during 
that month.

Lets start with the notes form the call:  Most of the participants on the 
call were interested in either or both of these issues.

  1.  Getting started with fixity practices. This could, for example, work 
through the each of the 4 fixity levels in the NDSA levels of digital 
preservation. The goal here would be to work through how to get started, 
different kinds of approaches and tools you can use to establish your 
workflows.
  2.  Fixity trade offs decision tool. Given different systems, different 
kinds of content, different scales of content etc. there should be different 
approaches to the frequency of fixity checking. There is interest in 
developing some kind of grid, or decision tree that could help orgs decide 
the best approach to how frequently to check the fixity of their content.

Anyone interested in number 1 specifically or number 2?  Should we start on 
both and see how it breaks out?
For number 2 were a number of ways we could break this out and look at it, 
or rather a number of parameters to frame it.  Here are the ones listed 
above:

System type
Type of content
Scale of content (not sure what this means) Frequency based on those factors 
Any others?

Karen



############################

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