We are currently considering the issue of cover sheets for our repository, but these don't seem to be compatible with the use of checksums/fixity.
Cover sheets may not necessarily be added at very first ingest into the repository, meaning that once they are, the checksum of the object will change. Maybe at some stage the cover sheet will be removed, for whatever reason; maybe down the track we'll want to change the coversheet. Lots of maybes here, all amounting to the fact that if we do use cover sheets, we'll no longer be able to rely on checksums to verify the integrity of an object. Has anybody else considered this issue? Bernadette Houghton Library Business Applications Developer Library [Title: Deakin University logo] Deakin University Locked Bag 20000, Geelong, VIC 3220 +61 3 52278230 [email protected]<mailto:[email protected]> www.deakin.edu.au<http://www.deakin.edu.au/> Deakin University CRICOS Provider Code 00113B Important Notice: The contents of this email are intended solely for the named addressee and are confidential; any unauthorised use, reproduction or storage of the contents is expressly prohibited. If you have received this email in error, please delete it and any attachments immediately and advise the sender by return email or telephone. Deakin University does not warrant that this email and any attachments are error or virus free.
<<inline: image003.jpg>>
