Validate and report filetypes per file

Version 1 by Lucien van Wouw
on Sep 28, 2011 10:34.

compared with
Current by Lucien van Wouw
on Oct 04, 2011 10:48.

(show comment)
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (10)

View Page History
| *Title* | Validate and report filetypes per file |
| *Detailed description* | _To report the file discrepency on a per file basis, we:_ \\
_ \- open each file from the archive_ \\
_ \- analyse the filetype using droid_ \\
_ \- compare the filetype with the web archive and report mismatch ( we may need to normalize variations in the same mimetype expressions, i.e. image\jpg=image\jpeg )_ \\
_ \- export report in csv_ \\
_Investigate if this tool can be offered as module\add on for the{_}_[jhove2-bfn|]_ _fork_ \\ |
| *Solution Champion* | Lucien van wouw <[email protected]> \\ |
| *Corresponding Issue(s)* | [REQ:Identifying web content]\\ |
| *Tool/code link* | _A link to code on Git hub or a corresponding_ _[myExperiment|]_ _if applicable_ |
| *[Tool Registry Link|]* | _If possible provide a link to information about any third party tools used. Ideally these should point to entries in the OPF Tool Registry_ |
| *Evaluation* | _Any notes or links on how the solution performed_ |
| *Tool/code link* | [heritrix-imp|] |
| *[Tool Registry Link|]* | [Heritrix |]and [Droid|]\\ |
| *Evaluation* | _Relativly time consuming as the entire archive needs to be unpacked before being able to identify each file. But the endresults shows clearly the differences in a simple csv between the Archive format description and the external tool ( Droid in this case ). Solution could be seen as a stand alone validation tool; but in regards to the problem description it ought to be seen as a proof of concept. That is: similar functionality ought to be ported into the Hove2-bfn module._ |