Master Encoding Guide: Author

Record Content: Author Element

<author>
Every record has an author name (or initials) on the second line under the date. The vendor was instructed to consider all text that appears before the first instance of the word "to" as an author and code under one author <a> tag. For most records, there will be one name (or initials) before the first instance of the word "to." In the full schema, there are three optional child elements to encode within the parent author tag: person, corporate, and/or office. These tags can be used together or separately. See below for examples.

<person>
Refers simply to a single individual. This element includes a target reference to a separate database of persons with birth and death dates. During encoding (Level 2), encoders will assign a target reference pulled on a list of the most commonly found names. In addition, any names not found on the list will be assigned a target reference. Construction of the target reference should be all lower case, "lastfirstmiddletitle." This will allow for cleaner sorting in the names database.

<corporate>
The corporate tag borrows from the standard cataloging rules for a corporate author. That is, a group of individuals, such as the U.S. Congress.

<office>
The office tag is used to distiguish an individual author from someone writing in the capacity of their office, such as the President of Congress, writing official documentation in his capacity as the President of Congress, but not necessarily as his own person. For example, John Adams may write to his colleague, Samuel Huntington, or he may write to the President of Congress who happens to be Samuel Huntington for several months.

Example:
<author><person target="huntingtonsamuel">Samuel Huntington,</person><office target="presidentofcon"> President of Congress,</office></author>

<author><corporate target="houseofrep">House of Representatives<corporate></author>