The JGOFS Data Management System was designed to be able to read any format that the investigator used for storing his/her data. Because it is object-oriented*, the only part of the System's software that needs to be able to read the data storage format is the 'method', or translation program. To be more precise, 10 routines that are called by the main part of the method must be customized for each data storage format. Another way to view this concept is that the JGOFS software offers unlimited flexibility if someone writes those few routines which make up the 'inner' portion of the method.
However, if the originator of the data, or the people who work for the originator, are not able to write this translator (because of time/money/priority/interest constraints), there are some methods already written. The formats that can be read as part of the JGOFS Data Management System, are listed below. The translation programs (methods) are noted, as well. As new methods are written and, therefore more data formats are JGOFS-readable, we will place them here on the list:
To the Data Management Page
To the U.S. JGOFS Home Page