Museum practice study
Solomon R. Guggenheim Museum
The Guggenheim’s “The Conserving Computer-Based Art Initiative” describes an ongoing, practice-based research project on computer-based works in the collection. The page documents a survey and backup of...
Read the complete studyOpen the full essay, notes, bibliography, and publication record.
- Series: A field of practice
- Status: public scholarship
- Institutional author: 6529 Network Museum
- Version: 1.0.0
- Publication date: 2026-08-04
- Research cutoff: 2026-08-04
- Research apparatus: primary-source register
The Guggenheim’s “The Conserving Computer-Based Art Initiative” describes an ongoing, practice-based research project on computer-based works in the collection. The page documents a survey and backup of artist-provided hardware and software, disk images, dependency research, source-code analysis, artist interviews, treatment testing, and dissemination through public presentations and publications.
From components to significant properties
The initiative’s public workflow records hardware, operating systems, programming languages, libraries, peripherals, media files, and relationships among dependencies. It also publishes acquisition checklists, a component spreadsheet, disk-imaging reports, and related documentation.
The Guggenheim describes source-code analysis as a way to document intended behaviors and significant properties that may not be visible during a single viewing. The page notes that computer-science collaboration is necessary for this work because most conservators are not trained to read the relevant programming languages.
The initiative uses Identity Reports for enduring characteristics and Iteration Reports for a particular installation. For a chain-native work, the 6529 Network Museum should use the same record boundary: the identity record should state what is being preserved, while each installation, migration, or fallback should receive a dated iteration record that names the environment, changes, tests, authority, and residual differences.
Restoration made visible
The Brandon credits and restoration page states that the 2016–17 restoration addressed Java applets that no longer displayed correctly, broken links, incorrect typography, an inoperable Mooplay interface, and inaccessible virtual court records. It says original code was retained and commented out when no longer executed; additions were documented through source-code annotation, version control, and treatment reporting. Java applets were replaced with JavaScript functions and animated GIFs, and other obsolete web structures were replaced with documented equivalents.
The “About net.flag” page records the work’s migration from Java to JavaScript and the decisions made around historical flag designs and countries absent from the original set. These pages identify the intervention, the people involved, the technical changes, and the remaining relationship to the earlier work.
What the Museum should adopt
- Create an identity record before accession that names significant properties, artist or estate authority, dependencies, and rights to preserve source, executable, media, and environment.
- Produce a bit-for-bit preservation image where a storage device is part of the work, record fixity and imaging conditions, and retain the original environment description.
- Maintain separate iteration records for every installation, migration, dependency replacement, or fallback build.
- Use code review and behavioral tests to record states, randomness, interaction, external data, timing, and failure modes.
- Publish intervention credits, decision rationales, before-and-after evidence, version-control references, and treatment reports when rights permit.
Where the analogy ends
The Guggenheim’s documented work relies on a CCBA fellowship, collaboration with New York University computer science, conservation staff, artist-provided systems, and case-specific authority. A public checklist cannot create those relationships. Source code is one evidentiary layer; display, interaction, sound, context, reception, rights, and artist or estate decisions must remain separately documented. Identity and iteration reports organize judgment; they do not decide it.
Sources
- Solomon R. Guggenheim Museum, “The Conserving Computer-Based Art Initiative”.
- Shu Lea Cheang and Solomon R. Guggenheim Museum, “Brandon: credits and restoration”.
- Mark Napier and Solomon R. Guggenheim Museum, “About net.flag”.
- Solomon R. Guggenheim Museum, “Seeing Double: Emulation in Theory and Practice”, 2004.
Revision history
1.— 2026-08-04: initial profile.0. 0