05.05.2014 Views

Paper Conservation: Decisions & Compromises

Paper Conservation: Decisions & Compromises

Paper Conservation: Decisions & Compromises

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The <strong>Conservation</strong> of the Hussite Codex (Mus.Hs.15492)<br />

Considerations on Minimal Intervention<br />

Birgit Speta<br />

Austrian National Library, <strong>Conservation</strong> Departement, Vienna, Austria<br />

Miniature painting<br />

The gradual is extensively illuminated. A large<br />

part of the first page is gilded. Beneath a picture<br />

of the Madonna, the Smisek family is portrayed.<br />

All initials are decorated, either with ornamental<br />

patterns or in figurative paintings.<br />

The first page of each choral is lavishly illuminated<br />

as well, for example with scenes of the<br />

life of Jesus Christ or motives including vines,<br />

angels, birds or fruits.<br />

Fig. 1: before conservation<br />

This paper discusses considerations on minimal<br />

conservation intervention, using the example of<br />

the Hussite Codex, which is in the collection of<br />

the Department of Music at the Austrian National<br />

Library in Vienna.<br />

History 1<br />

The Hussite Codex is one of the most famous<br />

graduals (books containing antiphons and choral<br />

music) of Kutna Hora (Czech Republik). Known<br />

as Hussite Codex or Smisek Gradual, this gradual<br />

is called the Hussite Codex because it contains<br />

illuminations showing scenes of the life of the<br />

reformer John Hus 2 , while its other name, the<br />

Smisek Gradual, reflects its original ownership<br />

by Michal Smísek of Vrchoviste, who commissioned<br />

it from Matthew´s workshop in Prague. A<br />

note on the last page of the manuscript records<br />

1491 as the year of completion.<br />

Technical description<br />

The object is very large and heavy, measuring 63<br />

cm in height, 42 cm in width and 21cm thick.<br />

All together it comprises 491 parchment leaves .<br />

Because of its size and the substantial metal fittings<br />

the Hussite Codex weighs 42 kg (Fig. 1).<br />

The textblock is sewn on 6 double cords made<br />

of leather plus two cords for the endbands. The<br />

leather of the cover is blind-tooled. The arms<br />

of the commissioning client is situated in the<br />

middle of the board. There are two huge clasps at<br />

the front, one of which is engraved with the year<br />

‘1562’.<br />

Another important detail: the headbands were<br />

plaited, which means that the strips of leather<br />

are sewn around the primary headbands as well<br />

as through the leather of the cover. As the primary<br />

headbands are part of the sewing, the cover<br />

of the spine is fixed to the textblock on head and<br />

tail.<br />

This detail will play a significant role in our<br />

considerations on conservation treatments.<br />

Damage<br />

The parchment of the textblock was in good condition,<br />

though there were minor losses or abrasions<br />

on the illuminations.<br />

The greatest damage and at the same time the<br />

greatest challenge was the fragile connection between<br />

textblock and the upper board.<br />

The upper board was connected with the<br />

textblock by just two strips of parchment backing<br />

and two weak and deteriorated double-cords<br />

as the leather of the cover, most of the backing<br />

and the flyleaves were broken in the upper joint.<br />

Due to this damage in combination with the<br />

weight of the front board every opening of the<br />

manuscript could have led to a total separation<br />

of board and textblock.<br />

The leather of the spine is very brittle and<br />

was also already broken at the joint to the lower<br />

ICOM-CC Graphic Documents Working Group Interim Meeting | Vienna 17 – 19 April 2013<br />

21

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!