Header Level 2

Now that we've covered how to encode a minimal header in level 1, we'll proceed to encoding some additional details for Robert Schumann’s song “Der Abendstern”. We'll use the following sources:

  • the reprint of the first Leipzig edition 1849, published by Breitkopf & Härtel:
image

  • and the entry describing this manifestation in the catalog of the German National Library:
image

Furthermore, you will learn how to indicate the relationship between this song and the song cycle of which it is a part.

Please use the file from level 1 as the basis of your further encodings.

1) Source Description (sourceDesc)

The file description is the place to encode the sources used to create the electronic file, so insert a <sourceDesc> element into your file description. As the reprint of the first print by Breitkopf & Härtel (Leipzig 1849) is used as the exemplar in this case, you should encode its metadata there.


2) Work description (workDesc)

As a next step, fill in the element for the work description. The work description is represented by the <workDesc> element. It follows the file description.


3) Title statements of the source description and the work description

In level 1 you learned that the file description includes a title statement that contains the title and the persons responsible for the electronic file you're creating. The <titleStmt> element is one of the elements that can occur in different places within a single MEI file. The source description and the work description have their own title statements. So you need to decide where to encode each one.


4) Uniform titles

If you'd like to encode any uniform titles for the „Liederalbum” and the song “Der Abendstern”, you may add another <title> element and a @type attribute with the value of “uniform”.


5) Persons responsible in sourceDesc and workDesc

Now encode the persons responsible for the source(s) used for the electronic transcription by adding a responsibility statement (<respStmt>) to the <titleStmt> within the <sourceDesc> element. Please include role information for everyone involved in the creation of the work.

Do the same for the work description (<workDesc>), adding the persons responsible for the song “Der Abendstern”, the first song of the song cycle.


6) @dbkey, @authority, @authURI, @role

We hope you're following the recommendations to use standardized forms of any names for the responsible parties. If so, add information about any authority file or controlled vocabulary which you've consulted or which provides further information.


7) Information on publication of the source

The next exercise deals with the edition statement (<editionStmt>) and the publication statement (<pubStmt>) of the source description (<sourceDesc>). This exercise encodes information about the publication of the reprint that can be found in the catalog entry illustrated above.

  1. Enter an edition statement (<editionStmt>) after the <titleStmt> element.
  2. Enter a publication statement (<pubStmt>) after the <editionStmt> element.


8) Contents of the edition statement of the source description

The edition statement (<editionStmt>) is a container for metadata pertaining to a particular edition of the material being described. Use the <edition> child element for capturing information about the reprint of the first 1849 printing from Leipzig. The <edition> element contains a word or text phrase that indicates a difference in either content or form between the item being described and a related item previously issued by the same publisher.

The title page of the reprint reads:

Reprint der Erstausgabe Leipzig 1849
Reprint of the First Printing Leipzig 1849


9) Contents of the publication statement of the source description

The title pages also display other information regarding the publication of the reprint. Have a look at the scans below:

imag image

To encode information about publisher, the printer, the publisher’s address, the order number and the copyright notice, you can use several special child elements within the publication statement (<pubStmt>) of the source description:

  1. Please add a <respStmt> element to the <pubStmt> element
  2. Now add a <corpName> element to the <respStmt> and enter the name of the publisher of the reprint.
  3. The sample reads: “Druck: PIROL Notendruckerei, Minden”. Add a <resp> element and a second <corpName> element to the <respStmt> to encode this information on the printer.
  4. You can also encode the address of the publisher, which is given on the title page of the reprint. You may use the <address> element, which requires one or more <addrLine> child elements to specify the place of publication.
  5. For encoding the order number of the reprint, please add an <identifier> element to the publication statement. The @type attribute can be used to specify which kind of identifier you're capturing.

There is also a copyright notice within the reprint. For encoding this, please add an <availability> element as well as an <useRestrict> child element to the publication statement of the source description.


10) Series statement of the source description

As shown on the title page, the “Lieder-Album für die Jugend” is published within the series “Breitkopf Archiv”, which is edited by Joachim Draheim.

You can capture this information in the series statement by adding a <seriesStmt> after the publication statement (<pubStmt>) of the source description.


11) Physical description of the source description

The catalog entry of the German National Library gives some information on physical descriptions of the reprint:

image

Create a physical description (<physDesc> element) within the source description and enter the child elements <dimensions>, which encodes information about the physical size of a bibliographic source, and <extent>, which is used to express size in terms other than physical dimensions, such as number of pages etc.

To encode the plate number of the reprint, found at the foot of page 3 of the source, enter a <plateNum> child element to the physical description.


12) Classification of the source description

Also within the source description, the <classification> element can be used to classify a musical text according to one or more of the following methods:

1. by reference to a recognized international classification scheme such as the DDC, the Universal Decimal Classification, the Library of Congress Classification, or any other system widely used in library and documentation work;

2. by providing a set of keywords, as provided, for example, by British Library or Library of Congress Cataloguing in Publication data.

The following elements are provided for this purpose: <termList> and <classCode>.

The <termList> element categorizes an individual text by supplying a set of terms that may describe its topic or subject matter, its physical or intellectual form, date, etc. Each term is represented by a <term> element. In some schemes, the order of items in the list is significant, for example, from major topic to minor; in others, the list has an organized substructure of its own. Wherever possible, such terms should be taken from a recognized source.

Try to classify the song cycle and enter the data in the <classification> element.

Well done! Within this tutorial you learned to encode all required metadata for identifying the source of your electronic transcription. You also learned how to incorporate a work description in you header.

You've already created quite an extensive header. If you’d like to learn how to encode some more special features of the MEI header, please go on to level 3.