Working with Obsolete Files - wvulibraries/mfcs GitHub Wiki

MFCS allows "obsolete" file types (by extension) to be managed in the system in the Obsolete-File-Types administration pages. Once they are input a listing of all the obsolete types can be seen from the Dashboard Auditing Obsolete Files (from the menu).

From this point it is a policy/procedure to convert them. Either replace them in MFCS with a converted version created locally or define a conversion to a known type and keep the conversion in the exports.

Keep in mind that when "overwriting" an archival file with a newer version, created locally, the original "obsolete" version will still exist in revision control.

It is recommended that you download, verify via check sum, and then upload the newer version of the file to MFCS as the archival copy. If you ever need to go back to the original (now obsolete version) use revision control. This allows greater flexibility while maintaining the original copy as well as any new file format derivatives.

All versions will continue to be checksummed when done in this manor. (MFCS does not run a checksum on derivatives generated by the system, because these are not considered archival/preservation but for export for import in an other system.