My organization is not currently using DSpace, but I am doing some research into its features from a preservation perspective. I've read through the documentation, and am seeking some clarification about file format identification in DSpace.
My understanding is that DSpace recognizes file formats by extension (rather than internal signatures) and compares the extension to an internal bitstream registry, which has certain default values and can be added to as needed. Would this be correct? I suppose if this is true, then version numbers of particular formats (e.g., PDF 1.x) aren't tracked? This thread <https://groups.google.com/d/msg/dspace-community/0xBnqoZUAak/3E63g78CDQAJ>with insightful comments from Bram Luyten and Pauline Ward brings up the idea of looping in DROID or PRONOM, or otherwise broadening DSpace's file format registry capabilities. Has there been any further thinking on this, or have any institutions developed custom workflows? I'm also curious about the question of file *validation* e.g., with a utility like JHOVE, and whether there are any efforts/discussions on that front. Big questions--all thoughts welcome. Russell White Library & Archives Canada -- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
