Hi Brian --

As mentioned in a previous recommendation, the BagIt packaging
specification is a very useful and well-supported specification for
delivery a set of file from a source to a recipient. The recipient then can
validate two things: that all files arrived as intended, and that none of
the files changed in transit (or since the checksums were generated for
each file).

You can read more about BagIt here:
https://tools.ietf.org/html/draft-kunze-bagit-12  (remember, it's merely a
specification)

There are tools that exist that will create BagIt bags for you. One is
Bagger, created by the Library of Congress, and available as a java package
here: http://sourceforge.net/projects/loc-xferutils/files/loc-bagger/2.1.3/

Alternatively, a new tool was just released and designed to be easier to
use than Bagger. This tool is called Exactly and is available for free here
(java package, Mac OS build, and/or Windows .exe options):
https://www.avpreserve.com/tools/exactly/

Both of these tools use the BagIt library (a code base for creating a
validating BagIt bags) as the packaging script - so the main differences
are the user interfaces, except Exactly support FTP transfers and will send
emails to verify delivery success.

Alternatively, there are many tools out there that create checksums for
files and list those in text docs or spreadsheets. The benefit of BagIt is
that the recipient can use automated tools to verify the delivery
(completeness and authenticity), which becomes very important when
thousands of files (or more) are involved.

Hope this helps a little.

All the very best --

Bertram Lyons
__________________


Bertram Lyons, CA
AVPreserve | www.avpreserve.com
International Association of Sound and Audiovisual Archives |
www.iasa-web.org

On Tue, Jan 19, 2016 at 7:44 PM, Records Management Email <[log in to unmask]>
wrote:

> Aloha Listserv Colleagues:
>
> I'm researching "hashing programs" to use whenever we provide records in
> response to Legal Orders.  The hashing program will be used to establish a
> "fingerprint" to be able to "authenticate" records and ensure they have not
> been changed or tampered with.
>
> Is anyone using a particular hashing program that they'd recommend?  Is
> there an "accepted standard" hashing program that most agencies accept?
>
> Your input is appreciated.
>
> Mahalo,
>
> Brian
>
>
> Brian A. Moriki
> AVP & Manager - OSD Records Management
> First Hawaiian Bank

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]