The activity or preservation procedure through which an item in the ArtBase database has been created. This may refer to primary source materials supplied by artists, such as artist links and descriptions. It may also refer to actions undertaken by the archivists and the preservation team at Rhizome in order to generate an artwork variant.
Generated by
Property
Open submission
Description: The process of adding items to the database between 1999–2008 was open to all without any filtering or curating by Rhizome staff.
Cloning
Description: The process of making a copy of the artwork files hosted on the artist’s server and transferring the copy to Rhizome’s server. This process was part of the open submission period, but was optional, artists could choose to link their works or clone them.
Webrecorder capture
Description: This process involves the use of Rhizome’s web archiving software tool Webrecorder in order to create an archival WARC file. WARC files are re-performed via Rhizome’s Webenact platform. These re-performances aim to be as close to the original presentation of the artwork as possible, but still involve curatorial decisions taken by the archivist. See the Archival Plan metadata for more details.
Webarchive capture
Description: This process involves the use of a mix of web archiving tools and web archiving resources in order to create an archival WARC file. WARC files are re-performed via Rhizome’s Webenact platform. These re-performances aim to be as close to the original presentation of the artwork as possible, but still involve curatorial decisions taken by the archivist. See the Archival Plan metadata for more details.
Emulated re-performance
Description: This process involves the use of either a cloned copy or a webarchive capture of the artwork, which is then re-performed in an emulated environment due to the artwork’s dependencies on specific components in an operating system or software application which are no longer supported in contemporary iterations of these systems or applications. The emulated environment is served via the Emulation-as-a-Service framework. See the emulated environment’s item page for more details, as well as the Interaction Notes metadata for performance instructions.