We wish to provide support for as many file formats as possible. As for specific formats, however, the proprietary nature of many file types makes it impossible to make guarantees. Put simply, our policy for file formats is:
* Content within our collections for which we have digital management rights and for which accessibility rights are open, will be retrievable. * We will recognize as many files' formats as possible. * We will support as many known file formats as possible.
Incoming born-digital content is assigned one of the following categories:
* supported: we fully support the format * known: we can recognize the format, but cannot guarantee full support * unsupported: we cannot recognize the format; these will be listed as "application/octet-stream," aka Unknown
By "support" we mean "make usable in the future, using whatever combination of techniques (such as migration, emulation, etc.) is appropriate given the context of need." For supported formats, we might choose to bulk-transform files from a current format version to a future one, for instance. But we can't predict which services will be necessary down the road, so we'll continually monitor formats and techniques to ensure we can accommodate needs as they arise.
In the meantime, we can choose to "support" a format if we can gather enough documentation to capture how the format works. Proprietary formats for which these materials are not publicly available will be made available online until no longer renderable without emulation, using University of Alabama Libraries current hardware and software. It is possible that for extremely popular but proprietary formats (such as Microsoft Word, Excel and PowerPoint), future tools will enable the reformatting of this content into better-supported alternatives. If funding and tools become available prior to obsolesence of this content, we will make every effort to migrate the materials and continue support. Even so, we cannot guarantee this level of service at this point, so we will still list these formats as "known," not "supported."
What to do if your format isn't recognized We understand that there are always more formats to consider, and we would appreciate your help in identifying and studying the suitability of support for formats you care about. If we can't identify a format, we will record it as "unknown," aka "application/octet-stream," but we would like to keep the percentage of supported format materials as high as possible.
Format Reference Collection In the table below, MIME type is the Multipurpose Internet Mail Extensions (MIME) type identifier. Description is what most people use as the name for the format. Extensions are typical file name extensions (the part after the dot, e.g. the extension for "index.html" is "html"). These are not case-sensitive, so either "sample.XML" or "sample.xml" will be recognized as XML. Level is our support for each format:
* supported: we fully support the format * known: we can recognize the format, but cannot guarantee full support * unknown: we cannot recognize a format; these will be listed a "application/octet-stream," aka Unknown
|AIFF||aiff, aif, aifc||supported||audio/x-aiff|
|Postscript||ps, eps, ai||supported||application/postscript|
|Rich Text Format||rtf||supported||text/richtext|
|Microsoft Project||mpp, mpx, mpd||known||application/vnd.ms-project|
|MPEG||mpeg, mpg, mpe||known||video/mpeg|
|MPEG Audio||mpa, abs, mpeg||known||audio/x-mpeg|
|Video Quicktime||mov, qt||known||video/quicktime|
|Unknown||(anything not listed)||unsupported||application/octet-stream|