My first week working on the archive was a case of building its architecture.
How I built its architecture.
In diagram form this architecture looks like a root systems (they call it a tree but it’s not, it works down) that starts at the top with the name of your collection. The collection is the ‘National Text Art Archive’ or the ‘Arts Archive Collection’ (it will have more than one name to keep its meaning open and broadly attributable to different bodies). From the ‘collection’ the structure drops down into ‘sub collections’ including the Text Festival Archive. This drops down into three ‘series’: Text 2005, Text 2009 and Text 2011. Decisions from this point on how the material is organised from these series is the point at which this archive becomes authored. How do I break up the admin and correspondence, what do I do with the curatorial plans for various exhibitions and events within the festivals, how do I organise the trail?
Thoughts on the authorship of this archive’s architecture.
The architecture has to allow for the materials and records to mingle. It cannot be organised to the point where the trail leads too directly to each item, record or example of correspondence. You have to leave room for the archive to breathe, for readers of the archive to wander around in. This roominess in the archive is a question of controlled ambiguity, structured vagueness. This project (of building the archive) has to capture and be led by the Text Festival’s approach to collating and gathering materials, artists and documentation for a show. The TF has a way of working that is decisively imprecise and haphazard, this is how it stays exploratory, and experimental.