Data for the original stake height and snow depth measurements, as well as the averages and standard deviations was submitted by Andrew G. Fountain to the data manager in August, 1997. The column showing "file name" identifies the original file containing that record. These are ascii text files and can be found on the PC in the McMurdo LTER data manager's office at INSTAAR.
Once submitted to INSTAAR, the data manager used Microsoft Excel and Access software to produce files that were in more of a relational mode. Information was assigned to different files according to type of data it dealt with. Separate files were generated for:
* stake height replications,
* snow depth replications, and
* averages/standard deviations calculated from stake height and snow depth replications.
In March, 2000, Thomas Nylen submitted data from the 1997-98, 1998-99 and 1999-2000 seasons. Instead of lumping all of the stake height and snow depth values for each glacier under one file, they were separated into files for each glacier. Metadata fields were also updated at this time.
In April, 2000, Denise Steigerwald added fields for dataset code and glstkid. Dataset code would allow the data to be linked to the metadata in a relational database. Glstkid is a code that ties stake records to points on a GIS base map being developed by Michael Prentice at the University of New Hampshire.
In addition, Denise divided the 'stake' field to 'stake' and 'stk replcmnt' values. The 'stake' value is an ID for a stake in a given location over time, while the 'stk replcmnt' value shows whether the stake is the original (A), the first replacement stake installed (B), the second stake installed (C), and so forth. (Melting on the glacier over time makes installation of replacement stakes necessary.) Since the replacement value is only relevant for the stake heights and snow depths datasets, division of the 'stake' value into separate fields made it more straightforward for grouping data across different datasets (eg. stake heights and snow densities).
In 2016, data and metadata were enhanced to comply with PASTA's unreasonable requirements.