The move from bit preservation to functional preservation involves raising the “knowledge level” status of the formats in our digital collections from “stored” (which is the current situation) to “identified” or, ideally, “known”. This information can then be used to identify preservation-related risks at the level of individual files, and actions to mitigate these risks can be taken if necessary. ![]() ![]() For known formats, format validation has been performed, and technical metadata have been extracted.For identified formats, formal format identification has resulted in a PRONOM identifier.For stored formats, only bit preservation is done, without any formal format identification (no PRONOM identifier).To this end, the KB has defined three “knowledge levels”, which are linked to file formats 1: One of these is a (gradual) move from pure bit preservation towards full functional preservation. The policy expresses a number of preservation-related goals for the upcoming years. In 2019 the KB published its current preservation policy for its digital collections. It further builds on earlier work I did on this subject between 20. In this post I’ll review to what extent such features can be detected using VeraPDF and JHOVE. fonts that are not embedded in a document), and reliance on external software. This includes encryption and password protection, external dependencies (e.g. The PDF format has a number of features that don’t sit well with the aims of long-term preservation and accessibility. ![]() "Rock 'em Sock 'em Robots Game" by Lorie Shaull, used under CC BY-SA 4.0, via Wikimedia Commons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |