Automatically Adapting Source Code to Document Provenance

Being able to ask questions about the provenance of some data requires documentation on each influence on that data's existence and content. Much software exists, and is being developed, for which there is no provenance-awareness, i.e. at best, the data it outputs can be connected to its inputs, but with no record of intermediate processing. Further, where some record of processing does exist, e.g. as logs, it is not in a form easily connected with that of other processes. We would like to enable compiled software to record useful documentation without requiring prior manual adaptation. In this paper, we present an approach to adapting source code from its original form without manual manipulation, to record information on data provenance during execution.

Classroom of students watching demonstration of closed-circuit TV

Students watch monitors that show a voltage meter being filmed in the Automotive Dept by department head William C. H. Meyer as part of a demonstration of a new technique in closed-circuit television. This is one of a series of photographs accompanying a press release about the development and demonstration of the new technique at the New York Trade School. Original caption reads, "In a classroom on another floor, students all have "front row" seats for the demonstration. Camera concentrates on close-up of a meter, where readings show the result of the voltage-regulator check. Instructor (standing at microphone) is Arthur Richards." Black and white photograph with accompanying caption.