Analysis of 20.1 Task

Prerequisites and Assumptions

TSH, ABR, and JRG had a long discussion about how to implement Planets integration with the DOMS characterizer. We decided that the best solution would be to:

A major point of discussion regarded what Jhove and Droid should return when called with a file to characterize. Somewhere should be placed code to parse the raw Jhove/Droid output and decide on it. The discussion ended in choosing basically between two different solutions:

  1. Raw tool-output handled by DOMS-characterizer: Jhove and Droid wrapping webservices return only an output dump from the tools, and the DOMS characterise module takes care of parsing and deciding.

  2. Raw tool-output handled by Planets-services: Jhove and Droid wrapping webservices parse tool output and return a few properties (file type URIs) that the DOMS characterise module decides on, as well as the full dump for storing on the file objects.

Advantages and disadvantages:

Advantages of 1:

Advantages of 2:

Disadvantages of 1:

Disadvantages of 2:

Resources