Search

Bench-scale studies were conducted using a constant-head groundwater flow chamber and natural soil. Initial experiments with chlorides and dye were conducted to test the hydraulic and adsorptive characteristics of the chamber. A constant flow of phenol was then introduced into the chamber and contaminant movement with time was monitored under freezing and nonfreezing conditions. The chamber was located in a controlled-temperature room, and freezing fronts were induced from the soil surface downward using cooled Freon circulated through freezer pads placed on the surface of the soil. The results conclusively demonstrate that phenol is excluded from the freezing front and pushed downward through the system. Extensive exclusion of the chemical occurs even though the freezing point of phenol (43 degrees C) is significantly higher than water. The information gained through this research is applicable in cold regions outside Alaska and the Arctic where ground water systems may undergo periodic freezing, and may also be of extreme importance in artificial-freezing scenarios such as those currently being investigated by the Environmental Protection Agency (EPA) as a method of contaminant containment.

The Code4Lib community has produced an increasingly impressive collection of open source software over the last decade, but much of this creative work remains out of reach for large portions of the library community. Do the relatively privileged institutions represented by a majority of Code4Lib participants have a professional responsibility to support the adoption of their innovations? Drawing from old and new software packaging and distribution approaches (from freeware to Docker), we propose extending the open source software values of collaboration and transparency to include the wide and affordable distribution of software. We believe this will not only simplify the process of sharing our applications within the library community, but also make it possible for less well-resourced institutions to actually use our software. We identify areas of need, present our experiences with the users of our own open source projects, discuss our attempts to go beyond open source, propose a preliminary set of technology availability performance indicators for evaluating software availability, and make an argument for the internal value of supporting and encouraging a vibrant library software ecosystem. [ABSTRACT FROM AUTHOR]